Comments
-
Do we get a discount for renewing or is that something that could possibly be considered?
-
Just a guess but this might be for their 'Ask a Question' achievement, lol.
-
Thanks for the follow up! We ended up changing the alerts to N=Generic;M=DateTime and so far that appears to be working for this client.
-
From the various interfaces I've checked, there appears to be no consistency. Some show off by several days, some show off by a few months. I've checked the dates they showed as triggered in the emails hoping there would be some kind of correlating alert in the logs, but there's nothing close to those dates or times. I am…
-
The one I tested on above alerted that morning, which is why I chose it. I was thinking along the same lines as you - hoping it was just stored information based on previous alert dates, but I've tested multiple interfaces and the date it throws out doesn't match up with any alerts, events or syslogs. No idea where it gets…
-
Unfortunately, I've been wrestling with this for roughly two months on and off - so I've had to rule out a number of issues already. The client's mail server appears to be a non-issue, the alert is set to trigger if a condition exists longer than 2 minutes (critical devices) - so delays shouldn't be a heavy issue and the…
-
I go to Alert Actions > Select the alert > Test > Execute. It's basically the same as simulate but generates what you would see in a real-world alert if it was triggered at that time.
-
I ran a test and got the following: So the first two Generic codes show the correct time, but the one using N=Alerting;M=AlertTriggerTime comes up with a completely random incorrect time.
-
All of the servers have been confirmed to be on the correct/same date and time already, so unfortunately its nothing simple like that. I'd have to imagine that the server knows the correct date/time since any time the client receives a real-world alert on their devices, the emails they receive have the current date/time,…
-
This is the executed test message I received: ALERT: Interface [location removed]-mx960-b-re0 - et-9/1/0 · 200G LAG Link#2 to [location removed]-mx960-b ae9 et-5/3/0 - [location removed]-8800-Trib C:6-1 on [location removed]-mx960-b-re0 is down at Sunday, October 31, 2021 8:04 PM Here is a screenshot of the email:
-
This is what I have in the subject ALERT: Interface ${N=SwisEntity;M=FullName} on ${N=SwisEntity;M=Node.Caption} is down at ${N=Alerting;M=AlertTriggerTime;F=DateTime} EDIT: See my reply below for the copy of the test email I recieved.
-
Forgot to mention, I checked the alert logs to see if its simply picking up the date for when the interface previously alerted, but I have nothing for October 21st. Like I said, a head scratcher.
