Closed vikas027 closed 6 years ago
You can configure the username from Slack's incoming webhook configuration. Is there any use case missing from this?
If you're on the free tier, each instances of incoming webhook are not counted as separate integrations.
Hey @whs ,
Yeah, I can do the same using on the Slack UI. But it would be useful to the know the source of the alerts if I want to use the same channel for alerts from various applications
This is my use case
k8s-alerts
gitlab
grafana
kube-slack
I hope the use case is clear now.
Cheers, Vikas
You can create 3 incoming webhooks that point to the same channels with different name. That's what we're using as well.
Yes, but IMHO that is a work around and then has limits. It would still be convenient to have variable SLACK_USERNAME
so that we don't need to have multiple hooks, and just one hook is sufficient for all alerts. I have plans to have more services alerting to the same channel.
I'm sorry but adding this feature which has equivalent option available would cause additional maintenance work on our part.
It is up to you, equivalent options are not really equivalent when you have multiple applications pointing to the same channel.
It would be good to have an option to define
SLACK_USERNAME
in order override the default usernameincoming-webhook