• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 12 replies
  • Subscribers 54 subscribers
  • Views 560 views
  • Users 0 members are here
Options
Related

Node is Critical - But Why??

jduehmig

I have a question/concern about navigating through the Orion alerts.  I'm probably missing something vary obvious, but I can't see it.  

I have a number of nodes (generally VM's) and a couple of groups (related to esxi hosts) that show as "critical".  However, when I drill down to the nodes themselves, there is nothing that pops out that says "this is why the node is critical."  If the CPU load and memory are within range, nothing in the default summary views pulls out what is triggering the alert.  Is it disk space?  Temp?  Hardware?  Nothing I click on or drill into seems to display the status of all monitored elements of a particular node.  

So, am I missing something or expecting too much?

Thanks,
Joe

Parents
  • 0

    1. Check Active Alerts for Specific Triggers

    • Go to Alerts & Activity > Active Alerts in Orion.
    • Look for any active alerts related to the specific node or group.
    • Clicking on an alert should provide details on what triggered it.

    2. Check Node Details View

    • Open the affected node’s details page.
    • Look at the All Applications, Hardware Health, Disk Volumes, and Interfaces sections.
    • Sometimes, an issue might be hiding in a subcomponent like disk space, fan speed, or power supply.

    3. Check the "Critical" Status Type

    • Nodes can be marked as critical for different reasons:
      • Custom thresholds exceeded (e.g., CPU, RAM, disk space).
      • Hardware failures (e.g., ESXi host issues).
      • Unacknowledged alerts (alerts may persist even if conditions return to normal).
      • Orion polling issues (could indicate a network issue affecting monitoring).
Reply
  • 0

    1. Check Active Alerts for Specific Triggers

    • Go to Alerts & Activity > Active Alerts in Orion.
    • Look for any active alerts related to the specific node or group.
    • Clicking on an alert should provide details on what triggered it.

    2. Check Node Details View

    • Open the affected node’s details page.
    • Look at the All Applications, Hardware Health, Disk Volumes, and Interfaces sections.
    • Sometimes, an issue might be hiding in a subcomponent like disk space, fan speed, or power supply.

    3. Check the "Critical" Status Type

    • Nodes can be marked as critical for different reasons:
      • Custom thresholds exceeded (e.g., CPU, RAM, disk space).
      • Hardware failures (e.g., ESXi host issues).
      • Unacknowledged alerts (alerts may persist even if conditions return to normal).
      • Orion polling issues (could indicate a network issue affecting monitoring).
Children
No Data

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 200,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification SolarWinds Lab Link Customer Portal
About THWACK Blogs Federal & Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2021 SolarWinds Worldwide, LLC. All Rights Reserved.