Skip to main content

Hey there,


I am developing a service that monitors my environment and sends pagers in case of an incident


I was going over PagerDuty docs and found that using the RestAPI the service will be able to raise an incident on any app using a single token so the incident will be less detailed (e.g. I wasn’t able to add links on an incident) while EventAPI can provide much detailed incident but requires a token per service which can be hard to manage in a large environments


My goal is to raise detailed incidents on any service using a single token


I feel like I am missing something.

can you tell me what is it?

Hello @shalom naim.


Thanks for reaching out. You are correct in your analysis and there is a clear trade-off depending on the path you choose.


For event ingestion and integration with other tools we typically recommend to go with Events API because it is more performant and it facilitates the routing to the correct service due to how integration keys are setup.


If you have access to Event Orchestration in PagerDuty you can create an Event Orchestration and generate a generic integration key that you can use when you use Events API. This would give you a unique key for all your services…but then you would need to define the service routes in Event Orchestration to properly redirect the event to the correct service.


You can do this manually on the portal or automate it with the REST APIs or Terraform.


Let me know if this makes sense. Thanks!

Reply


Terms & ConditionsCookie settings