topic Re: Identifying logs that are not ingested programatically in Dynatrace API

Identifying logs that are not ingested programatically

jonno56 — Fri, 19 Apr 2024 06:20:20 GMT

In a host screen, we can see logs that have been detected but are not ingested:

How can these be listed via an API call?

I have looked at the data returned from the entity API for this host & also for the process_group (& process_group_instance) and the data isn't in those models.

Re: Identifying logs that are not ingested programatically

AntonPineiro — Thu, 18 Apr 2024 10:45:05 GMT

Hi,

Logs are discovered automatically but if you want to ingest then, you need to create logs ingestion rules.

It means, you can check your rules in tenant, host groups or host to know.

It can be checked from API.

Best regards

Re: Identifying logs that are not ingested programatically

jonno56 — Thu, 18 Apr 2024 10:58:48 GMT

Thanks - I know that we need to create ingestion rules. We have developed self-service functionality where users can configure this themselves via code.

However - if the log is not detected, it requires a "custom log source". I can't see an easy way to determine if a custom log source rule is needed for a specified log path, via an API.

Re: Identifying logs that are not ingested programatically

Yosi_Neuman — Sat, 27 Apr 2024 19:07:45 GMT

Hi @jonno56

Check the response of /api/v2/entities/{entity-id} with process instance id and look for logFileStatus or logSourceState values. If its not appears try to extend the api timeframe.

HTH

Yos