{"id":28423,"date":"2015-12-30T09:07:01","date_gmt":"2015-12-30T03:37:01","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=28423"},"modified":"2022-01-11T14:18:42","modified_gmt":"2022-01-11T08:48:42","slug":"docker-monitoring-using-new-relic","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/docker-monitoring-using-new-relic\/","title":{"rendered":"Docker Monitoring Using New Relic"},"content":{"rendered":"

In my last couple of blogs, I talked about Docker monitoring, why I would need Docker monitoring and how I can monitor Docker containers using AWS<\/a>, Ruxit<\/a> and Sysdig<\/a>. Today, we are going to talk about another such tool which most of us already know about which also provides Docker<\/a> monitoring. The tool is New Relic.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

How to go about starting the New Relic monitoring for Docker:<\/p>\n

Steps<\/strong><\/span><\/h3>\n

1. Firstly you would need to update your apt sources list which can be done by using the following command:<\/p>\n

[js]echo deb newrelic non-free >> \/etc\/apt\/sources.list.d\/newrelic.list[\/js]<\/p>\n

2. Next, is putting the authentication key for the source.list:<\/p>\n

[js]wget -O- https:\/\/download.newrelic.com\/548C16BF.gpg | apt-key add -[\/js]<\/p>\n

3. Now, just run the next two commands to install the New Relic agent.<\/p>\n

[js]apt-get update<\/p>\n

apt-get install newrelic-sysmond\u00a0[\/js]<\/p>\n

4. After this, you need to specify the license key. You can find it in account settings which you can find from the drop-down on the right top corner:
\n\"Docker
\nThere on the right-hand side you will find the License key:
\n\"Account
\nAfter you have your license, run the following command:<\/p>\n

[js]nrsysmond-config –set license_key=ddbf346exxxxxxxxxxxxxx47b1790c1cb96ed[\/js]<\/p>\n

4. The New Relic agent can now be started by using the command:<\/p>\n

[js]\/etc\/init.d\/newrelic-sysmond start[\/js]<\/p>\n

5. One last thing that’s\u00a0left\u00a0is creating a docker group if it does not exist already, adding the newrelic user to that group and then restarting the Docker service and New Relic agent which can be done by the following commands in sequence:<\/p>\n

[js]groupadd -r docker<\/p>\n

usermod -a -G docker newrelic<\/p>\n

service docker restart && \/etc\/init.d\/newrelic-sysmond restart[\/js]<\/p>\n

6. Also, I have run a simple ubuntu container in my host machine using the following command:
\n\"Screenshot
\nThen I have gone ahead and installed apache2 inside my container. The port mapping 80:80 maps the 80 port of my container with the port 80 of the host machine. What this means is any hit on the port 80 of the host machine will land on the port 80 of the container which should show the apache2 start page:
\n\"Screenshot<\/p>\n

Let’s head on to the New Relic Console<\/strong> to see what insights we have now:<\/h3>\n

When you open the New Relic console, simply click on the Servers\u00a0<\/strong>option as shown in the below image:
\n\"Account<\/p>\n

This will take you to the servers page where all your servers on which New Relic agent is running will be shown:
\n\"All<\/p>\n

I will click on the server apachecon<\/strong>. This is the server inside which our container is working. After clicking on this, it will open this specific server’s monitoring. In there we can see options like Overview, Processes and Docker. We are interested in these 3 options. We will go through them one by one.<\/p>\n

The overview gives you a brief of everything like in the image below which is self-descriptive:
\n\"Screenshot<\/p>\n

Now, Click on Processes and it will show you processes based on memory usage:
\n\"Screenshot<\/p>\n

If you wish to list processes based on CPU:
\n\"Screenshot<\/p>\n

Let’s now, head on to the Docker option and see what New Relic has for us. If you simple click on Docker it gives you a combined graph of all the containers:
\n\"Screenshot<\/p>\n

New Relic shows containers as a part of the image they were run. You can also view this as a table. So, it wont show you the container name here, rather show you the image name and now, if \u00a0you click on the image name:
\n\"Docker<\/p>\n

It shows you:
\n\"Screenshot<\/p>\n

The above is again very simple to understand. That is all this Docker option here gives us.\u00a0The information they provide on the containers is simply the cpu and memory. It is trivial to determine exactly what the container might be doing, like any regular server, it could be running anything. For example: If an image runs an application, you may want to run one of their APM agents for better insight. So, you could simply head on to plugins:
\n\"Docker<\/p>\n

It has almost every plugin available for you. You can use the search bar to search what you are looking for depending on what is running inside you container. You will need to install New Relic agent inside the container like we did on the host machine earlier and then integrate a plugin with it to see insights in the APM menu where data will be segregated according to server then container ID.
\n\"Screenshot<\/p>\n

You can select any plugin:
\n\"Plugin<\/p>\n

It will show you all the steps on how to go about it:
\n\"Screenshot<\/p>\n

So, New Relic can help you monitor your Docker container and give you insights in depth. A lot of features are yet to be integrated with New Relic specific to Docker. That should be happening anytime soon.<\/p>\n","protected":false},"excerpt":{"rendered":"

In my last couple of blogs, I talked about Docker monitoring, why I would need Docker monitoring and how I can monitor Docker containers using AWS, Ruxit and Sysdig. Today, we are going to talk about another such tool which most of us already know about which also provides Docker monitoring. The tool is New […]<\/p>\n","protected":false},"author":174,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":5},"categories":[1174,1],"tags":[248,1916,2918,1891,1883,2920,2594,2911,2412,2891,2917,2919],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/28423"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/174"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=28423"}],"version-history":[{"count":2,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/28423\/revisions"}],"predecessor-version":[{"id":54560,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/28423\/revisions\/54560"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=28423"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=28423"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=28423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}