16 Apr 2023 04:18 PM - last edited on 12 Jun 2023 09:56 AM by MaciejNeumann
Dynatrace 1.261 introduced new API /api/v2/monitoringstate for querying status of monitoring for process group instances. At first sight this looks as a replacement for legacy process group API v1.
It seems this API is not yet in the documentation , @jaroslaw_orlows can you give a look?
I'd like to ask folks using the API already how can you use it on a larger scale?
I ran into two issues severly limiting usage of this API:
Solved! Go to Solution.
08 Jun 2023 05:42 PM
im right there with you on this @Julius_Loman. Have you made any headway with this?
08 Jun 2023 06:17 PM
@ChadTurner no, there is no progress I'm aware of. In the current state is not useful for us, we are still using the legacy v1 smartscape API for process groups (mostly detecting processes requiring restarts).
08 Jun 2023 06:27 PM
Yeah I tend to fall back on the Legacy methods even when they are "Deprecated" lol
18 Sep 2023 10:18 AM
Looks like some of my wishes sometimes make it to the product 😁
In 1.275 there is finally pagination supported as described in release notes. Still waiting for filtering on the monitoring states
19 Apr 2024 02:58 PM
Hi,
I'd like to get a list of all process groups with status "restart_required". I supposed it should be entitySelector like this for monitoringState API: type("PROCESS_GROUP_INSTANCE"),healthState("HEALTHY"),state("restart_required") but there is response:
{
"error": {
"code": 400,
"message": "Constraints violated.",
"constraintViolations": [
{
"path": "entitySelector",
"message": "Scope: state. Cannot deserialize value: \"restart_required\"",
"parameterLocation": "QUERY",
"location": null
}
]
}
}
We need such option for filtering to replace depracated API: .../api/v1/entity/infrastructure/processes?restartRequired=true&includeDetails=true.
Please help.
Michal
19 Apr 2024 10:03 PM - edited 19 Apr 2024 10:03 PM
That's what I mentioned above. That API does not allow filtering on the severity or state value. You can only query by entitySelector and then iterate the output, which is far from being effective.