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: Use API to update alert channels

feature-request
feature-idea
rfb

#1

https://rpm.newrelic.com/api/explore/alerts_channels/create

We would like to be able to update Alert channels via a PUT call to the API. Example use cases would be updating the recipients for an email channel or the webhook URL for a Slack channel.

This is especially problematic with Terraform, which has to destroy then re-create channels when any parameter is changed.

Thanks,
Ron Lipke
Gannett/USA Today


New Relic edit

  • I want this, too
  • I have more info to share (reply below)
  • I have a solution for this

0 voters

We take feature ideas seriously and our product managers review every one when plotting their roadmaps. However, there is no guarantee this feature will be implemented. This post ensures the idea is put on the table and discussed though. So please vote and share your extra details with our team.


#2

Interesting use case, @rlipke! Thanks for posting it here in the community so we can collect interest around this via votes! Please add yours as well! :blush:


#3

I signed up because I hit exactly this and chased it for a while. To make terraform useful here we really need a PUT to update an existing channel, but we also need GET to return configuration so that we can compare it to what we expect.

At the moment an example GET return is:
{
“id”: XXXX,
“name”: “Dev/Test Account”,
“type”: “pagerduty”,
“links”: {
“policy_ids”: [
YYYY
]
}
}

and as you can see does not return the pagerduty service id. This means that terraform is going to try and update this value every time because it doesn’t know what the old value is. Though as mentioned, this is still better than the current situation which has to recreate the object and thus destroy the links to policies.

I’m going to preempt the “but security” response with the caveat that i don’t care if you send me back the actual key, you can hash it, or whatever scheme you like. I just need a way to verify that the newrelic configuration is the same as what i think it is.

Note that you can always tell that data like this is needed when:
GET https://alerts.newrelic.com/internal_api/v3/accounts/XXX/channels/YYY
and
PUT https://alerts.newrelic.com/internal_api/1/accounts/XXX/channels/YYY
provide exactly what we need, but are internal only. Please don’t cripple the public APIs.


#4

Corresponding terraform issue: https://github.com/terraform-providers/terraform-provider-newrelic/issues/5


#5

I’m after this feature as well, I am planning on writing an Ansible module for managing New Relic alerts and hence an update endpoint would be super useful.


#6

Thank you for sharing your use case with us, @David.ReedFrancis! I will pass along your input to our Alerts Product manager. Be sure to also vote in the thread above! :blush:


#7

Any updates on this? It’s a pain having to manage alerts in terraform without this.


#8

Hey @Hoshang.Sadiq No updates right now but I’ll get your +1 added. :slight_smile:


#9

Bump - would be very useful to have this and a GET by ID for managing alerts/notification channels.


#10

Thanks @duncan.sommerville - I’ll get your +1 added here :slight_smile:


#11

Nearly two years later… can I add a +100? :slight_smile:


#12

Hey @volte - sorry that we have no update right now - I’ll get your +100 added here!


#13

Thanks Ryan! That +100 should move it up the list of priorities, right? :wink:


#14

I hope so too :crossed_fingers: