# ElasticSearch plugin for newrelic

**URL:** <https://discuss.elastic.co/t/elasticsearch-plugin-for-newrelic/11298>\
**Category:** Elasticsearch\
**Created:** [March 25, 2013, 4:55pm UTC](https://discuss.elastic.co/t/elasticsearch-plugin-for-newrelic/11298 "2013-03-25T16:55:26Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vinicius\_Carvalho](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinicius_carvalho/32/770_2.png) [@Vinicius\_Carvalho](https://discuss.elastic.co/u/Vinicius_Carvalho)\
**Post date:** [March 25, 2013, 4:55pm UTC](https://discuss.elastic.co/t/elasticsearch-plugin-for-newrelic/11298/1 "2013-03-25T16:55:26Z")

</div>

Hi there. I'm finishing an elasticsearch to collect metrics from ES (using  
nodestats) and send to newrelic. Bigdesk is awesome, but we needed to have  
historical data, SPM is also fantastic, but would mean another cost on  
monitoring. So for those who use newrelic, you can find the plugin  
here: [https://github.com/viniciusccarvalho/elasticsearch-newrelic](https://github.com/viniciusccarvalho/elasticsearch-newrelic)

I'm still improving, I'd love to hear from the community. It's in a working  
stage, we have it deployed in our cluster in production sending data to  
newrelic. In the next few days I want to improve documentation and add  
some new features as well.

Hope to hear back from you guys.

Regards

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![polyfractal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/polyfractal/32/48162_2.png) [@polyfractal](https://discuss.elastic.co/u/polyfractal)\
**Post date:** [March 25, 2013, 5:43pm UTC](https://discuss.elastic.co/t/elasticsearch-plugin-for-newrelic/11298/2 "2013-03-25T17:43:37Z")

</div>

New Relic is a fantastic product - glad to see this ES being integrated!  
Good work =D

-Zach

On Monday, March 25, 2013 12:55:26 PM UTC-4, Vinicius Carvalho wrote:

> Hi there. I'm finishing an elasticsearch to collect metrics from ES (using  
> nodestats) and send to newrelic. Bigdesk is awesome, but we needed to have  
> historical data, SPM is also fantastic, but would mean another cost on  
> monitoring. So for those who use newrelic, you can find the plugin here:  
> [GitHub - viniciusccarvalho/elasticsearch-newrelic: Plugin to push elasticsearch data to newrelic](https://github.com/viniciusccarvalho/elasticsearch-newrelic)
> 
> I'm still improving, I'd love to hear from the community. It's in a  
> working stage, we have it deployed in our cluster in production sending  
> data to newrelic. In the next few days I want to improve documentation and  
> add some new features as well.
> 
> Hope to hear back from you guys.
> 
> Regards

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\
**Post date:** [March 25, 2013, 6:39pm UTC](https://discuss.elastic.co/t/elasticsearch-plugin-for-newrelic/11298/3 "2013-03-25T18:39:35Z")

</div>

if you haven't done so, would you mind opening a pull request adding this  
to the website?

simon

On Monday, March 25, 2013 5:55:26 PM UTC+1, Vinicius Carvalho wrote:

> Hi there. I'm finishing an elasticsearch to collect metrics from ES (using  
> nodestats) and send to newrelic. Bigdesk is awesome, but we needed to have  
> historical data, SPM is also fantastic, but would mean another cost on  
> monitoring. So for those who use newrelic, you can find the plugin here:  
> [GitHub - viniciusccarvalho/elasticsearch-newrelic: Plugin to push elasticsearch data to newrelic](https://github.com/viniciusccarvalho/elasticsearch-newrelic)
> 
> I'm still improving, I'd love to hear from the community. It's in a  
> working stage, we have it deployed in our cluster in production sending  
> data to newrelic. In the next few days I want to improve documentation and  
> add some new features as well.
> 
> Hope to hear back from you guys.
> 
> Regards

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Vinicius\_Carvalho](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinicius_carvalho/32/770_2.png) [@Vinicius\_Carvalho](https://discuss.elastic.co/u/Vinicius_Carvalho)\
**Post date:** [March 25, 2013, 6:53pm UTC](https://discuss.elastic.co/t/elasticsearch-plugin-for-newrelic/11298/4 "2013-03-25T18:53:33Z")

</div>

Hi Simon, just opened that. Thanks for pointing out. Amazing how you guys  
embrace community, I had no idea the whole website was driven by github 😃

Cheers

On Monday, March 25, 2013 2:39:35 PM UTC-4, simonw wrote:

> if you haven't done so, would you mind opening a pull request adding this  
> to the website?
> 
> simon
> 
> On Monday, March 25, 2013 5:55:26 PM UTC+1, Vinicius Carvalho wrote:
> 
> > Hi there. I'm finishing an elasticsearch to collect metrics from ES  
> > (using nodestats) and send to newrelic. Bigdesk is awesome, but we needed  
> > to have historical data, SPM is also fantastic, but would mean another cost  
> > on monitoring. So for those who use newrelic, you can find the plugin here:  
> > [GitHub - viniciusccarvalho/elasticsearch-newrelic: Plugin to push elasticsearch data to newrelic](https://github.com/viniciusccarvalho/elasticsearch-newrelic)
> > 
> > I'm still improving, I'd love to hear from the community. It's in a  
> > working stage, we have it deployed in our cluster in production sending  
> > data to newrelic. In the next few days I want to improve documentation and  
> > add some new features as well.
> > 
> > Hope to hear back from you guys.
> > 
> > Regards

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Accu\_Search](https://avatars.discourse-cdn.com/v4/letter/a/e0b2c6/32.png) [@Accu\_Search](https://discuss.elastic.co/u/Accu_Search)\
**Post date:** [May 14, 2013, 12:33am UTC](https://discuss.elastic.co/t/elasticsearch-plugin-for-newrelic/11298/5 "2013-05-14T00:33:25Z")

</div>

\*Hi \*Vinicius,  
\*  
\*  
\*Great work on new relic integration. It was quite easy to install and get  
it working. One of the issue that i am facing is with metric. I am using  
Elastic Search's Java TransportClient to query index. \*  
\*As per data from transport client the query takes between 10 ms to 50 ms  
but on checking average time in mills graph, hovering over the graph line  
shows that the request took seconds. \*  
_Attached is the screen shot. Are there any settings that i need to do in  
order to get the metrics correct? I had downloaded zip from gitbub on  
5/3/2013 built it using gradle._  
\*  
\*  
_Thanks_

On Monday, March 25, 2013 9:55:26 AM UTC-7, Vinicius Carvalho wrote:

> Hi there. I'm finishing an elasticsearch to collect metrics from ES (using  
> nodestats) and send to newrelic. Bigdesk is awesome, but we needed to have  
> historical data, SPM is also fantastic, but would mean another cost on  
> monitoring. So for those who use newrelic, you can find the plugin here:  
> [GitHub - viniciusccarvalho/elasticsearch-newrelic: Plugin to push elasticsearch data to newrelic](https://github.com/viniciusccarvalho/elasticsearch-newrelic)
> 
> I'm still improving, I'd love to hear from the community. It's in a  
> working stage, we have it deployed in our cluster in production sending  
> data to newrelic. In the next few days I want to improve documentation and  
> add some new features as well.
> 
> Hope to hear back from you guys.
> 
> Regards

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Eran\_Eidinger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eran_eidinger/32/44831_2.png) [@Eran\_Eidinger](https://discuss.elastic.co/u/Eran_Eidinger)\
**Post date:** [May 20, 2013, 7:55am UTC](https://discuss.elastic.co/t/elasticsearch-plugin-for-newrelic/11298/6 "2013-05-20T07:55:08Z")

</div>

Hello,

I'm very excited about this plugin for new relic, thanks alot for the effort!  
I installed it (and saw that it loads in the elasticsearch logs).

The endpoint \_newrelic is working fine:  
{  
configuration: {  
agents: {  
http: true  
pool: true  
transport: true  
fs: true  
indices: true  
network: true  
}  
refreshInterval: 10  
}  
}

However, in my new relic account I do not see those metrics as available. When I create a custom dashboard I only have four options:  
CPU  
GC  
Memory  
MemoryPool

There is no autocpmlete for indices, for example.

What can cause this? Is there something else I need to define after installing the plugin with:

bin/plugin -url file://${jar\_location} -install newrelic

and restarting the ES service?

---

<div class="post-metadata">

**Author:** ![Petrus\_Repo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/petrus_repo/32/2308_2.png) [@Petrus\_Repo](https://discuss.elastic.co/u/Petrus_Repo)\
**Post date:** [May 28, 2013, 2:26pm UTC](https://discuss.elastic.co/t/elasticsearch-plugin-for-newrelic/11298/7 "2013-05-28T14:26:48Z")

</div>

I had exactly the same problem!

The root cause was that plugin's install instructions don't assume that  
Elastic Search is ran as a service. Plugin's install instructions work only  
when ES is started in client mode with "bin/elasticsearch".

When Elastic Search is started as a service (eg. with  
/etc/init.d/elasticsearch), configuration in "bin/elasticsearch.in.sh" WILL  
NOT be read.

I added the "-javaagent" option to file "bin/service/elasticsearch.conf" as  
the last "additional parameter" as follows:  
wrapper.java.additional.10=-javaagent:%ES\_HOME%/newrelic/newrelic.jar

Another confusion was that ES analytics are only available as New Relic  
dashboard widgets, hence the default landing page for the ES' statistics is  
empty (I first thought my service wasn't being monitored at all). When  
creating the dashboard, you must _manually_ write the ES specific keyword  
(eg. "indices/") in the "metrics" field. The "metrics" list, which appears  
when clicking the input field, does _not_ include any ES specific  
categories before you have written one manually.

According to the plugin's README the available keywords for categories are:  
indices, pool, network, transport, http and filesystem.

I struggled with this problem, and this thread was the closest thing I  
found. I hope you'll get easier time by applying these findings! 🙂

Petrus Repo

On Monday, May 20, 2013 10:55:08 AM UTC+3, Eran wrote:

> Hello,
> 
> I'm very excited about this plugin for new relic, thanks alot for the  
> effort!  
> I installed it (and saw that it loads in the elasticsearch logs).
> 
> The endpoint \_newrelic is working fine:  
> {  
> configuration: {  
> agents: {  
> http: true  
> pool: true  
> transport: true  
> fs: true  
> indices: true  
> network: true  
> }  
> refreshInterval: 10  
> }  
> }
> 
> However, in my new relic account I do not see those metrics as available.  
> When I create a custom dashboard I only have four options:  
> CPU  
> GC  
> Memory  
> MemoryPool
> 
> There is no autocpmlete for indices, for example.
> 
> What can cause this? Is there something else I need to define after  
> installing the plugin with:
> 
> bin/plugin -url file://${jar\_location} -install newrelic
> 
> and restarting the ES service?
> 
> --  
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/ElasticSearch-plugin-for-newrelic-tp4032305p4035148.html](http://elasticsearch-users.115913.n3.nabble.com/ElasticSearch-plugin-for-newrelic-tp4032305p4035148.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 2:34am UTC](https://discuss.elastic.co/t/elasticsearch-plugin-for-newrelic/11298/8 "2017-07-06T02:34:22Z")

</div>


