You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that since then, the query results are fully loaded into memory and held there in full for a brief time. This causes an out of memory error on history views as there the number of resulting rows is usually very large.
To solve this, we may do one of the following things:
Query redis in exports again for each individual result. Pro: quickly done, Con: Bad performance
Fetch results in parts and query redis every nth number of them. Pro: Better performance, Con: Not easily done
I'd prefer 2) 😅
nilmerg
added
the
difficulty/hard
You can do this! Just ask someone for input first, please. And demand (some of) it as comment here!
label
Jan 17, 2024
nilmerg
changed the title
HTML exception session_name(): Cannot change session name when headers already sent when trying to get JSON history output
Unable to get JSON history output
Apr 9, 2024
Describe the bug
The following HTML is output at the end of the JSON when requesting the history of a service for a host
Additionally, the full check history for the service is not returned either in the JSON that is output, just one check result as far as I can see.
To Reproduce
OR
Run a cURL command like the following requesting JSON
curl -s -HContent-Type:application/json -HAccept:application/json -u api:api "https://icinga/icingaweb2/icingadb/service/history?name=service&host.name=hostname&format=json"
Expected behavior
Well formatted JSON, with the full check history is returned
Your Environment
Include as many relevant details about the environment you experienced the problem in.
icinga2 --version
): r2.14.1-1icingadb --version
): v1.1.1php --version
): 7.3.33The text was updated successfully, but these errors were encountered: