Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This article describes how to monitor and troubleshoot Maestrano's infrastructure with New Relic






1 - Overview

Server monitoring enables you to supervise the actual infrastructure behind the applications

Drilling down to a specific server shows its details

2. Troubleshooting an alertĀ 

Severs alerts are related to either high CPU usage, memory usages, I/O or load.

Looking at the server by itself is usually not enough to understand the root cause of the issue, so it needs to be correlated to other events on the application side.

2.1 Non critical example: Memory Alert


Here, we have an alert on Memory usage on one of our servers, this is a none critical alert but we will make sure no action is needed.

From the Apps section, we can see that this is MnoHub.

Drilling down to processes helps us see what is going on

Everything looks fine, but to ensure business services are not impacted, we are going back to APMĀ 

All good.


  • No labels