-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpsGenie integration does not work when created via API. #59517
Comments
Assigning to @getsentry/support for routing ⏲️ |
Routing to @getsentry/product-owners-settings-integrations for triage ⏲️ |
Adding this to the backlog for investigating |
Any progress on this?
This is the body I used to create the integration. And this is the way I generate the exception.
|
Hi @m1n9o we don't have an update for this yet, it's in our backlog for investigation, is there any reason why you can't just create the integration in the Opsgenie app and use that key itself? |
Since Click-ops is not encouraged in our company. So we are going to design an internal platform to provision OpsGenie (and Sentry) resources with IaC (maybe pulumi/terraform/api). For our long term goal, this is important. |
Are there any updates on this issue? We are currently facing the same thing. To provide some extra information on our findings. Up until now we were using the legacy Opsgenie integration which seems to support communicating via integrations created using the Opsgenie API. Did something change where the current integration is doing some additional checks? Additionally it seems like the Opsgenie Integration when created using the parameter |
Hi @m1n9o and @martendeng, I tried the code provided above, and it works for me. After investigating, it seems that |
I am creating the integration manually in the UI as described in https://docs.sentry.io/organization/integrations/notification-incidents/opsgenie/ and https://support.atlassian.com/jira-service-management-cloud/docs/integrate-with-sentry/ and I am getting the error initially reported in pulumi/pulumi-opsgenie#203. I contacted Sentry support and they directed me to this GitHub issue (Case 132930). Is there a way to fix it or at least get more debug info? It appears this is the place in the code where the exception is thrown
Atlassian insists that hey key looks good to them |
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Expected Result
The integration in Sentry works and alerts messages are sent to opsenie when a rule is triggered.
Actual Result
No alert messages are sent.
Issue was initially raised in: pulumi/pulumi-opsgenie#203
Manually creating the integration in OpsGenie serves as a workaround, however there is not explanation at the moment on why the API-generated key does not.
@Dhrumil-Sentry mentions the user needs to created the integration via the UI. Is this a requirement? Is there an explanation on why this is the case?
Product Area
Settings - Integrations
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: