New Community Ranking System
Our Community ranking system has recently been updated. You may notice changes in user rankings and receive system messages or notifications. If you have questions about how the new ranking works, please refer to the announcement post for more details (click here).
Anyone else frustrated by the way DCE logs events (alarms)?
EcoStruxure IT Forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Search in
Improve your search experience:
Exact phrase→Use quotes " "(e.g., "error 404")
Wildcard→Use * for partial words(e.g., build*, *tion)
AND / OR→Combine keywords(e.g., login AND error, login OR sign‑in)
Keep it short→Use 2–3 relevant words, not full sentences
Filters→Narrow results by section(Knowledge Base, Users, Products)
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-0512:13 AM. Last Modified: 2024-04-0412:58 AM
Anyone else frustrated by the way DCE logs events (alarms)?
DCE puts each alarm in its log with a START and an END time.
That sounds sort of interesting - except when you are trying to actually research an issue that has a lot of devices and events, it becomes confusing.
For instance -
"A discharged battery condition no longer exists" - That means that the system can't provide power - but the stat of this alarm is not the start of the incident. The incident started at some other time, this would likely be the recovery of the overall incident though.
"No longer on battery power" - This is a crucial alarm as it indicates when the power becomes unreliable and when it is reliable again - even if the UPS died in between
While the method used makes for a tidy log - it makes it hard to do forensics after the fact - as these events may cross over each other and weave in and out. the start times make not relate to the end times.
I'd also prefer that the ALARM text be what is recorded - not the RECOVERY text.
"UPS on Battery Power"
rather than the resolution - "No longer on Battery Power"
Anyone else run into this? I ended up finding it easier to go to each device and pulling the logs there and combining them myself - that defeats the purpose of having DCE.