xMatters Receiver
34 views
Skip to first unread message
Travis DePuy
Oct 28, 2020, 7:03:53 PM10/28/20
to Prometheus Developers
Hi all!
I'd like to see about submitting a PR for an xMatters receiver. We're happy to do the work and submit the PR following all the contributing guidelines. In poking around however, I found this statement on the configuration page:
"We're not actively adding new receivers, we recommend implementing custom notification integrations via the webhook receiver."
The statement isn't really clear as a 3rd party. Prometheus developers may not be adding new receivers, but as a 3rd party ready and willing to do the needed work, how does this apply?
Any guidance would be appreciated!
Happy Wednesday!
--- Travis
Julien Pivotto
Oct 28, 2020, 7:14:47 PM10/28/20
to Travis DePuy, Prometheus Developers
On 28 Oct 16:03, Travis DePuy wrote:
> Hi all!
> I'd like to see about submitting a PR for an xMatters receiver. We're
> happy to do the work and submit the PR following all the contributing
> guidelines. In poking around however, I found this statement on the
> configuration
> <https://prometheus.io/docs/alerting/latest/configuration/#receiver> page:
> Hi all!
> I'd like to see about submitting a PR for an xMatters receiver. We're
> happy to do the work and submit the PR following all the contributing
> guidelines. In poking around however, I found this statement on the
> configuration
> "*We're not actively adding new receivers, we recommend implementing custom
> notification integrations via the webhook
> <https://prometheus.io/docs/alerting/latest/configuration/#webhook_config> receiver.*
> "
>
> The statement isn't really clear as a 3rd party. Prometheus developers may
> not be adding new receivers, but as a 3rd party ready and willing to do the
> needed work, how does this apply?
For alertmanager, I'd recommend you to implement the webhook receiver in
>
> The statement isn't really clear as a 3rd party. Prometheus developers may
> not be adding new receivers, but as a 3rd party ready and willing to do the
> needed work, how does this apply?
your service directly, like, among others, squadcast did:
https://support.squadcast.com/docs/prometheus
>
> Any guidance would be appreciated!
> Happy Wednesday!
> --- Travis
>
> You received this message because you are subscribed to the Google Groups "Prometheus Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-devel...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-developers/9b7755c3-7f72-4e41-ac99-f7d0be542ae4n%40googlegroups.com.
--
Julien Pivotto
@roidelapluie
Travis DePuy
Oct 28, 2020, 7:21:52 PM10/28/20
to Prometheus Developers
Hey!
Cool. I did see that, but to provide a more streamlined solution for our customers we'd like to go with the receiver.
Why do you recommend one over the other?
Thanks!
Julien Pivotto
Oct 28, 2020, 7:26:04 PM10/28/20
to Travis DePuy, Prometheus Developers
On 28 Oct 16:21, Travis DePuy wrote:
> Hey!
> Cool. I did see that, but to provide a more streamlined solution for our
> customers we'd like to go with the receiver.
> Why do you recommend one over the other?
> Thanks!
We do not accept new integrations at the moment, and with integrating
> Hey!
> Cool. I did see that, but to provide a more streamlined solution for our
> customers we'd like to go with the receiver.
> Why do you recommend one over the other?
> Thanks!
the webhook receiver in your api/backend, all users can benefit from it
without installing an extra component.
--
Julien Pivotto
@roidelapluie
Travis DePuy
Oct 28, 2020, 7:35:05 PM10/28/20
to Prometheus Developers
Understood. Thanks!
Reply all
Reply to author
Forward
0 new messages