Key Requests

[BrunoBaptista]

Hi everyone,

I hope you're all doing well.

I came across something that raised a question for me.

I ran some tests while creating a Dashboard for a few endpoints. Since I was using metrics rather than spans, I noticed that some endpoints seemed to use timeseries {... in their queries.

Why do some endpoints appear without the need to be marked as Key Requests, while others require it?

The only difference I was able to identify between the ones that appear and the ones that don't is that the endpoints that already appear in the Dashboard do not go through Kubernetes, while the ones that don't appear do go through Kubernetes.

Does anyone know why this happens or have any insight into this?

I've attached two examples for reference.

[sujit_k_singh]

Hi @BrunoBaptista 

This comes down to how Dynatrace detects the service, not whether it's on Kubernetes. Dynatrace has two ways of building the per-endpoint rows that feed timeseries/dashboards:

SDv2 → all endpoints show up automatically, no marking needed.
Classic SDv1 without Enhanced endpoints → only endpoints manually marked as Key Requests get their own timeseries data. Everything else falls into an aggregate bucket with no per-endpoint metrics.

So the split you're seeing (Pix.Recorrente.Api showing up fine vs. spi-liq-api needing Key Requests) is most likely because those two services are being monitored under different detection modes.

Thanks,

Sujit

[Fin_Ubels]

You can also enable automatic endpoint detection for SDV1. This allows you to start moving away from manually marking key requests and reaping the benefits of being able to granularly measure all of your endpoints. You can find more details in the docs here for SDV1 Enable endpoint metrics for SDv1 services — Dynatrace Docs and here for SDV2 Customize endpoint detection in Service Detection v2 — Dynatrace Docs

[sujit_k_singh]

Hi @Fin_Ubels 

That's a great point!