$CFID problem

3 messages in this thread

list Colin Coe · Fri, 6 Feb 2015 10:01:25 +0800 ·

Hi all

I;ve been trying to track done why some events cause two identical alerts
to be sent.  To help debugging, I added the CFID variable to the alerts and
the value was 151.  Line 151 is the "include" line :)

Any chance of getting Xymon to give the line number of the include file?

Thanks

list Japheth Cleaver · Thu, 5 Feb 2015 19:22:46 -0800 ·

▸ quoted from Colin Coe

On Thu, February 5, 2015 6:01 pm, Colin Coe wrote:

Hi all

I;ve been trying to track done why some events cause two identical alerts
to be sent.  To help debugging, I added the CFID variable to the alerts
and
the value was 151.  Line 151 is the "include" line :)

Any chance of getting Xymon to give the line number of the include file?

Thanks


That might be tricky, but the line numbers given from the --dump-config
option to xymond_alert will match up with the CFID given out there.
Perhaps that would be enough to track down the offending entry?

HTH,

-jc

list Colin Coe · Fri, 6 Feb 2015 12:54:19 +0800 ·

OK, you're now officially a legend.  Many thanks, that did it.

On Fri, Feb 6, 2015 at 11:22 AM, J.C. Cleaver <user-87556346d4af@xymon.invalid>

▸ quoted from Japheth Cleaver

wrote:

On Thu, February 5, 2015 6:01 pm, Colin Coe wrote:

Hi all

I;ve been trying to track done why some events cause two identical alerts
to be sent.  To help debugging, I added the CFID variable to the alerts
and
the value was 151.  Line 151 is the "include" line :)

Any chance of getting Xymon to give the line number of the include file?

Thanks


That might be tricky, but the line numbers given from the --dump-config
option to xymond_alert will match up with the CFID given out there.
Perhaps that would be enough to track down the offending entry?

HTH,

-jc

$CFID problem 🔗 link

$CFID problem