Welcome to community Discussions!

[ktkaushik]

👋 Welcome!

We’re using Discussions as a place to share feedback, discuss queries, and just connect with others. We hope that you:

• Ask questions.
• Share ideas.
• Engage with others.
• Remember to be loving and respectful 💪

Feel free to introduce yourself.

[richamishra006]

Hi @ktkaushik
I am facing few issues with spike.sh

1. i am not getting incident title , i clicked on click to report, multiple times in past few days, but nothing happened
2. Also i am creating alert rules to ignore few alerts, but those rules are not working
   
   
   I created the above rule and had set the priority and severity of the incident, but still those incidents were repeating
   
   I created above rule such that if there is crashloopbackoff keyword in any incident, then is should not create the incident, but still i was getting the alerts

Please let me know if i am missing anything or not doing it in correct way.
Thanks,
Richa Mishra

[noob-master147]

Hey @richamishra006

I looked into your incidents. From the metadata, it seems like you are using Prometheus in your infrastructure for monitoring and using a Webhook integration on Spike.sh for sending alerts.

I recommend using the Prometheus integration that we have on Spike instead of the webhook integration.
Learn more about our Prometheus integration here

If you still want to use webhook integration instead, here is how it works:
For webhook integration to parse a message, the message should be provided in the request body as req.body.title. This title is used to formulate the incident title. Read more about Webhook integration here.

Since in your case, there was no title key present in the req.body, the parsing failed.

The alert rules that you set did not work because the conditions did not satisfy for it to run. Since the parsing failed, the alert rules naturally did not find the keyword CrashLoopBackOff in the incident title.

I hope this helps

[noob-master147]

We support a specific format in which the severity and priority. The incidents that you have don't have the specific key-value pairs and hence the alert config did not work.
Read more here

[richamishra006]

Thanks a lot for replying, i will try out these steps and will let you know