Manage oneagent

[avasiliev]

Hi all!

I have some questions about oneagent:

- How I can determine oneagent version on hosts via Saas API?

- How I can deploy custom version of oneagent via API? Or we can do it only through GUI?

- Can we trigger oneagent update on host group via API?

- How we can track new releases of oneagent? I found rss feed with releases, but I would like a better solution

- After onegant updated, it wants to restart services, how I can avoid this? I don't want restarted my services, after upgrade oneagent.

[Joe_Hoffman]

Artem,

You seem to have concerns about the version of OneAgent. Perhaps you can explain your use case where the automatic updates to OneAgent do not work for your situation.

Keep in mind that after a OneAgent update, you can restart the associated services at your convenience, it does not need to be restarted immediately after the OneAgent update.

[anuranjan_kumar]

thanks Artem...got answer for my ques.

[rodrigo_alvare1 · Accepted solution]

Hello Artem,

Would be great if you can explain your use case as Joseph mention, so we can take a look to solutions for that.

If you just look for single answers:
- How I can determine oneagent version on hosts via Saas API?

You can retrieve all agents and each agent version using the REST call /entity/infrastructure/hosts 

Think that even if you have the last version downloaded, some agents could still are running in older versions if they were not restarted in a long time, that is why you cannot get a single value for all the hosts. But if you are interested in general oneagent version, you could retrieve the version running on the cluster and agent will be one behind (so cluster 164, the last oneagent version will be 163)

- How I can deploy custom version of oneagent via API? Or we can do it only through GUI?
Again in the API you can find different endpoints like in the Deployment section, the /deployment/installer/agent/{osType}/{installerType}/latest  endpoint to download the latest agent version, or another call like /deployment/installer/agent/{osType}/{installerType}/version/{version} that allow you to select the version

- Can we trigger oneagent update on host group via API?
Not sure about this one, I think it is not possible.

- How we can track new releases of oneagent? I found rss feed with releases, but I would like a better solution

A new Release is expected every month, if you have enabled autoupdate, it will be available in your environment as soon as it is published.
You can get more information about the new releases by
https://www.dynatrace.com/news/category/release-notes/

https://www.dynatrace.com/support/help/whats-new/dynatrace-release-notes/

- After onegant updated, it wants to restart services, how I can avoid this? I don't want restarted my services, after upgrade oneagent.
After an upgrade the agent want to restart the services to start using the new version, but it will not restart them. You will have to do it and in the meantime the old agent will still work and capture/report information as normal.
See the doc: https://www.dynatrace.com/support/help/technology-support/operating-systems/linux/operation/update-o...

Following Dynatrace OneAgent auto-updates, you must restart all server processes, as some components of Dynatrace OneAgent keep running in processes that are monitored by Dynatrace (for example, Java, .NET, Apache, and IIS). These processes will continue to be monitored with the previous version of Dynatrace OneAgent until they are restarted. Following restart, these processes will be monitored with the latest version of Dynatrace OneAgent.

Regards

[anuranjan_kumar]

Does DT oneagent is backward compatible???

[Julius_Loman]

You can use older oneagents. Officially supported are all oneagent versions not older than 1 year. That means you have to restart your application at least once per year.

[anuranjan_kumar]

thanks....

[adelgado]

Hi Everyone! I work with Artem- I'll try to provide some context around our use case.

We have automated our deployments to new hosts with scripts- We have several environments(tenants) and hundreds of apps (and all the headaches that go with it- Zones, Hosts groups etc) ultimately we are looking at over 5000 hosts over 6 tenants(and counting)

When a new version of the agent is released we have to go back and update every script (there could be potentially hundreds of different script configurations) -

Auto-update on the host would work- but if the environment is auto-scaled up in AWS and runs our script it could be installing an older version of the agent. Also in A DevOps world as we deploy our own new releases and spin up replacement instances with new code- the script would execute and older agent install if it was not updated to reflect newer version

We want a way to pull the latest version number or maybe agent file name- through the API if possible - so that we can put that into our automation - sample logic could be script runs- pulls the version or file name- and incorporates that variable into the build script so that it will install the latest version- or even better - say N-1 release.

I hope that helps.

I suppose we can have all scripts pull version from one location- and we could just manually update that location/file with the file name of the latest agent (of whatever version we want to install) - That way we just update one variable- and all the scripts can pull from there- but we would like to be able to pull this from the tenant API directly.

[rodrigo_alvare1]

Hello Alexis,

I think that the API I mentioned before could help you:

- How I can deploy custom version of oneagent via API? Or we can do it only through GUI?Again in the API you can find different endpoints like in the Deployment section, the /deployment/installer/agent/{osType}/{installerType}/latest  endpoint to download the latest agent version, or another call like /deployment/installer/agent/{osType}/{installerType}/version/{version} that allow you to select the version

Also you could try to recover the last version with

/deployment/installer/agent/{osType}/{installerType}/latest/metainfo and substract one version and request the N-1 version with

/deployment/installer/agent/{osType}/{installerType}/version/{version}

Regards