Your data. Anywhere you go.

New Relic for iOS or Android

Download on the App Store    Android App on Google play

New Relic Insights App for iOS

Download on the App Store

Learn more

Close icon

Feature Idea: Custom Payload Variables



Any update on this? My team has a similar requirement for integrating NewRelic alerts into our centralised monitoring system.

Seems like a straight forward ask:

  1. allow custom payload to support nested references to $TARGETS, example: $TARGETS[0].name


  1. expose some other variable which holds the value for TARGETS name.

Understanding that these would probably only work is Alert Policy is set to “By condition and entity” if the user wants a single value instead of a list.


Hi @Alex_Pena! I see that you also have a support ticket open and are speaking directly to our Alerts experts regarding this. Once this gets all sorted, please come back to this thread and give us all (in the online technical community) the update regarding the progress! Thanks so much, hope to hear back soon.


Any update on this?

I’m doing an integration with various services and would be very useful if I could use Target [0] .name.


No update to share right now, @jefferson.silva! Thanks for sharing your use case—I am passing your input along to our product team right now. Thanks again and check back soon.


Any update on this ? I am trying to use Target[0].name as well for a integration.


Nothing to share on this today, @alohani! Thanks for letting us know you would also benefit from this. Please be sure to vote above and keep checking back. :blush:


Has this been implemented?


Not yet, @anthony.allen. If you have a use case to share, please feel free to reply to this thread. Also be sure to vote above! Thanks. :blush:


@Linds I am trying to build out a webhook to integrate with my companies ticketing system, and I need the application name ($TARGETS[0].name) to bind it to configuration item. The current setup slows down the time it takes to create a ticket due to it having to parse out the information that is needed from $TARGETS instead of just letting me send the necessary information in the original payload.


Great! @anthony.allen - adding this to the request I sent along for you yesterday. Thanks!


I need to be able to show the Entity that created the alert in a webhook payload. It apears from this thread that the TARGETS object contains tht info, but only as a JSON object and that there is no way of just extracting the Name property. If there is any way of achieving this please let me know.


Hey @mike.dymond - you can check out the docs on Custom Payloads to see what is currently supported;

There is currently no way to extract individual elements of the $TARGETS JSON segment.


Hello Folks,

I have a requirement where I would need to get the $TARGETS metric to our centralized monitoring system. I have a custom webhook which feeds alerts data to Insights. But the $TARGETS data is not populating in Insights when accessing the event in Insights. How do I get $TARGETS so I can add it to centralized monitoring system


Hi, @bala.narasimha.rao.a: The $TARGETS field is an array; it is not possible to send it directly to Insights. You will have to create your own API endpoint to receive the webhook from New Relic Alerts, turn the $TARGETS array into a delimited string or a collection of key-value pairs, then post it to Insights.


I challenge this premise that sending as an ‘array’ only and we have to codify stripping the component pieces apart is a valid fix. This is like saying we bought this great race car from you, but, we have to build our own engine. This seems to be more than just a minor miss in the solution.


Hi, @tim.davis: Unfortunately, I am not on the product team, so I cannot change how it works. I can certainly relay your feedback to the product team, but until they change its behavior, the only solution I know of is the above workaround.


Is this feature still unresolved?


Hi, There is a new feature in limited release that addresses this issue:


I checked the connect manual you sent me.
But it doesn’t contain any content that I can use the name of TARGETS like $ TARGETS [0] .name I was curious about.

Are you saying I can use $ TARGETS [0] .name if I use Connect?


New Relic Connect has a flatten_target option that changes the target(s) from an array to one or more root-level fields.