22 Aug 2025
01:58 PM
- last edited on
27 Aug 2025
11:22 AM
by
GosiaMurawska
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?
26 Aug 2025 09:08 AM
If I use the button "Monitor this host" in host monitoring settings, processes restart.
I think that confirms that the API has a problem.