Allow for webhooks as a logging target

[stgraber]

Is there an existing issue for this?

• There is no existing issue for this feature

What are you currently unable to do

Similar to #1420, it would make sense to also supports webhooks as another logging target type.

So we'd basically end up supporting:

• loki
• syslog
• webhook

For each of which we'd support selecting the type of events we want to send as well as some other configuration options like the log level for logging messages or the number of retries that should be made for sending to loki or webhook.

For webhooks specifically, we'll need the user to provide a URL and an optional number of retries that should be made. Internally we'll just spawn a goroutine which will make up to that number of attempts to send the data. We'd also allow configuring the format of the webhook. Initially we could support our own (same JSON struct as an API event) as well as some common options like the Slack webhook format and Google Chat webhook format so Incus can directly notify a notification channel in those chat platforms.

What do you think would need to be added

No response

[chxmxii]

Hello @stgraber, can you assign this to me?

[stgraber]

@chxmxii I'm going to hold off on that for a few more days as @presztak is currently working on #1420 which will cause the main reorganization of how we do logging in Incus.

Once he's part of the work (adding the new structure, adding syslog and moving loki over) is complete, then this issue can move forward with adding webhook as an extra option to it which at that point should be pretty straightforward to do.

[stgraber]

This is now unblocked.
@chxmxii let me know if you still want it.

[chxmxii]

Yes, you can assign this to me!