topic Re: Service detection rules for gRPC calls in Open Q&A

Service detection rules for gRPC calls

mmsz — Tue, 20 Jun 2023 13:04:23 GMT

Hi,

When I try to separate a gRPC call from the requests detected as "Requests to public network" it's not working. The support suggested to use the Service Detection Rules, but I tried a couple of different rules and didn't work either.

Does anyone know how to accomplish that?

The trace information looks like this:

Re: Service detection rules for gRPC calls

EduardoDelBas — Tue, 13 Dec 2022 11:02:39 GMT

Same case here with over Dynatrace SaaS:

grpc://google.pubsub.v1.Subscriber

and

grpc://google.pubsub.v1.Publisher

Could you help us?

Thanks in advance

Re: Service detection rules for gRPC calls

gerald_ehmayer — Wed, 14 Dec 2022 09:08:18 GMT

Hello, please check if you find the grpc path, e.g., "google.bigtable.v2.Bigtable" in the list of watched services ("publicInternetServices"):
see DebugUI > Cassandra-persisted configuration + Auditing > Part: Services configuration > Load latest JSON > "publicInternetServices" list

Re: Service detection rules for gRPC calls

EduardoDelBas — Wed, 14 Dec 2022 09:16:21 GMT

Hi Gerald, how can access to that option "DebugUI"?

Re: Service detection rules for gRPC calls

gerald_ehmayer — Thu, 15 Dec 2022 09:29:24 GMT

Unfortunately this is a Dynatrace diagnostic feature that is not accessible per default. Please contact support for help or raise a request for assistance.

Re: Service detection rules for gRPC calls

EduardoDelBas — Thu, 15 Dec 2022 10:10:54 GMT

Thanks for your info

Re: Service detection rules for gRPC calls

elodie_lam — Wed, 17 May 2023 16:35:12 GMT

I agree with that idea, I have created a RFE: https://community.dynatrace.com/t5/Product-ideas/Service-detection-for-gRPC-calls-detected-as-quot-Requests-to/idi-p/212505#M37528

Could you please vote? Thank you!

Re: Service detection rules for gRPC calls

Jennny_hz — Mon, 26 Feb 2024 15:13:16 GMT

@mmsz I don't know if you still need help with this topic and from what I've seen @elodie_lam RF hasn't been released yet and we don't have a scheduled date.

However, I managed to break the service through a custom device by entering the called IP range.

To find the IP I checked some requests and established the range: for example 111.11.11.1 to 111.11.11.10
(the field only accepts 10 IPs).

Note: All other settings are customized and you can enter as you see fit.

After creating the custom device, this was the result in my environment:

Then I renamed the services and they were:

CUSTOM DEVICES MENU

The Custom Devices menu is not highlighted, you can access it by adding #newcustomdevices at the end of your URL, as follows:

Managed: https://{environmentid}.live.dynatrace.com/#newcustomdevices