-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add link to Signalilo in integrations page #1589
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're taking secrets on the command line, which is not secure.
@@ -69,6 +69,7 @@ For notification mechanisms not natively supported by the Alertmanager, the | |||
* [AWS SNS](https://github.com/DataReply/alertmanager-sns-forwarder) | |||
* [DingTalk](https://github.com/timonwong/prometheus-webhook-dingtalk) | |||
* [GELF](https://github.com/b-com-software-basis/alertmanager2gelf) | |||
* [Icinga2 (Signalilo)](https://github.com/vshn/signalilo): creates services in Icinga2 based on received notifications |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just saying Icinga2 is enough
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't need the description either
We're aware of that and pass the secrets as environment vars from a Kubernetes secret in the Helm chart. Unfortunately |
Let me know when that's resolved, our policy is not to list integrations with obvious security issues. |
Can you elaborate on what you consider obvious security issues when it comes to handling secret arguments? |
You're allowing secrets on the command line. |
I was asking more generally as to what practices you consider obvious security issues, since I wasn't able to find any guidelines after a quick look in the repository. For example, Is it OK to pass secrets in environment variables? In config files? |
Both those methods are okay (though environment variables have their risks). |
Maybe we should also wait for vshn/signalilo#15 to be resolved to people can use this effectively? |
There's no documentation requirement, as long as the code isn't obviously broken that's good enough in that regard. |
https://github.com/vshn/signalilo/blob/master/webhook/icinga.go#L20 -> is that an internal repo? |
|
@roidelapluie no idea how we missed this during the opensourcing process, the only reason why the github build works is that |
The description still needs to be removed. Thanks. |
@roidelapluie Can you elaborate on which description needs to be removed? I don't quite follow. |
@@ -69,6 +69,7 @@ For notification mechanisms not natively supported by the Alertmanager, the | |||
* [AWS SNS](https://github.com/DataReply/alertmanager-sns-forwarder) | |||
* [DingTalk](https://github.com/timonwong/prometheus-webhook-dingtalk) | |||
* [GELF](https://github.com/b-com-software-basis/alertmanager2gelf) | |||
* [Icinga2](https://github.com/vshn/signalilo): creates services in Icinga2 based on received notifications |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* [Icinga2](https://github.com/vshn/signalilo): creates services in Icinga2 based on received notifications | |
* [Icinga2](https://github.com/vshn/signalilo) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh ok, I've adjusted that in the latest version of the commit.
Signalilo is a tool to convert Alertmanager notifications to Icinga2 services. Signed-off-by: Simon Gerber <simon.gerber@vshn.ch>
Thanks. now only pending vshn/signalilo#17 |
I actually missed my last comment when merging. I hope that you will soon be able to address vshn/signalilo#17 |
This is just a small change adding our tool "Signalilo" which converts received notifications into Icinga2 services to the list of webhook-based integrations.