Help needed for testing some alerting providers

[TwiN]

I'm preparing a PR that adds a lot of new alerting providers.

The issue is that I don't have the time to create an account for each provider and test them myself, as such, I decided I'd try to take a bit of a different approach than usual.

The new providers will be added and will include a note at the top of their section in the documentation:

⚠️ WARNING: This alerting provider has not been tested yet. If you've tested it and confirmed that it works, please remove this warning and create a pull request, or comment on #1223 with whether the provider works as intended. Thank you for your cooperation.

The warning is pretty self-explanatory, but I'm hoping I can leverage the help of other developers as they passively/organically use these new alerting providers, as opposed to me having to take on the work of testing everything by myself.

[TwiN]

Relevant PR: #1224

This will be merged as soon as I'm done going over it a 3rd time.

The new providers are:

• Datadog
• IFTTT
• Line
• NewRelic
• Plivo
• RocketChat
• SendGrid
• Signal
• SIGNL4
• Splunk
• Squadcast
• Vonage
• Webex
• Zapier

I primarily selected them based on popularity (and thus likelihood of being used by Gatus users), but some were picked because they were alternatives to very popular providers.

Based on how the approach of letting Gatus users test new providers goes (i.e. how quickly they are tested), I may do one or two more batches like this, or perhaps start taking suggestions in a discussion like this.

[rons4]

I have just tested it and I can confirm that SIGNL4 works fine for both, triggering and resolving alerts.

[TwiN]

Thank you for taking the time to test it! I merged your PR

[rons4]

Thanks a lot, @TwiN.

[jules2689]

Hi! I was able to get signal working with https://github.com/bbernhard/signal-cli-rest-api (which is what I assume you intended to use with the /v2/send embedded).

The only issue I had was that I didn't realize v2/send was hardcoded here. A possible improvement could be to have validation that the configured URL does not end with v2/send & to mention what container the integration was designed to be used with (as I know there are a couple containers available which implement different types of signal apis.

Thanks for the updates here! Looking forward to seeing a semver release so I dont need to run latest :)

[TwiN]

Partially addressed via d559990. Thank you for taking the time to share this with me!

As for releasing a real version with all these changes, it's coming soon. With the new Suites feature I merged last week, I want to give it some time to soak in, as suites made me change a lot of existing features and I want to make sure nothing's broken before releasing a new stable version.

[jules2689]

That makes sense! Any chance you have thought about re-alerting if something isn't fixed?
I had been messing around with my homelab and didnt notice the telegraf instance being down as I was fixing other things - would be great to re-alert every n hours or something! For now Im exporting metrics to Grafana and handling the re-alerting myself :)

[TwiN]

This is already possible using alert reminders (see alerts[].minimum-reminder-interval)

[StaticVoidMoon]

Hi.
[Alerting Provider] Line : Is Working Correctly.
I have test both using group_id and user_id. Both of them are working correctly. Thanks for including Line which is only popular in some countries. Unluckily my country included in that list.

• Please find the attached pictures below for proof.
  ** Tested on gatus:latest. [sha256:b3eba160defba9431dc1f35eba2ec14fd6871a57f4aa557d650c06ba85025784]

Although, I found the wording of the config kinda confusing since it said 'user-ids' when actually you can use both 'user-id', 'group-id', or 'room-id' here.

alerting:
  line:
    channel-access-token: "YOUR_CHANNEL_ACCESS_TOKEN"
    user-ids:
      - "U1234567890abcdef" # This is user-id
      - "U2345678901bcdefg" # This can be a group-id

Also, noted that unlike other provider you need to have Line Official Account to interact with Line Messaging API. And sorry for not opening a PR. I am not confident with my English.

Thanks again for your awesome works.
P.S. Any grammatical mistakes are my own.

This one is sending to single user.

This one is sending to a group of user.

[TwiN]

Addressed in 3d61f5f

Thank you very much for taking the time to reach out!

[luketainton]

Hi @TwiN - the Splunk integration is working 🥳

[TwiN]

Glad to hear it! Would you like to create a PR to update the documentation (removing the note about the Splunk integration being untested)?

If not, no worries, I'll take care of it :)

[luketainton]

Opened #1475 :)

[capachow]

Rocket.Chat is working but has some minor visual bugs in the conditions (image attached). Also, do the overrides support partial attachment overrides (or is it all or nothing)? For example, if I wanted to use a different icon in the attachment author name:

overrides:
    - attachments:
        title: ":warning: Gatus Alert Message Example"

Thanks! It's looking great!

[TwiN]

Thank you for letting me know! Would you mind creating an issue so that we can get this fixed?

[CoreKit-glitch]

Hello,

I tried the alerting provider Webex.

At now i only test with incoming webhook : https://apphub.webex.com/applications/incoming-webhooks-cisco-systems-38054-23307-75252

Webex user can create a webhook and map it to a room/space.

Webhook url is provided like : https://webexapis.com/v1/webhooks/incoming/[id]

Next just configure your alerting provider in yaml like this :

alerting:
  webex:
    webhook-url: "https://webexapis.com/v1/webhooks/incoming/[id]"
    default-alert:
      description: "health check failed"
      send-on-resolved: true
      failure-threshold: 3
      success-threshold: 3

Map on your endpoint the webex alert type :

alerts:
    - type: webex

You'll receive on your Webex space a message like this

and for recovery

Hope this help !