alertmanager

Author	SHA1	Message	Date
gotjosh	1ba6405bbc	Remove the dedicated field to APIURL in favour of the configuration one Signed-off-by: gotjosh <josue.abreu@gmail.com>	2022-12-15 11:51:45 -04:00
gotjosh	572de996b7	Remove the `bot_token` Signed-off-by: gotjosh <josue.abreu@gmail.com>	2022-12-15 11:48:01 -04:00
gotjosh	5ebe94d325	Rename message to markwdown on the webex notifier Signed-off-by: gotjosh <josue.abreu@gmail.com>	2022-12-15 11:05:55 -04:00
gotjosh	f51f51ec72	Use the new truncation in bytes functions to ensure strings are not butchered Signed-off-by: gotjosh <josue.abreu@gmail.com>	2022-11-11 15:15:09 +00:00
gotjosh	e8b5c0aa0d	Fix and add a new test Signed-off-by: gotjosh <josue.abreu@gmail.com>	2022-11-09 20:07:54 +00:00
gotjosh	ac0dc96127	A few changes to better align with what I know think it's the best setup in Webex Teams - Move away from Webhook to APIRUL - Make the Room ID a require field - Set Authorization Credentails via Headers Signed-off-by: gotjosh <josue.abreu@gmail.com>	2022-11-09 20:07:54 +00:00
gotjosh	9e2608ebff	Notifier: Webex Cisco's Webex has been one of the most requested notifiers on Grafana for a while now, please see: https://github.com/grafana/grafana/issues/11750#issue-318358659 Given it's straightforward implementation, low maintance overhead and request demand, I think it's worth including this directly in the Alertmanager. Signed-off-by: gotjosh <josue.abreu@gmail.com>	2022-11-09 20:07:54 +00:00