Is your feature request related to a problem?
Please describe.
With Atlassian officially deprecating standalone Opsgenie and merging its incident management capabilities directly into Jira Service Management (JSM), the existing Opsgenie alert channel in SigNoz will eventually become obsolete for teams migrating to the consolidated Atlassian platform. Currently, routing logs and critical alerts natively to JSM requires custom webhook configurations that don't always parse cleanly into JSM's incident schema.
Describe the solution you'd like
I would like to request a native Alert Channel integration specifically for Jira Service Management (JSM). Similar to the existing Slack or PagerDuty integrations, this would allow users to input a JSM API token/webhook URL and seamlessly map SigNoz log alerts and metrics directly to JSM incident fields (e.g., Summary, Description, Priority, and custom labels).
Describe alternatives you've considered
Custom Webhooks: Manually configuring SigNoz webhooks to hit the JSM API, though this requires maintaining custom payload mapping.
Middleware Automation: Routing the SigNoz webhook payload through an external automation tool like n8n to catch, transform, and forward the data to JSM. While effective, an intermediate hop adds unnecessary complexity and potential points of failure for critical infrastructure alerts.
Additional context
Add any other context or screenshots about the feature request here.
Thank you for your feature request – we love each and every one!
Is your feature request related to a problem?
Please describe.
With Atlassian officially deprecating standalone Opsgenie and merging its incident management capabilities directly into Jira Service Management (JSM), the existing Opsgenie alert channel in SigNoz will eventually become obsolete for teams migrating to the consolidated Atlassian platform. Currently, routing logs and critical alerts natively to JSM requires custom webhook configurations that don't always parse cleanly into JSM's incident schema.
Describe the solution you'd like
I would like to request a native Alert Channel integration specifically for Jira Service Management (JSM). Similar to the existing Slack or PagerDuty integrations, this would allow users to input a JSM API token/webhook URL and seamlessly map SigNoz log alerts and metrics directly to JSM incident fields (e.g., Summary, Description, Priority, and custom labels).
Describe alternatives you've considered
Custom Webhooks: Manually configuring SigNoz webhooks to hit the JSM API, though this requires maintaining custom payload mapping.
Middleware Automation: Routing the SigNoz webhook payload through an external automation tool like n8n to catch, transform, and forward the data to JSM. While effective, an intermediate hop adds unnecessary complexity and potential points of failure for critical infrastructure alerts.
Additional context
Add any other context or screenshots about the feature request here.
Thank you for your feature request – we love each and every one!