topic Some simple questions/remarks about segments and security context in Open Q&A

Some simple questions/remarks about segments and security context

henk_stobbe — Wed, 11 Jun 2025 13:49:56 GMT

Hello All,

To keep it simple:

- Segments are simply put, filters and security context can be used as a kind of ACL

- You can only have one security context, this is as designed

- Security context is not available on custom metric

I really like your comments on this (-;

KR Henk

Re: Some simple questions/remarks about segments and security context

christian_k — Wed, 11 Jun 2025 14:00:20 GMT

Hello Henk

Thanks for sharing your feedback!
As there is no concrete question, I assume you want to express that you are unhappy with the current options for defining access as well as filtering criteria.
You are right with your observation that Segments are used as one way of filtering data - it is mainly about adding individual context to all of the data stored in Grail, across all data types.
Security context is a way to add an additional attribute for defining data access - but it is not the only one. Looking at https://docs.dynatrace.com/docs/manage/identity-access-management there are more options available to define policies.
I'd love to hear where the current capabilities don't fit your needs - you can either add them in this thread or add me on LinkedIn to share your thoughts.

Best Regards
Christian

Re: Some simple questions/remarks about segments and security context

henk_stobbe — Wed, 11 Jun 2025 14:16:41 GMT

Hi Christian,

No, not unhappy (-; Just to make it clear for me.

Can you also comment on the last on?

Security context is not available on custom metric

So as use case: Suppose you create a "log metric", is it still possible to add a security context?

(just like to know)

KR Henk

Re: Some simple questions/remarks about segments and security context

christian_k — Fri, 13 Jun 2025 05:53:27 GMT

Hello Henk

Then even better 🙂
And yes, I can confirm that with the next update on OpenPipeline, we will also introduce ingest and processing pipelines for metrics. These will give you the possibility to perform processing steps (such as renaming/dropping attributes, adding new fields, etc.) and setting the security context.

So the short answer is "yes." Like with other events, you will have the possibility to modify the metadata so it fits your requirements. You can expect this feature to be rolled out at the end of July / early August.

Best Regards
Christian

Re: Some simple questions/remarks about segments and security context

henk_stobbe — Fri, 13 Jun 2025 06:38:13 GMT

Good morning Christian,

Thanks for your answer and the glimpse into the near future👍

Have a nice day,

KR Henk

Re: Some simple questions/remarks about segments and security context

avinashpodisett — Mon, 23 Feb 2026 20:23:37 GMT

I expected segments is onething that is going to address a lot of our issues, but i am not at all happy with how this functionality was rolled out.
no proper documentation.. and not able to use existing variables or command line arguments , as dynatrace already capturing it ? for shared infrastructure org, create segments is not user-friendly at all. can't reuse any of our tags either ?
for openshift, recommendation is to use K8 namespace, with that we are seeing traces and not services in the services page 🤔.