16 May 2020
10:34 PM
- last edited on
23 Nov 2023
12:10 PM
by
Michal_Gebacki
Hi ..How i can be notified when the OneAgent version is updated? I need to setup a change management notification when Dynatrace updates OneAgent to a new version. What are the ways and is there any link that i can look through.
Solved! Go to Solution.
Check deployment status of OA's for your current status
Or from rest api - Topology & Smartscape - Host
If you want to control the update manually, switch off the automatic update.
HTH
Yos
Do you have an idea if the timestamp value in the API results is when it was installed, or some time related to when the agent was developed/released?
Hi @Antonio S.
The timestamp is the released time of the OA version
Yos
Should have seen that all timestamps are the same for all hosts, so it makes sense to be the OA version. Thanks!
Is there a way for us to have notification when dynatrace version updates? Like need to send a notification for the teams.
For automatic updates there is no way to get alerts of update OOTB.
You can control the updates manually.
Yos
That RFE is about SaaS cluster update notifications. The mention of OneAgents only points back to this thread.
Has anything further been attempted regarding notification of OneAgent updates (not just the release/rollout date) ?
I'm also on the same boat as I would not only like to get notified when new versions become available for our SaaS tenant but also new revisions. I've raised multiple chats/tickets about this but always hit a brick wall.... Looks like this is still not possible OOTB and therefore needs periodic polling of the API v1/deployment/installer/agent/versions/{osType}/{installerType} incl. parsing of the response to check for new entries - something that we would like to avoid if possible...
For us it would be important to have at least some kind of email notification or - even better - a webhook integration (similar to the one for problem notifications) as we are building our own codemodule images for k8s app-monitoring which are then pushed to a private registry with "latest" and "release" tags for test and production rollouts...