Hello,
I'm attempting to create an alert checker for our router and switch power supplies. I seem to be part way there but am seeing some unexpected behaviour that I cannot explain.
I started with the test condition: sensor_event notequals ok and the associations are "or:" Sensor Description match PEM* Sensor Description match Power Supply 0 @* Sensor Description match Power Supply 1 @*
Here's a specific device inventory showing PEM 0 status is currently down:
It seems the last two associations don't mach anything and for some reason the PEM* association only matches the power supplies that are ok, not the one I want the alert for which is currently down. I've tried to match against "Power Supply" and that matches power supplies in my servers but they don't seem to have a status, more like a current sensor instead. I'm attempting to deal strictly with the power supplies in our Juniper routers and switches and from what I can tell they all have a status/sensor_event state.
I think the two "Power Supply 0 @*" associations should also match additional power supplies as shown in the list below taken from the hardware inventory and filtering for a description of Power Supply:
Clearly I'm missing something en the alert checker associations but I'll be darned if I can figure out what that is. I've tried to match on MIB as well but nothing seems to match those power supplies.
What am I missing here?
Thanks, Dave.
It's not really clear what the problem is, since the screenshots don't actually show anything wrong, and you've not screenshotted the actual alert associations, which would be the important part.
I have no idea what device the top screenshot is referring to, since it's not included and you've not said.
adam.
David Milton via observium wrote on 2024-03-17 20:47:
Hello,
I'm attempting to create an alert checker for our router and switch power supplies. I seem to be part way there but am seeing some unexpected behaviour that I cannot explain.
I started with the test condition: sensor_event notequals ok and the associations are "or:" Sensor Description match PEM* Sensor Description match Power Supply 0 @* Sensor Description match Power Supply 1 @*
Here's a specific device inventory showing PEM 0 status is currently down:
It seems the last two associations don't mach anything and for some reason the PEM* association only matches the power supplies that are ok, not the one I want the alert for which is currently down. I've tried to match against "Power Supply" and that matches power supplies in my servers but they don't seem to have a status, more like a current sensor instead. I'm attempting to deal strictly with the power supplies in our Juniper routers and switches and from what I can tell they all have a status/sensor_event state.
I think the two "Power Supply 0 @*" associations should also match additional power supplies as shown in the list below taken from the hardware inventory and filtering for a description of Power Supply:
Clearly I'm missing something en the alert checker associations but I'll be darned if I can figure out what that is. I've tried to match on MIB as well but nothing seems to match those power supplies.
What am I missing here?
Thanks, Dave.
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
Sorry Adam, I put the conditions and associations in words it the beginning of my email. Here's a screen shot:

On Mar 17, 2024, at 16:10, Adam Armstrong via observium observium@lists.observium.org wrote:
It's not really clear what the problem is, since the screenshots don't actually show anything wrong, and you've not screenshotted the actual alert associations, which would be the important part.
I have no idea what device the top screenshot is referring to, since it's not included and you've not said.
adam.
David Milton via observium wrote on 2024-03-17 20:47:
Hello,
I'm attempting to create an alert checker for our router and switch power supplies. I seem to be part way there but am seeing some unexpected behaviour that I cannot explain.
I started with the test condition: sensor_event notequals ok and the associations are "or:" Sensor Description match PEM* Sensor Description match Power Supply 0 @* Sensor Description match Power Supply 1 @*
Here's a specific device inventory showing PEM 0 status is currently down:
It seems the last two associations don't mach anything and for some reason the PEM* association only matches the power supplies that are ok, not the one I want the alert for which is currently down. I've tried to match against "Power Supply" and that matches power supplies in my servers but they don't seem to have a status, more like a current sensor instead. I'm attempting to deal strictly with the power supplies in our Juniper routers and switches and from what I can tell they all have a status/sensor_event state.
I think the two "Power Supply 0 @*" associations should also match additional power supplies as shown in the list below taken from the hardware inventory and filtering for a description of Power Supply:
Clearly I'm missing something en the alert checker associations but I'll be darned if I can figure out what that is. I've tried to match on MIB as well but nothing seems to match those power supplies.
What am I missing here?
Thanks, Dave.
observium mailing list -- observium@lists.observium.org mailto:observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org mailto:observium-leave@lists.observium.org
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
And the top screenshot is referring to the device sktn; our Saskatoon router.
On Mar 18, 2024, at 07:38, David Milton david@dmilton.ca wrote:
Sorry Adam, I put the conditions and associations in words it the beginning of my email. Here's a screen shot:
<association-ruleset.png>
On Mar 17, 2024, at 16:10, Adam Armstrong via observium observium@lists.observium.org wrote:
It's not really clear what the problem is, since the screenshots don't actually show anything wrong, and you've not screenshotted the actual alert associations, which would be the important part.
I have no idea what device the top screenshot is referring to, since it's not included and you've not said.
adam.
David Milton via observium wrote on 2024-03-17 20:47:
Hello,
I'm attempting to create an alert checker for our router and switch power supplies. I seem to be part way there but am seeing some unexpected behaviour that I cannot explain.
I started with the test condition: sensor_event notequals ok and the associations are "or:" Sensor Description match PEM* Sensor Description match Power Supply 0 @* Sensor Description match Power Supply 1 @*
Here's a specific device inventory showing PEM 0 status is currently down:
It seems the last two associations don't mach anything and for some reason the PEM* association only matches the power supplies that are ok, not the one I want the alert for which is currently down. I've tried to match against "Power Supply" and that matches power supplies in my servers but they don't seem to have a status, more like a current sensor instead. I'm attempting to deal strictly with the power supplies in our Juniper routers and switches and from what I can tell they all have a status/sensor_event state.
I think the two "Power Supply 0 @*" associations should also match additional power supplies as shown in the list below taken from the hardware inventory and filtering for a description of Power Supply:
Clearly I'm missing something en the alert checker associations but I'll be darned if I can figure out what that is. I've tried to match on MIB as well but nothing seems to match those power supplies.
What am I missing here?
Thanks, Dave.
observium mailing list -- observium@lists.observium.org mailto:observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org mailto:observium-leave@lists.observium.org
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
This device doesn't seem to have any status entities matching "Power Supply *" at all, though?
adam.
David Milton via observium wrote on 2024-03-18 12:40:
And the top screenshot is referring to the device sktn; our Saskatoon router.
On Mar 18, 2024, at 07:38, David Milton david@dmilton.ca wrote:
Sorry Adam, I put the conditions and associations in words it the beginning of my email. Here's a screen shot:
<association-ruleset.png>
On Mar 17, 2024, at 16:10, Adam Armstrong via observium observium@lists.observium.org wrote:
It's not really clear what the problem is, since the screenshots don't actually show anything wrong, and you've not screenshotted the actual alert associations, which would be the important part.
I have no idea what device the top screenshot is referring to, since it's not included and you've not said.
adam.
David Milton via observium wrote on 2024-03-17 20:47:
Hello,
I'm attempting to create an alert checker for our router and switch power supplies. I seem to be part way there but am seeing some unexpected behaviour that I cannot explain.
I started with the test condition: sensor_event notequals ok and the associations are "or:" Sensor Description match PEM* Sensor Description match Power Supply 0 @* Sensor Description match Power Supply 1 @*
Here's a specific device inventory showing PEM 0 status is currently down:
It seems the last two associations don't mach anything and for some reason the PEM* association only matches the power supplies that are ok, not the one I want the alert for which is currently down. I've tried to match against "Power Supply" and that matches power supplies in my servers but they don't seem to have a status, more like a current sensor instead. I'm attempting to deal strictly with the power supplies in our Juniper routers and switches and from what I can tell they all have a status/sensor_event state.
I think the two "Power Supply 0 @*" associations should also match additional power supplies as shown in the list below taken from the hardware inventory and filtering for a description of Power Supply:
Clearly I'm missing something en the alert checker associations but I'll be darned if I can figure out what that is. I've tried to match on MIB as well but nothing seems to match those power supplies.
What am I missing here?
Thanks, Dave.
observium mailing list --observium@lists.observium.org To unsubscribe send an email toobservium-leave@lists.observium.org
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
There are two different classes of devices. The routers all have power supplies marked as PEM N where N can be anything from 0 through 6. The switches have Power Supplies with indicators as Power Supply N @ something as shown below. I was hoping to create a single checker that worked for both. Regardless, I still have the problem where the currently down status indicator PEM 0 does not seem to be matching either.

Here's the status indicators from one of our switches regn-sw1. There are more examples like this for other devices as well. 
On Mar 18, 2024, at 07:46, Adam Armstrong via observium observium@lists.observium.org wrote:
This device doesn't seem to have any status entities matching "Power Supply *" at all, though?
adam.
David Milton via observium wrote on 2024-03-18 12:40:
And the top screenshot is referring to the device sktn; our Saskatoon router.
On Mar 18, 2024, at 07:38, David Milton david@dmilton.ca mailto:david@dmilton.ca wrote:
Sorry Adam, I put the conditions and associations in words it the beginning of my email. Here's a screen shot:
<association-ruleset.png>
On Mar 17, 2024, at 16:10, Adam Armstrong via observium observium@lists.observium.org mailto:observium@lists.observium.org wrote:
It's not really clear what the problem is, since the screenshots don't actually show anything wrong, and you've not screenshotted the actual alert associations, which would be the important part.
I have no idea what device the top screenshot is referring to, since it's not included and you've not said.
adam.
David Milton via observium wrote on 2024-03-17 20:47:
Hello,
I'm attempting to create an alert checker for our router and switch power supplies. I seem to be part way there but am seeing some unexpected behaviour that I cannot explain.
I started with the test condition: sensor_event notequals ok and the associations are "or:" Sensor Description match PEM* Sensor Description match Power Supply 0 @* Sensor Description match Power Supply 1 @*
Here's a specific device inventory showing PEM 0 status is currently down:
It seems the last two associations don't mach anything and for some reason the PEM* association only matches the power supplies that are ok, not the one I want the alert for which is currently down. I've tried to match against "Power Supply" and that matches power supplies in my servers but they don't seem to have a status, more like a current sensor instead. I'm attempting to deal strictly with the power supplies in our Juniper routers and switches and from what I can tell they all have a status/sensor_event state.
I think the two "Power Supply 0 @*" associations should also match additional power supplies as shown in the list below taken from the hardware inventory and filtering for a description of Power Supply:
Clearly I'm missing something en the alert checker associations but I'll be darned if I can figure out what that is. I've tried to match on MIB as well but nothing seems to match those power supplies.
What am I missing here?
Thanks, Dave.
observium mailing list -- observium@lists.observium.org mailto:observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org mailto:observium-leave@lists.observium.org
observium mailing list -- observium@lists.observium.org mailto:observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org mailto:observium-leave@lists.observium.org
observium mailing list -- observium@lists.observium.org mailto:observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org mailto:observium-leave@lists.observium.org
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
There's not really anything complicated going on with the associations. It just converts * to % and then dumps it into a SQL LIKE statement.
The last two entries are just not matching anything in the SQL query, try a different strategy to match them.
Personally I'd match ( JUNIPER-MIB AND ( PEM* OR Power Supply*) ) or something like that. The shorter the match the less likely it'll break (and including the MIB means you don't have to be too specific)
adam.
David Milton via observium wrote on 2024-03-17 20:47:
Hello,
I'm attempting to create an alert checker for our router and switch power supplies. I seem to be part way there but am seeing some unexpected behaviour that I cannot explain.
I started with the test condition: sensor_event notequals ok and the associations are "or:" Sensor Description match PEM* Sensor Description match Power Supply 0 @* Sensor Description match Power Supply 1 @*
Here's a specific device inventory showing PEM 0 status is currently down:
It seems the last two associations don't mach anything and for some reason the PEM* association only matches the power supplies that are ok, not the one I want the alert for which is currently down. I've tried to match against "Power Supply" and that matches power supplies in my servers but they don't seem to have a status, more like a current sensor instead. I'm attempting to deal strictly with the power supplies in our Juniper routers and switches and from what I can tell they all have a status/sensor_event state.
I think the two "Power Supply 0 @*" associations should also match additional power supplies as shown in the list below taken from the hardware inventory and filtering for a description of Power Supply:
Clearly I'm missing something en the alert checker associations but I'll be darned if I can figure out what that is. I've tried to match on MIB as well but nothing seems to match those power supplies.
What am I missing here?
Thanks, Dave.
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
I ended up changing the alert type to a status check rather than a sensor check and that matches the items I want.
On Mar 18, 2024, at 11:01, Adam Armstrong via observium observium@lists.observium.org wrote:
There's not really anything complicated going on with the associations. It just converts * to % and then dumps it into a SQL LIKE statement.
The last two entries are just not matching anything in the SQL query, try a different strategy to match them.
Personally I'd match ( JUNIPER-MIB AND ( PEM* OR Power Supply*) ) or something like that. The shorter the match the less likely it'll break (and including the MIB means you don't have to be too specific)
adam.
David Milton via observium wrote on 2024-03-17 20:47:
Hello,
I'm attempting to create an alert checker for our router and switch power supplies. I seem to be part way there but am seeing some unexpected behaviour that I cannot explain.
I started with the test condition: sensor_event notequals ok and the associations are "or:" Sensor Description match PEM* Sensor Description match Power Supply 0 @* Sensor Description match Power Supply 1 @*
Here's a specific device inventory showing PEM 0 status is currently down:
It seems the last two associations don't mach anything and for some reason the PEM* association only matches the power supplies that are ok, not the one I want the alert for which is currently down. I've tried to match against "Power Supply" and that matches power supplies in my servers but they don't seem to have a status, more like a current sensor instead. I'm attempting to deal strictly with the power supplies in our Juniper routers and switches and from what I can tell they all have a status/sensor_event state.
I think the two "Power Supply 0 @*" associations should also match additional power supplies as shown in the list below taken from the hardware inventory and filtering for a description of Power Supply:
Clearly I'm missing something en the alert checker associations but I'll be darned if I can figure out what that is. I've tried to match on MIB as well but nothing seems to match those power supplies.
What am I missing here?
Thanks, Dave.
observium mailing list -- observium@lists.observium.org mailto:observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org mailto:observium-leave@lists.observium.org
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
Oh, lol.
Yeah, you're not going to match statuses if your alert type is set to sensor :D
adam.
David Milton via observium wrote on 2024-03-18 17:05:
I ended up changing the alert type to a status check rather than a sensor check and that matches the items I want.
On Mar 18, 2024, at 11:01, Adam Armstrong via observium observium@lists.observium.org wrote:
There's not really anything complicated going on with the associations. It just converts * to % and then dumps it into a SQL LIKE statement.
The last two entries are just not matching anything in the SQL query, try a different strategy to match them.
Personally I'd match ( JUNIPER-MIB AND ( PEM* OR Power Supply*) ) or something like that. The shorter the match the less likely it'll break (and including the MIB means you don't have to be too specific)
adam.
David Milton via observium wrote on 2024-03-17 20:47:
Hello,
I'm attempting to create an alert checker for our router and switch power supplies. I seem to be part way there but am seeing some unexpected behaviour that I cannot explain.
I started with the test condition: sensor_event notequals ok and the associations are "or:" Sensor Description match PEM* Sensor Description match Power Supply 0 @* Sensor Description match Power Supply 1 @*
Here's a specific device inventory showing PEM 0 status is currently down:
It seems the last two associations don't mach anything and for some reason the PEM* association only matches the power supplies that are ok, not the one I want the alert for which is currently down. I've tried to match against "Power Supply" and that matches power supplies in my servers but they don't seem to have a status, more like a current sensor instead. I'm attempting to deal strictly with the power supplies in our Juniper routers and switches and from what I can tell they all have a status/sensor_event state.
I think the two "Power Supply 0 @*" associations should also match additional power supplies as shown in the list below taken from the hardware inventory and filtering for a description of Power Supply:
Clearly I'm missing something en the alert checker associations but I'll be darned if I can figure out what that is. I've tried to match on MIB as well but nothing seems to match those power supplies.
What am I missing here?
Thanks, Dave.
observium mailing list --observium@lists.observium.org To unsubscribe send an email toobservium-leave@lists.observium.org
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
participants (2)
-
Adam Armstrong -
David Milton