Closed icinga-migration closed 9 years ago
Updated by mfriedrich on 2014-10-10 19:46:35 +00:00
nebstruct_notification_data doesn't provide any long_output, which means that the core would be needed to provide such when calling the notification event broker triggers.
Thise involves an update for the nebstruct (so a feature for 1.12). Try the attached patch and report back, please.
Updated by mfriedrich on 2014-10-24 22:29:16 +00:00
Any feedback?
Updated by mfriedrich on 2014-10-24 22:29:24 +00:00
Updated by mfriedrich on 2014-12-05 11:36:27 +00:00
Thanks for no feedback. Closing this as it works for me.
Updated by dmikulski on 2015-07-03 15:28:59 +00:00
Hello dnsmichi,
sorry for this late feedback. I was really busy in the last month and so missed it. For general...it works! but...I've installed Version 1.12.2 about two month ago and now ran into trouble. The database grew about 2GB in this period of time and the transaction logs for db-backup grew much more.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/7362
Created by dmikulski on 2014-10-09 08:52:30 +00:00
Assignee: mfriedrich Status: Resolved (closed on 2014-12-05 11:36:27 +00:00) Target Version: 1.12 Last Update: 2015-07-03 15:28:59 +00:00 (in Redmine)
The column long_output in the icinga_notifications table is always filled with short output data. The output and long_output columns are both filled with the same content.
Can anyone change the line 1627 in [module/idoutils/src/idomod.c]()
to
and remove line 1626:
This should do the job.
Attachments
Changesets
2014-10-24 23:17:17 +00:00 by mfriedrich f7e744158bcfe4f78f7fcaa1473c20855e3239bd