incident.io provider does not send deduplication_key on first firing, causing 422 error

[KevPace]

Describe the bug

When using the native incident.io alert provider in Gatus, the first firing does not include a deduplication_key in the request body. As a result, incident.io responds with HTTP 422 ("Deduplication key is required") and no incident is created. This prevents incident.io integration from working out of the box.

What do you see?

• Gatus triggers an alert for an endpoint configured with the incident.io provider.
• The POST request sent to incident.io does not include a deduplication_key.
• The incident.io API responds with a 422 error: "Deduplication key is required".
• No incident is created in incident.io.

What do you expect to see?

• On the first firing, Gatus should generate and send a valid deduplication_key in the incident.io payload so that an incident is created.
• If send-on-resolved is enabled, the same key should be reused for resolve events.
• If not, a new key should be generated for each firing as needed.

List the steps that must be taken to reproduce this issue

1. Configure Gatus with the incident.io alert provider:

   alerting:
     incident-io:
       url: "https://api.incident.io/v2/alert_events/http/<id>"
       auth-token: "<token>"
   endpoints:
     - name: example
       url: "https://example.org/health"
       conditions:
         - "[STATUS] == 200"
       alerts:
         - type: incident-io
           description: "service down"
           send-on-resolved: true

2. Trigger an alert (e.g., stop the monitored service so that the endpoint fails).
3. Observe the outgoing POST request to incident.io and the 422 response.
4. Confirm that no incident appears in incident.io dashboard.

Version

5.24.3

Additional information

Additional context

• This happens because the provider only sets deduplication_key from alert.ResolveKey, which is empty on the first firing.
• See alerting/provider/incidentio/incidentio.go for reference.

[TwiN]

@KevPace very detailed issue! Would you like to try fixing it?

[KevPace]

@TwiN thanks, I could give it a try, I'm not that golang pro but, i can try it :)

[KevPace]

@TwiN fix is done by my private profile :)
i also added that the metadata object will also use the extraLabels