Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

impossible to export an event in json with icingaweb2 #5261

Closed
fdumont35 opened this issue Sep 19, 2024 · 5 comments
Closed

impossible to export an event in json with icingaweb2 #5261

fdumont35 opened this issue Sep 19, 2024 · 5 comments

Comments

@fdumont35
Copy link

Describe the bug

Hi, for an application, I want to automatically retrieve the entire content of the output field of an old event.
image

I can't do that with icinga2 api.
With icingaweb2 / eventhistory I have only the first line of the Output field.
So I try with this path : XXX/icingaweb2/monitoring/event/show?type=hard_state&id=22790006&format=json
but json export does not work. It is ok with pdf, but not with json and csv format.
Can you fix this ?

To Reproduce

Try to get json response with postman of in a web browser

Your Environment

Program Version | r2.14.2-1

Thank you for your help

@nilmerg
Copy link
Member

nilmerg commented Sep 23, 2024

Hi,

I'd rather suggest to use Icinga DB Web's export functionality as basis for your app.

The monitoring module will not receive such an addition anymore.

@nilmerg nilmerg closed this as not planned Won't fix, can't repro, duplicate, stale Sep 23, 2024
@fdumont35
Copy link
Author

fdumont35 commented Sep 23, 2024

Hi Nilmerg,
It is not possible de add a parameter to icingaweb2/monitoring/list/eventhistory to export in json not only the first line, but all the content of output field ?

@nilmerg
Copy link
Member

nilmerg commented Sep 23, 2024

Possible, probably. Worth the effort, not really. 😉

@fdumont35
Copy link
Author

Thank you for your response, one last question :
Do you know why the json export for path icingaweb2/monitoring/event/show is not working ?
Is it a problem on our side or global to icinga r2.14.2-1 ? You will not plan to fix this ?

@nilmerg
Copy link
Member

nilmerg commented Sep 23, 2024

The reason is, it is not implemented. In Icinga Web 2. (Specifically, the monitoring module) Icinga DB Web is the successor of the monitoring module, hence why I'm suggesting you to switch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants