All, has anyone seen an issue where email messages that Xymongenerates (NOTE: not the client status on the webpage, which is complete) are getting truncated beyond a certain length? We had already bumped up MAXMSG_STATUS and MAXMSG_CLIENT for a different issue (where the status messages going to the server were getting truncated), but this is different. For example, an alarm gets generated, and on the xymon webpage, you can see the entire status. The email we receive, however, is truncated. We're running Xymon 4.2.3 on RHEL5. We're trying to track down what layer this at, and it's proving a challenge. We're seeing this across different alarms, but they all seem to get truncated around 6kb.
Regards,
Mark
What does your alert config look like?
On Aug 23, 2010 7:47 PM, "Mark Stoltzfus" <mark.stoltzfus at pmigroup.com> wrote:
All, has anyone seen an issue where email messages that Xymongenerates (NOTE: not the client status on the webpage, which is complete) are getting truncated beyond a certain length? We had already bumped up MAXMSG_STATUS and MAXMSG_CLIENT for a different issue (where the status messages going to the server were getting truncated), but this is different. For example, an alarm gets generated, and on the xymon webpage, you can see the entire status. The email we receive, however, is truncated. We’re running Xymon 4.2.3 on RHEL5. We’re trying to track down what layer this at, and it’s proving a challenge. We’re seeing this across different alarms, but they all seem to get truncated around 6kb.
Regards,
Mark
We use a mix of alert scripts with a mix of instructions for different recipients, some written in PHP, some in bourne shell, that all show the same behavior. The hobbit-alerts.cfg is rather large (400+ lines), but a typical line looks like this:
PAGE=production
SCRIPT /opt/xymon/scripts/notify_unix.sh mark.stoltzfus at pmigroup.com DURATION>2m EXSERVICE=$NOC_IGNORE REPEAT=9999
Where NOC_IGNORE is set to services our NOC folks don't care about. Maybe a better question would be, does anyone get email alerts that are larger than 6kb?
Regards,
Mark
From: Josh Luthman [mailto:josh at imaginenetworksllc.com] Sent: Monday, August 23, 2010 4:52 PM To: xymon at xymon.com Subject: Re: [xymon] Truncated email alerts
What does your alert config look like?
On Aug 23, 2010 7:47 PM, "Mark Stoltzfus"<mark.stoltzfus at pmigroup.com> wrote:
All, has anyone seen an issue where email messages thatXymon generates (NOTE: not the client status on the webpage, which is complete) are getting truncated beyond a certain length? We had already bumped up MAXMSG_STATUS and MAXMSG_CLIENT for a different issue (where the status messages going to the server were getting truncated), but this is different. For example, an alarm gets generated, and on the xymon webpage, you can see the entire status. The email we receive, however, is truncated. We're running Xymon 4.2.3 on RHEL5. We're trying to track down what layer this at, and it's proving a challenge. We're seeing this across different alarms, but they all seem to get truncated around 6kb.
Regards,
Mark
participants (2)
-
josh＠imaginenetworksllc.com
-
mark.stoltzfus＠pmigroup.com