AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.

    Skip to end of metadata
    Go to start of metadata

    The page covers how to use the Node Problem Viewer to troubleshoot node problems. 

    AppDynamics categorizes the ten items that deviate the most from the baseline performance as node problems. The Machine Agent must be installed on the machine hosting the node that you are troubleshooting.

    Using the Node Problem Viewer

    If accessed from the Snapshot viewer, the Node Problem viewer displays node problems for the time range of the snapshot. If accessed from the Node dashboard, the Noce Problem viewer uses the time range set in the Node dashboard. You can edit the time range in the Node Problem viewer and then apply the new time range. You can also define and save a custom time range.

    The right panel of the Node Problem viewer displays the metrics that deviate the most from their baselines for the specified time range.

    On the left, you can set filters on what data appears. Options include:

    • The baseline to use to define node problems.
    • The type of metrics, whether custom, hardware metrics, JVM, and so on.
    • Specify whether to display problems with values that are:

      • higher than baseline
      • lower than the baseline
      • higher and lower than baseline

      For example, if you are only interested in CPU that is too high, set the Analysis Type to Higher for Hardware Resources. On the other hand, if you want to monitor the load on your machine continuously because low CPU usage would also be a problem, set the Analysis Type to Higher and Lower. The right panel shows the ten items that deviate the most from the baseline.

    After changing an option, click the Analyze Node Problems button to apply the change.

    • No labels