Restricting access to Service metrics using security context

[panumjp]

Is it possible?

I have a service with security context configured, but I don't understand how security context should be propagated to time series created by the service.

For example dt.service.request.count used in graphs in service overview of Services application.

[jason_gs]

refer to this post https://community.dynatrace.com/t5/Open-Q-A/Security-on-Metrics-SaaS-Possible/td-p/274384 

[panumjp]

Thanks for the tip. This looks like good method to use if you need to restrict access by metric key. And that probably works well in use case where it is possible to have a metric key for every "security boundary".

In the "Host tags and properties" section of this documentation page https://docs.dynatrace.com/docs/manage/identity-access-management/use-cases/access-security-context
it states: "After you set the security context on a host, it will be used to automatically determine the security context for all logs, spans, metrics and events that are sent from this host."

I believe there is no equivalent functionality for services...

According to this page https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/guides/metadata-automation/k8s-metadata-tel...
security context enrichment for Service metrics in Kubernetes environments will be available in the future.

I like the idea of security context, but it's unfortunate that it's not available everywhere (or is it?). As a Dynatrace newbie, I find it quite challenging to determine from the documentation where it can and cannot be used.

[DanielS]

As you say, @panumjp , this isn't an easy task. Based on my personal experience of using Dynatrace for over nine years, it's helpful to have a general overview of the platform to understand the scope of these tasks. My advice in these cases is to seek help from the community, which has many knowledgeable people willing to help. And if you need something more extensive than a question, I recommend finding a professional with specific experience who can help you build the foundation and explain the implications.

[jason_gs]

We're starting to see service metrics in grail appearing: https://docs.dynatrace.com/docs/shortlink/release-notes-saas-sprint-310#calculated-service-metrics-i... but it'll be some time before there's parity with the builtin metrics from classic. Is it a must-have feature is the short term to control access to metrics; is this something you could do in the future?