SolarWinds Observability REST API only return logs created in the last hours since June

It worked fine until May and showed all the logs, but since then only shows recently created logs (in the last few hours)

It also happens in the SWO-CLI tool, by default no older results are shown. But in this case there is a min-time parameter that allow to show older logs

But in the API I tried all parameters in the documentation, even dates, but never get older results

https://api.eu-01.cloud.solarwinds.com/v1#/logs/getLogs 

This query return no results, even if we had some logs visible in the Web (my.eu-01.cloud.solarwinds.com/.../logs and in the SWO-CLO :

api.eu-01.cloud.solarwinds.com/.../logs the process

How can I get logs created in the last days?

Parents
  • In brief: since June the SolarWinds observability REST API only displays logs created a few hours ago

    Example of the same query with one hour lapse:

    1. [GET] logs results at 12:14 : 1 result

    2. [GET] logs results at 13:23 (0 results)


    At the same time in SolarWinds' web the same log result (of the first query) and older are present:



  • Solved.

    I didn´t understand how the logs' REST API works:

    Log searches can take a long time to complete, even if there are no results, so the API splits the work into multiple round trips. That ensures that any interruptions or errors can be efficiently resumed, rather than trying to do everything in a single query that could potentially take hours to finish. It also allows interactive clients to provide regular progress reports, similar to the Log Viewer. We’ll be adding some examples to the documentation to clarify how it works.

    So when querying the API, regardless of what options are sent, the consumer has to be prepared to follow any “nextPage” URLs until all of the results are received.

Reply
  • Solved.

    I didn´t understand how the logs' REST API works:

    Log searches can take a long time to complete, even if there are no results, so the API splits the work into multiple round trips. That ensures that any interruptions or errors can be efficiently resumed, rather than trying to do everything in a single query that could potentially take hours to finish. It also allows interactive clients to provide regular progress reports, similar to the Log Viewer. We’ll be adding some examples to the documentation to clarify how it works.

    So when querying the API, regardless of what options are sent, the consumer has to be prepared to follow any “nextPage” URLs until all of the results are received.

Children
No Data