Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Newrelic condition_description field not present in OpsGenie Newrelic New integration templating


Setting a custom violation description in NewRelic does not seem to be accessible in the OpsGenie NewRelic New integration parsed variables. 

Is there a way to access this field from the payload sent by NewRelic using variable interpolation ?

{{ raw.payload.condition_description }}


2 answers

1 accepted

@Nick H helped confirm that the format for rendering the custom condition description is. 

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 03, 2023

Can you update the documentation below regarding custom attributes?
Integrate Opsgenie with New Relic Workflows | Opsgenie | Atlassian Support

0 votes
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 08, 2022 • edited

Hi @steven.falconieri ,

If this field / data is parsing in the payload, you should be able to extract it using either String Processing or Regex.

It would realistically depend on how the condition_description is parsing in the payload, but maybe try:



Feel free to also share a what the payload looks like in the Processed incomingData log either with a screenshot or copy/paste it here - as long as you are comfortable sharing.  

Thanks @Nick H , that suggestion definitely makes it much more obvious whats happening. 

It appears that although the payload being received includes the `condition_description` field it is is not part of the `_parsedData`. 

Might i suggest a feature request to include the raw payload in the parsed data or are there potential security implications in doing so. 

Parsed data
{ "_incomingData": { "_parsedData": {
"-originalTags": [ "og_priority:P2", "" ],
"target_name": "Transaction query",
"event_type": "INCIDENT",
"incident_id": "XXXX",
"target_link": "",
"_target_labels_map": {},
"delayIfDoesNotExists": "true",
"details": "Transaction query result is > 1.0 for 1 minutes on 'test og custom desc'",
"state": "open",
"condition_name": "test og custom desc",
"target_product": "NRQL",
"timestamp": "1646776273605",
"owner": "",
"severity": "CRITICAL",
"policy_url": "",
"-recipients": [],
"target_type": "Query",
"policy_name": "TEST",
"incident_url": "",
"priority": "CRITICAL",
"-teams": [],
"runbook_url": "null",
"-tags": [ "og_priority:P2", "" ],
"-target_labels": [ {} ] },
"integrationType": "NewRelicV2",
"integrationName": "NewRelic [dev]",
"integrationId": "xxxx",
"incomingDataId": "xxxx"
} }


Raw payload received
{ "_incomingData": { "integrationType": "NewRelicV2", "_payload": "
\"condition_name\":\"test og custom desc\",
\"condition_description\":\"This is a custom description field\",
\"details\":\"Transaction query result is > 1.0 for 1 minutes on 'test og custom desc'\",
\"open_violations_count\":{\"critical\":1,\"warning\":0},\"closed_violations_count\":{\"critical\":0,\"warning\":0},\"severity\":\"CRITICAL\",\"targets\":[{\"id\":\"Transaction\",\"name\":\"Transaction query\",\"link\":\"\",\"labels\":{},\"product\":\"NRQL\",\"type\":\"Query\"}],\"timestamp\":xxxxx,\"timestamp_utc_string\":\"2022-03-08, 21:51 UTC\",\"event_type\":\"INCIDENT\",\"version\":\"1.0\",\"violation_callback_url\":\"\",\"duration\":469,\"condition_family_id\":xxxxx,\"metadata\":{\"evaluation_system_source\":\"Willamette\"}},\"recipients\":\"\",\"tags\":\"og_priority:P2,\"}", "_httpParams": {}, "httpUrl": "/v2/json/newrelic", "incomingDataId": "xxxxx", "_httpHeaders": { "User-Agent": "okhttp/4.9.1", "X-Amz-Cf-Id": "xxxx", "X-Forwarded-For": "xxxx", xxxx, xxxx, xxxx", "Accept-Encoding": "gzip", "Content-Length": "xxx", "X-Amzn-Trace-Id": "Self=1-xxx-xxx;Root=1-xxxx-xxxx", "Content-Type": "application/json" } }, "_actionSource": { "_details": { "ownerType": "NewRelicV2", "clientIpAddress": "xxxx", "writeAccessGranted": "true", "configAccessGranted": "false", "deleteAccessGranted": "true", "ownerId": "xx-xxx", "ownerDomain": "integration", "readAccessGranted": "true" }, "type": "API" } }


Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 08, 2022

Thanks for sharing that. Based on the payload shared, you may be able to simply use:


to extract that field. If either of those suggestions do not work - feel free to open a ticket with support here:

You can even reference this Community post and Nick H., and I'll try to pick that up! We might need to take a deeper look into the account / logs. 

Thanks for the suggestion @Nick H but my testing with `{{condition_description}}` was unsuccessful. I have raised a support ticket OGSP-85926 as you suggested. 

Really appreciate the help on this. 

Like Nick H likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events