topic Re: "OneAgent log analytics" process lost after reactivating monitoring in Dynatrace API

"OneAgent log analytics" process lost after reactivating monitoring

AlexLarrieu — Wed, 27 Aug 2025 10:22:37 GMT

Hello,

We use a API v2 to disable and enable monitoring.

curl 'https://[tenant]/api/v2/settings/objects' \

-X POST \

-H 'Accept: application/json; charset=utf-8' \

-H 'Content-Type: application/json; charset=utf-8' \

-H 'Authorization: Api-Token ACCESS_TOKEN' \

-d $'[{"schemaId":"builtin:host.monitoring","schemaVersion":"1.4","scope":"HOST-ID","value":{"enabled":true}}]'

After activation, we lose the process «OneAgent log analytics » as well as others (OneAgent extensions and OneAgent network). So no more log ingestion.

The healthcheck.log file gives us information :
[0000406b] [severe ] [oneagentloganalytics] Failed to create named pipe /var/lib/dynatrace/oneagent/agent/watchdog/oneagentloganalytics_pipe_16485: File exists

It is true, this file exists.

If we manually delete the « oneagentloganalytics_pipe_16485 » file, the « OneAgent log analytics » is restarted.

How to use this API without losing log ingestion?
Or is there a problem with the operation of Oneagent?

Re: "OneAgent log analytics" process lost after reactivating monitoring

AlexLarrieu — Tue, 26 Aug 2025 08:08:01 GMT

If I use the button "Monitor this host" in host monitoring settings, processes restart.
I think that confirms that the API has a problem.

Re: "OneAgent log analytics" process lost after reactivating monitoring

Michal_Gebacki — Fri, 12 Dec 2025 13:57:31 GMT

Hello, @AlexLarrieu!

Could you take a look at these Documentation pages and let us know whether anything in here is helping do address your issues highlighted above?

Log ingestion via OneAgent
Log ingestion API

Thank you for any feedback!