Skip to content
This repository has been archived by the owner on Jan 11, 2021. It is now read-only.

Feature Request - Option of Slack Username #39

Closed
vikas027 opened this issue Jul 7, 2018 · 6 comments
Closed

Feature Request - Option of Slack Username #39

vikas027 opened this issue Jul 7, 2018 · 6 comments

Comments

@vikas027
Copy link

vikas027 commented Jul 7, 2018

It would be good to have an option to define SLACK_USERNAME in order override the default username incoming-webhook

@whs
Copy link
Member

whs commented Jul 7, 2018

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.

@vikas027
Copy link
Author

vikas027 commented Jul 9, 2018

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

  • Slack Channel Name - k8s-alerts
  • GitLab alerts are thru name gitlab
  • Grafana alerts are thru name grafana
  • Similarly, I want a customized name for kube-slack

I hope the use case is clear now.

Cheers,
Vikas

@whs
Copy link
Member

whs commented Jul 9, 2018

You can create 3 incoming webhooks that point to the same channels with different name. That's what we're using as well.

@vikas027
Copy link
Author

vikas027 commented Jul 9, 2018

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.

@whs
Copy link
Member

whs commented Jul 10, 2018

I'm sorry but adding this feature which has equivalent option available would cause additional maintenance work on our part.

@whs whs closed this as completed Jul 10, 2018
@vikas027
Copy link
Author

It is up to you, equivalent options are not really equivalent when you have multiple applications pointing to the same channel.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants