newkidd2 wrote:
To my knowledge, Orion does not use the ${Status} variable that is in the Subject line. It merely uses it for displaying the status of the interface at the time the alert was generated. I concur with my fellow Thwackers who stated that Orion probably that the problem may be with the alert as it has been configured.
Sorry, but the point of the alert is exactly to tell me what the status of the interface is at the time the alert was generated. If you look at the alert I have configured, you'll see that the criteria matches -- the interface is in WARNING, which is not Up or Unknown. I'm kind of at a loss at to what you mean by your statement -- why would you not want the alert to be the status of the interface when the alert was generated, if the criteria matches the alert?
newkidd2 wrote:
By the way, what does the status in the subject line reads? This might give us an idea of what Orion is reporting. Also, I must say..., when I saw the screenshot you provided, it made me think that Orion detected an "unknown status" briefly for the interface. So, it alerted on the "unknown status", but very likely, by the time you got a chance to check the device in SW, its status had gone to Normal. This seems to me the more likely scenario.
The Alert subject line says:
Warning : bridgewave-low-B -
My question is why was it in Warning. There is no indication anywhere that it ever went into "Unknown" status. I have received Unknown alerts before from other nodes. If this is in fact an Unknown issue, Solarwinds needs to address an issue with their alerting engine.