Skip to content
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

The title of incident without hostname and check name #5

Closed
pablolibo opened this issue Feb 8, 2019 · 2 comments
Closed

The title of incident without hostname and check name #5

pablolibo opened this issue Feb 8, 2019 · 2 comments

Comments

@pablolibo
Copy link
Contributor

Hi all,

I'm having a strange behavior about this handler to pagerduty, when sending the event is not included hostname and the check name of the alert like old version of handler pagerduty written in ruby.

for example, the ruby version the 'Related to Incident' in pagerduty console is like:

services-01289.ops/elasticsearch-cluster-status : ESClusterStatus WARNING: Cluster is yellow
hostname/check_name: output

that is fine, but the pagerduty in GO I have something like this:

CheckHttp CRITICAL: Request error: end of file reached
this is the output command without the hostname and check name, I would like to add these fields for a better understanding of the alert.

How I can fix it?

Thanks!

@pablolibo
Copy link
Contributor Author

I am adding new PR for this issue #6

@nixwiz
Copy link

nixwiz commented Aug 20, 2020

This was left open even though changes were merged. Subsequently, the summary field is now configurable as a template (in #28 )

@nixwiz nixwiz closed this as completed Aug 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants