shinken-solutions/shinken

Output from another check used in notification

EChauve opened this issue · 1 comments

If this is not the right place to post this issue, please let me know.

Description :
A monitoring service became CRITICAL and a notification was sent. All fields of the notification were correctly filled except for the plugin output which seem to have been taken from a totally different monitoring service.
We are using Shinken 2.4.

What data would be required to further investigate this issue?
Has such a behavior been observed before?

k0ste commented

Paste your notification cfg.