Enrich metric with some host tags using Openpipeline

[kumaravel]

I am trying to enrich the metric with one of the host tag values which can be set as dt.security_context for better filtering through the Openpipeline metric processing.

Is it possible to access the host tags for the host metric ingested? 

I do get the host id and host group id, is there some other information like meatdata, ostype, etc of host available in the openpipeline processing?

Kind Regards,

Kumaravel

[PierreGutierrez]

Hi @kumaravel 
If you are using OneAgent for the ingest metric, I think the host tag is part of the register automaticaly. 
Do you have any picture? or more detail please.

[Julius_Loman]

Those values are not available in OpenPipeline processing. For fast processing, lookups are not available. For general enrichment, look at primary grail fields: https://docs.dynatrace.com/docs/shortlink/semantic-dictionary-primary-grail-fields .

@PierreGutierrez, afaik only the custom properties (not tags) you set on the host level are added as dimensions for host and process group metrics (from that host).

If you want to add this information for reporting, an easier approach would be to look up the data in DQL on query time.

[PierreGutierrez]

Thanks @Julius_Loman 

Maybe my answer was too general.
I was thinking about using OneAgent SDK, Stats D or Extensions.

When the extension brings information from the host, in the extension configuration you can sometimes place tags, and even more so when custom is developed, you can define more information.

For a simulation, if the ingestion of the host metric comes with the host data or name, through DQL you can access to relate it with Lookup, Join, etc. 

I think in OpenPipeline in Processing and Permissions (set security context) could be something.
Just is a idea⚡

[kumaravel]

Thanks for the inputs.

DQL does allow to do lookup and get tag information.

But I am looking for an option to enrich the metric with information that could set proper security context during the ingestion and allow the use of segments in more effective way. This will ensure users get quick access to their metrics and may be certain metrics can be restricted in future as well.

[Julius_Loman]

Can't you set the security context on the source?

[kumaravel]

In case of metrics ingested for kubernetes or from OTEL, I still have some addtional information but for a VM host through oneagent how can it be done on the source?

[Julius_Loman · Accepted solution]

Kubernetes approach https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/guides/metadata-automation/k8s-metadata-tel...
For OTEL, I think you can add the OTEL resource attribute dt.security_context , but I've never tried it.

For OneAgent host, you can add additional metadata (properties) for the host and those will be added to telemetry data. See more at https://docs.dynatrace.com/docs/shortlink/tagging-hostautotag#host-metadata.