Add Telegram alerting provider #232
Conversation
|
@somtochiama please rebase with main branch and solve the conflicts for CI to run. |
|
I think we should look into switching to |
somtochiama
force-pushed
the
telegram-notification
branch
from
0992874 to
ce3bce5
Compare
internal/notifier/telegram.go
Outdated
| // The telegram API requires that some special characters are escaped | ||
| // in the message string. Docs: https://core.telegram.org/bots/api#formatting-options. | ||
| // The function only handles a subset of the characters because the only special | ||
| // characters in kubernetes names and namespaces are '-' and '.'. |
There was a problem hiding this comment.
But event.Message can contain any character, for example a kubectl apply error.
There was a problem hiding this comment.
I will update the function
There was a problem hiding this comment.
Please test this with a Kustomization that fails to apply. I see that we don't post the revision but we should, check how alerts look for Slack: https://fluxcd.io/img/slack-error-alert.png
There was a problem hiding this comment.
We have to add the event metadata to the message body as separate field in the markdown, maybe a list?
There was a problem hiding this comment.
This is what the message now looks like with the metadata added
Signed-off-by: Somtochi Onyekwere <[email protected]>
somtochiama
force-pushed
the
telegram-notification
branch
from
8bbacc2 to
b0563cb
Compare
stefanprodan
changed the title
|
Seems that's not working for {"level":"info","ts":"2021-09-22T12:19:25.795Z","logger":"event-server","msg":"Dispatching event: Helm upgrade succeeded","reconciler kind":"HelmRelease","name":"ingress-nginx","namespace":"flux-system"}
{"level":"error","ts":"2021-09-22T12:19:25.816Z","logger":"event-server","msg":"failed to send notification","reconciler kind":"HelmRelease","name":"ingress-nginx","namespace":"flux-system","error":"failed to send notification to \"-****\", response status code 400 Bad Request"} |
Closes #222