REST API calls for New Relic Infrastructure alerts

You can manage individual Infrastructure and integrations alerting conditions directly within the New Relic Infrastructure UI. You can also use Infrastructure's REST API to add (PUT), update (POST), delete, and list (GET) alerting conditions.

REST API calls for Infrastructure alerts are not available in the API Explorer.

Requirements

In order to use the Infrastructure REST API, you need:

• The alerting condition's related policy_id from New Relic Alerts (available via GET list of conditions or via the New Relic Alerts REST API)
• The condition id (available via GET list of conditions, or via the condition's URL in the Infrastructure UI)
• Your Admin user's API key

Using Infrastructure API calls

Here are some basic cURL commands and their responses for Infrastructure alert conditions. Depending on the type of condition, the DATA information you provide in the call will vary for POST (add) and PUT (update) calls. Definitions of each attribute used in the data blocks can be found in the Definitions section.

GET Infrastructure conditions

You can either GET a list of Infrastructure conditions or GET a specific Infrastructure condition. Here are a few tips for listing Infrastructure conditions.

• For pagination, use limit (records per page) and offset (how many records to skip) parameters. Default is 50 records per page, and offset starts at 0 (skip no records).
• To scope the results to a specific policy, use policy_id.

GET a list of Infrastructure conditions

curl -v -X GET --header "X-Api-Key: admin_api_key" \
  "https://infra-api.newrelic.com/v2/alerts/conditions?policy_id=111111"

Example GET a list of conditions

Response showing 2 of the 3 conditions for the example policy (formatted for readability and truncated):

HTTP/1.1 200 OK
Content-Length: 622
Content-Type: application/json

{
   "data":[
      {
         "type":"infra_process_running",
         "name":"Java is running",
         "enabled":true,
         "where_clause":"(`hostname` LIKE '%cassandra%')",
         "id":13890,
         "created_at_epoch_millis":1490996713872,
         "updated_at_epoch_millis":1490996713872,
         "policy_id":111111,
         "comparison":"equal",
         "critical_threshold":{
            "value":0,
            "duration_minutes":6
         },
         "process_where_clause":"(`commandName` = 'java')"
      },
      {
         "created_at_epoch_millis": 1501704525462,
         "critical_threshold": {
             "duration_minutes": 5
         },
         "enabled": true,
         "filter": {
            "and": [
                {
                     "like": {
                         "fullHostname": "Production_1"
                     }
                 }
             ]
         },
         "id": 448036,
         "name": "PROD - Host Machine's Agent Not Responding ....",
         "policy_id": 98485,
         "type": "infra_host_not_reporting",
         "updated_at_epoch_millis": 1504879191220
      }
     . . . 
   ],
   "meta":{
      "limit":50,
      "offset":0,
      "total":3
   },
   "links":{
      "next":"infra-api.newrelic.com/v2/alerts/conditions?limit=1\u0026offset=50\u0026policy_id=111111"
   }
}

To get a list of the 10 Infrastructure conditions beyond the 50 limit:

curl -v -X GET --header "X-Api-Key: admin_api_key" \
  "https://infra-api.newrelic.com/v2/alerts/conditions?policy_id=111111&offset=50&list=10"

GET a specific Infrastructure condition

To get information about a single Infrastructure condition:

curl -v -X GET --header "X-Api-Key: admin_api_key" \
 "https://infra-api.newrelic.com/v2/alerts/conditions/condition-id"

Example GET a specific condition

Response (formatted for readability):

HTTP/1.1 200 OK
Content-Length: 246
Content-Type: application/json

{
   "data":{
      "type":"infra_host_not_reporting",
      "name":"demo condition",
      "enabled":false,
      "id":13887,
      "created_at_epoch_millis":1490981583580,
      "updated_at_epoch_millis":1490981583580,
      "policy_id":23635,
      "critical_threshold":{
         "duration_minutes":100
      }
   }
}

Create (POST) an Infrastructure condition

To add an Infrastructure condition, use this basic cURL command:

curl -X POST 'https://infra-api.newrelic.com/v2/alerts/conditions' \
     -H 'X-Api-Key:admin_api_key' -i \
     -H 'Content-Type: application/json' \
     -d \
'{
   "data":{DATA object details
      }
   }
}'

Include details in the DATA object (-d \ section) for the type of Infrastructure condition you are adding:

• Process running conditions API data
• Metric conditions API data
• Host not reporting conditions API data

Update (PUT) an Infrastructure condition

You only need to include the fields that need to be changed when updating an Infrastructure condition. The API keeps the existing values for any missing fields.

To update an Infrastructure condition, use this basic cURL command. To indicate which condition is to be updated, be sure to include the "id": .

Example update (PUT) a condition

curl -X PUT 'https://infra-api.newrelic.com/v2/alerts/conditions/condition-id' \
     -H 'X-Api-Key:admin_api_key' -i \
     -H 'Content-Type: application/json' \
     -d \
'{
   "data":{DATA object details
      }
   }
}'

Include details in the DATA object (-d \ section) for the type of Infrastructure condition you are updating:

• Process running conditions API data
• Metric conditions API data
• Host not reporting conditions API data

curl -v -X DELETE --header "X-Api-Key: admin_api_key" \
  "https://infra-api.newrelic.com/v2/alerts/conditions/condition_id"
      

"critical_threshold":{
   "value":<number>,
   "duration_minutes":<integer>,
   "time_function":"any" or "all"
},

"critical_threshold":{
   "value":<integer>,
   "duration_minutes":<integer>,
},

"critical_threshold":{
   "duration_minutes":<integer>,
},

{and: [{is: {ec2InstanceType: "m3.medium"}}]}

"[test] process running"

"commandName = '\''java'\''"

"(`hostname` LIKE '\''%cassandra%'\'')",