Skip to main content

Hi PagerDuty team! 👋

I'm trying to get custom details from Grafana alerts to display in our Slack notifications, but only seeing basic information.

Current Setup:

  • ✅ Grafana → PagerDuty integration working (using Events API V2)
  • ✅ PagerDuty → Slack integration connected (service: my-service-prod → channel: #team-alerts)
  • ✅ Alerts are flowing through successfully

The Issue: Our Grafana alerts send rich custom details to PagerDuty (verified in PagerDuty incident view):

  • severity: "critical"
  • namespace: "production"
  • pod: "api-service-7d9c5-xyz"
  • cluster: "us-west-2-prod"
  • component: "api-service"
  • description: "Pod is in CrashLoopBackOff state..."
  • runbook_url: "https://wiki.internal/runbooks/..."

However, in Slack we only see:

🔴 Pod CrashLoopBackOff Alert
Service: my-service-prod
Urgency: Low
[Acknowledge] [Resolve]

What We Need: Display the custom_details fields in Slack notifications so our on-call engineers can see critical context without clicking through to PagerDuty.

What I've Tried:

  1. Configured PagerDuty contact point in Grafana with Details fields mapped to templates like {{ .CommonLabels.namespace }}
  2. Checked Slack integration settings in PagerDuty (Extensions → Slack → View)
  3. The configuration UI only shows basic options (thread creation, channel selection) but no options for enabling custom details display

Questions:

  1. Is there a way to enable custom details display in the current Slack integration?
  2. Do we need to upgrade to a different Slack integration version or add Slack V2 app?
  3. Can Event Orchestration be used to enrich Slack messages with custom_details?
  4. Is there an API endpoint or webhook approach for more control over Slack message formatting?

Environment: Using standard PagerDuty Slack integration Service: my-service-prod Integration Key: Events API V2

Any guidance would be greatly appreciated! Looking to display the custom metadata our monitoring system sends to help reduce MTTR. 🙏

 

Hey ​@soumyajyotiii 👋 I hope you are doing well!

 

By default, PagerDuty keeps Slack notifications as simple as possible to avoid overwhelming channels with too much info. This tends to be a case for teams with a high alert volume. So that notification cannot be customised.

 

However there are other ways that you can get access to your custom_details fields without having to leave Slack:

  1. Leverage the /pd {custom field name} to view/edit any custom field. This is documented on our actions list
  2. You can configure an incident workflow that can either be triggered manually by the /pd workflow or automatically depending on incident conditions that will send a message to a slack channel of choice with your custom_details fields

Please, let me know if these ways helped with your issue! Have an amazing day 😁

Hey ​@danieljcafonso 

I would like to use this method to get to our {custom field name} but I may be missing some syntax.

I tried /pd customfieldname - but was just prompted for what do you want to do?  

Any thoughts on what I need to do to use this?

I can see all the “available” commands, but that one is not listed for me:

 

Hey ​@jalley01 

I hope you are doing well today! in order to leverage the /pd {customfieldname} command like the "ack", "note", "resolve", etc  you need to use it on the incident dedicated channel. Trying to run this command elsewhere won't have the context of which incident you are referring to.

If you are already trying to do this on an incident dedicated channel and is not working then it might be a scenario of white spaces between words. In those cases, just replace the white spaces with an "_" and it will work. E.g. /pd customers_impacted

Let me know if this helped! Have a great day 😁

Terms & ConditionsCookie settingsAccessibility statement