Jump to content

New Relic Integration?


Recommended Posts

Hi Team,

We've run into a few issues and are wanting to setup external monitoring on our Vodia servers.

I can see that there is a section to input a new relic license key?
Can you provide some further information on how to setup the new relic integration?

Link to comment
Share on other sites

Hi DanielA 

This is a very simple set up, You will need a New Relic license key from https://newrelic.com/, you can then plug the license key in the vodia phone system. 

You should be able to see traffic coming vodia ---> New Relic 

If you run into to any issues, check the logfile in the vodia phone system https://doc.vodia.com/docs/admin-logfile



Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...
On 7/3/2021 at 2:31 AM, Vodia support said:


This is a very simple set up, You will need a New Relic license key from https://newrelic.com/, you can then plug the license key in the vodia phone system. 


Hi Team,

As previously mentioned, the keys available from newrelic do not validate in the license key field.
Over-riding the pattern match on the field to add any of the available license keys from new relic also does not work.

Any update/feedback on how to get this to work?

Link to comment
Share on other sites

The New Relic integration was done a few years ago, and since then we did not touch this area. We just post a JSON object to https://platform-api.newrelic.com/platform/v1/metrics and that seems to have worked for years.

Looking at https://docs.newrelic.com/docs/telemetry-data-platform/ingest-apis/report-metrics-metric-api/ it seems that the API that we are using should be still working, though in our account I was not able to get a new "Insights API key". There is a curl example on that page, if you find what API key works for you you can copy that key into the input field of the PBX and then it should work.

Link to comment
Share on other sites

Following the documentation you referred to - I was able to obtain an Insights Insert key.
Looks like these are handled @ https://insights.newrelic.com/ as they have not yet been added to the new dashboard layout.
Vodia still doesn't pattern match the key.

The issue I'm running into is that when Vodia attempts to post the data, I'm receiving a 403 forbidden response.

From the Vodia log:

POST /platform/v1/metrics HTTP/1.1
Host: platform-api.newrelic.com
X-License-Key: ****************
Content-Type: application/json
nAccept: application/json
Content-Length: 546

HTTP/1.1 403 Forbidden
Content-Length: 32
Date: Mon, 26 Jul 2021 00:19:17 GMT
Content-Type: text/plain; charset=utf-8
{"error": "Invalid license key"}

Looking at the Newrelic documentation - is the endpoint that vodia is using correct?
Newrelic docs show the endpoint as:


The docs also refer to the header value of "Api-Key" not "X-License-Key"



Required. The Insert API key authenticates you to use the Metric API. If this is provided as both a header and a query parameter, the values must match.

Link to comment
Share on other sites

Did not work... also tried a few other keys but still no luck. They must have changed their API 😆 seems Vodia is not the only one doing such things.

[9] 20210802173943: https:metric-api.newrelic.com: Send request (698 bytes)
POST /metric/v1 HTTP/1.1
Host: metric-api.newrelic.com
Content-Type: application/json
Accept: application/json
Content-Length: 516

{"agent":{"host":"TestServer","pid":"pbxctrl","version":"67.1"},"components":[{"name":"Debug System","guid":"com.vodia.pbx","duration":360,"metrics":{"Component/Traffic/SIP[packets/sec]":0,"Component/Traffic/HTTP[packets/sec]":24,"Component/Load/Media[usage]":[0,120,0,0,0],"Component/PBX/CDR[units]":113,"Component/PBX/Emails[units]":0,"Component/PBX/Uptime[sec]":9,"Component/PBX/Minutes[units]":9,"Component/PBX/Registrations[units]":0,"Component/PBX/Subscriptions[units]":0,"Component/PBX/Calls[units]":0}}]}
[9] 20210802173943: Initialize TLS connection
[9] 20210802173943: Received 298 bytes
HTTP/1.1 403 Forbidden
Date: Mon, 02 Aug 2021 21:39:43 GMT
Content-Type: text/plain;charset=UTF-8
Content-Length: 2
Connection: keep-alive
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 678a75e59839e708-EWR


Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...