Skip to content
NR1 application for exploring containers across accounts in New Relic.
JavaScript CSS
Branch: master
Clone or download
Latest commit b396078 Nov 13, 2019


GitHub release (latest SemVer including pre-releases) Snyk

View and manage millions of containers in context - in New Relic One.


Requires New Relic infrastructure agent to deployed on hosts that are running Docker containers.

This Nerdpack provides a launcher that gives you a global view of all of the containers in an account, which you can easily segment and drill down by tags. CPU, Memory and Disk I/O is presented in a space efficient heat map:


In the entity explorer, we provide a nerdlet that will show all of the containers that are running for a selected APM application (service). If the infrastructure data is coming from a different account, we automatically detect that and present the container telemetry in-context.

Click on a node in the heatmap to see details about that container, and jump to its host in the entity explorer.

Open Source License

This project is distributed under the Apache 2 license.

What do you need to make this work?

New Relic Infrastructure agent deployed on any host you want to monitor.


We generate per-container CPU etc by summarizing all processes in a given containerId. For example, this query will report CPU for a single container for the last minute:

SELECT sum(cpuPercent) FROM ProcessSample WHERE containerId = '${containerId}'
    SINCE 1 minute ago UNTIL 30 seconds ago

However: This will report an accurate value only if the agent reports one ProcessSample per process every 30 seconds. If the agent reports once every 15 second, then we would get 2x the value for this query. I'm looking to add a capability to estimate the reporting rate per process per container, but note that this reporting rate can vary by host depending on agent config.

If a set of viewed containers all report a the same rate heatmap colorization will be consistent irrespective of an agent's reporting rate. But the reported absolute values may be off.

The infrastructure team is working on agent changes that will properly report by container, at which point we can convert to using that data.

Getting started

First, ensure that you have Git and NPM installed. If you're unsure whether you have one or both of them installed, run the following command(s) (If you have them installed these commands will return a version number, if not, the commands won't be recognized):

git --version
npm -v

Next, clone this repository and run the following scripts:

git clone
cd nr1-container-explorer
npm install
npm start

Visit, navigate to the Nerdpack, and

Deploying this Nerdpack

Open a command prompt in the nerdpack's directory and run the following commands.

# this is to create a new uuid for the nerdpack so that you can deploy it to your account
nr1 nerdpack:uuid -g [--profile=your_profile_name]
# to see a list of APIkeys / profiles available in your development environment, run nr1 credentials:list
nr1 nerdpack:publish [--profile=your_profile_name]
nr1 nerdpack:deploy [-c [DEV|BETA|STABLE]] [--profile=your_profile_name]
nr1 nerdpack:subscribe [-c [DEV|BETA|STABLE]] [--profile=your_profile_name]

Visit, navigate to the Nerdpack, and


New Relic has open-sourced this project. This project is provided AS-IS WITHOUT WARRANTY OR SUPPORT, although you can report issues and contribute to the project here on GitHub.

Please do not report issues with this software to New Relic Global Technical Support.


New Relic hosts and moderates an online forum where customers can interact with New Relic employees as well as other customers to get help and share best practices. Like all official New Relic open source projects, there's a related Community topic in the New Relic Explorers Hub. You can find this project's topic/threads here: (Note: URL subject to change before GA)

Issues / Enhancement Requests

Issues and enhancement requests can be submitted in the Issues tab of this repository. Please search for and review the existing open issues before submitting a new issue.


Contributions are welcome (and if you submit a Enhancement Request, expect to be invited to contribute it yourself 😁). Please review our Contributors Guide.

Keep in mind that when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. If you'd like to execute our corporate CLA, or if you have any questions, please drop us an email at

You can’t perform that action at this time.