Inconsistency in Notification Email

[vinothsethuram]

This white space will not make any difference.

[abrist]

What type of checks are failing to send complete email messages? Is there any consistency>

[vinothsethuram]

Yes, there is inconsistency and that is the subject of this post too.. Posting again my very first post


1) Custom notification is working for few services,but not for all the services. For few services, custom notification is not sending emails.

2) For few services/host, critical/recovery emails were received without info. i.e email body is blank and few emails had partial info.

[abrist]

My apologies, as I may not have been clear. I was asking if there was any consistency to which services fail? Are the working service notifications similar, or does this just seem to be completely random?

[vinothsethuram]

Let me split into two

1) Custom Notification - Custom notification is working for few services always and not for rest of the services always

2) Alert Notification(Host down, Service failure). Few request has full data and few request has partial data(response).

[abrist]

1) Can you give me some examples of the checks that are failing to send proper notifications?

Few request has full data and few request has partial data(response).

2) Can you give me some examples of the the checks that have truncated statuses?

[vinothsethuram]

What kind of example? What kind of information you are expecting?

[abrist]

The check command, the text of the notification email, and a few examples of the returned output from the check status. I want to see the difference between a working notification and broken/truncated one. You may have a returned status string that contains some characters that are not getting parsed by the notification handlers correctly.
I would like to be able to reproduce the issue.