It seems like it was just yesterday that New Relic Infrastructure was released to the world. More and more customers are trying it out every day, and with good reason: New Relic Infrastructure makes monitoring health, configuration, and inventory changes so easy, those tasks actually become fun.

But we’re far from finished. Ever since last November’s launch, we have been listening to our customers tell us about the capabilities they’d like to see us add to make Infrastructure even more useful. Our developers have been busy adding new features designed to help surface potential problem areas that could keep your business applications from running at their full potential.

Here are three new alert features you’ll want to check out right away:

1. Host not reporting alert

SS1_screen-infra-host-not-reporting-bb

This one is big for obvious reasons. When a host stops responding, you need to know ASAP to prevent potential outages or slowdowns that could affect your applications. The host not responding alert can tell you when we are not receiving data from the Infrastructure agent on a given host. This could be because the agent process has stopped, the host went offline, or worse, the host has crashed for some reason.

In any case, the ability to detect when these problems occur can help you improve Mean Time To Repair (MTTR) and lessen the likelihood of missing a critical SLA. As your environment changes, our convenient tagging capability makes it easy to add or remove hosts dynamically from the alert condition, drastically reducing the amount of time spent on administration.

2. Process running alert

SS2_infra-process-running-filtered

Sometimes it’s useful to know when more processes are running than you would expect would be needed to support a given application. Conversely, too few processes running may indicate that the host is not operating as efficiently as it should. The new process running alert built into New Relic Infrastructure can help you stay on top of exactly how many—or how few—processes are running so you always know when things are outside of the norm.

Here too, our tagging capability makes it easy to create the process running alert for processes on a single host or a group of hosts, simply by matching a process-tag such as ‘command name’ or ‘user name’.

3. Memory % used alert

ss3

New Relic Infrastructure works across your entire host ecosystem. Whether your applications are running in the data center, in the cloud, or in a container, we let you track and monitor your memory utilization in real time.

But because memory resources can vary from system to system, it doesn’t always make sense to set static flags for exactly how much memory is used. The new memory % used alert condition can set thresholds based on a percentage instead a of static value, so you can know when all your different-sized hosts have the same % of memory remaining.

That’s important, because using too much memory on a host can lead to poor application performance, especially if you start paging. On the other hand, using too little memory on a consistent basis might mean you are under utilizing expensive resources that might be better employed elsewhere.

We have an absolutely amazing development team that work at a blazing pace, so if you have an idea for a new feature that would help you accelerate or protect the hosts that are at the core of your business, be sure to talk to your account executive or join the discussion in our Discussion Forums.

If you would like to see these new features in action, don’t miss our upcoming webcast: New Relic Infrastructure: Features Update April 2017. It’s scheduled for 10 a.m. Pacific Time (1 p.m. Eastern Time) on Wednesday, April 5th, 2017. Register today!

Additional resources:

Aaron Newcomb is a senior product marketing manager at New Relic. He has more than 20 years of IT industry experience. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!