topic Re: Refresh tags from environment variables in Open Q&A

Refresh tags from environment variables

markusb — Thu, 04 Dec 2025 20:20:07 GMT

I set a couple of tags from environment variables.

These tags can change when the process is restarted. But Dynatrace still displays the old setting. How can I tell Dynatrace to refresh the tags to what the environment variables say.

For example I have

DT_RELEASE_VERSION=v10.4.0-b02

in my environment.

After updating the software the variable is set to

DT_RELEASE_VERSION=v10.5.0-b01

but in Dynatrace I still see the old value 'v10.4.0-b02'.

How can I tell Dynatrace to refresh the tags bases on the environment variables of the running process?

Re: Refresh tags from environment variables

AntonPineiro — Fri, 05 Dec 2025 07:34:54 GMT

Hi,

You can try to ingest metadata using oneagenctl + autotagging rule.

Best regards

Re: Refresh tags from environment variables

m3tomlins — Fri, 05 Dec 2025 17:46:53 GMT

One of our experiences is that tag value updates are delayed with the auto-tagging propagation, for complex rules. If you have tags that are applied to other layers in the "stack" (e.g. apply to services, or underlying hosts, etc). In some cases it could take hours for a tag to be propagated to the new value. We ended up scoping our auto-tagging rules to limit propagation and keep tags from being applied unneccesarily to other entities.

One other thought I had: perhaps your process restart isn't refreshing the session hosting the process?...thus the environment variables would not be dropped and re-set on a new underlying session?

Re: Refresh tags from environment variables

sujit_k_singh — Mon, 08 Dec 2025 22:29:29 GMT

Dynatrace reads environment variables (like DT_RELEASE_VERSION) only at process start when OneAgent injects its hooks. If you change the variable and restart the process, Dynatrace should pick up the new value — but if the process group detection or tagging logic is cached, the old tag can persist until the agent re-evaluates.

Restart the monitored process. If restart didn’t help, restart the OneAgent service on the host. This clears cached metadata.