Is your feature request related to a problem?
Currently, SigNoz’s webhook notification channel sends a fixed JSON payload that follows the Alertmanager schema.
However, some notification targets — such as WeCom (WeChat Work), DingTalk, and Feishu — require specific message formats or field names (for example, msgtype, markdown.content, etc.).
Without the ability to define a custom payload body or template, it’s not possible to directly send alerts to these services without introducing an extra relay server, which increases complexity and maintenance overhead in restricted network environments (e.g., China mainland).
Describe the solution you'd like
Add support for custom webhook payload templates in alert channel configuration, similar to what Prometheus Alertmanager or Grafana provides.
For example:
Allow users to define a text or JSON template in the webhook channel settings.
Expose alert context variables like {{ .Status }}, {{ .Labels.alertname }}, {{ .Annotations.description }}, etc.
Render this template as the actual HTTP body for the POST request.
Example expected configuration:
type: webhook
url: https://example.com/wecom/bot
method: POST
headers:
Content-Type: application/json
bodyTemplate: |
{
"msgtype": "markdown",
"markdown": {
"content": "🚨 {{ .Labels.alertname }}\nStatus: {{ .Status }}\nSummary: {{ .Annotations.summary }}"
}
}
This would make SigNoz directly compatible with more webhook-based alerting systems without any relay.
Describe alternatives you've considered
Hosting a middle-layer HTTP relay to reformat payloads before forwarding to third-party chat systems.
Problem: Adds operational overhead, reliability risks, and isn’t feasible in some restricted environments.
Using email → webhook bridge services.
Problem: Not reliable and not suitable for enterprise internal use cases.
Additional context
Add any other context or screenshots about the feature request here.
Grafana, Alertmanager, and Zabbix all provide customizable payload templates for webhook integrations.
Supporting this in SigNoz would significantly improve interoperability, especially for teams using WeCom, Feishu, or custom internal APIs.
Thank you for your feature request – we love each and every one!
Is your feature request related to a problem?
Currently, SigNoz’s webhook notification channel sends a fixed JSON payload that follows the Alertmanager schema.
However, some notification targets — such as WeCom (WeChat Work), DingTalk, and Feishu — require specific message formats or field names (for example, msgtype, markdown.content, etc.).
Without the ability to define a custom payload body or template, it’s not possible to directly send alerts to these services without introducing an extra relay server, which increases complexity and maintenance overhead in restricted network environments (e.g., China mainland).
Describe the solution you'd like
Add support for custom webhook payload templates in alert channel configuration, similar to what Prometheus Alertmanager or Grafana provides.
For example:
Allow users to define a text or JSON template in the webhook channel settings.
Expose alert context variables like {{ .Status }}, {{ .Labels.alertname }}, {{ .Annotations.description }}, etc.
Render this template as the actual HTTP body for the POST request.
Example expected configuration:
type: webhook
url: https://example.com/wecom/bot
method: POST
headers:
Content-Type: application/json
bodyTemplate: |
{
"msgtype": "markdown",
"markdown": {
"content": "🚨 {{ .Labels.alertname }}\nStatus: {{ .Status }}\nSummary: {{ .Annotations.summary }}"
}
}
This would make SigNoz directly compatible with more webhook-based alerting systems without any relay.
Describe alternatives you've considered
Hosting a middle-layer HTTP relay to reformat payloads before forwarding to third-party chat systems.
Problem: Adds operational overhead, reliability risks, and isn’t feasible in some restricted environments.
Using email → webhook bridge services.
Problem: Not reliable and not suitable for enterprise internal use cases.
Additional context
Add any other context or screenshots about the feature request here.
Grafana, Alertmanager, and Zabbix all provide customizable payload templates for webhook integrations.
Supporting this in SigNoz would significantly improve interoperability, especially for teams using WeCom, Feishu, or custom internal APIs.
Thank you for your feature request – we love each and every one!