Well well well... https://promlabs.com/blog/2022/12/23/sending-prometheus-alerts-to-discord-with-alertmanager-v0-25-0/
On n'a plus besoin de discord alert manager maintenant. Ça simplifie…
31e59937dc
Merge pull request 'feat: Initial setup for monitoring and alerting' (#48) from feat/monitor into master
0d56fbc09d
wip: applied comments in pr, changed naming of AlertChannel to AlertReceiver and added rust doc to Monitor for clarity
Does this even work? I don't see the binding with the ensure_ready impementation of K8sAnywhere.
This should not be called deploy as this will not deploy every time it is called. We use "ensure" for this behavior.
It's a bit weird to use a public raw function like this to initialize a Score, why not just use the usual struct building method?
autoloading inventory here is a big smell, you should avoid this as much as possible. What if the used built a custom Inventory and now you're autoloading his production inventory and you start wiping operating systems and network configurations?
This function looks really weird, I feel like this is a hack to link the config and the dependency together.
This rustdoc is pretty good to explain the abstraction, but giving a concrete example such as Prometheus would make a complete understanding much easier. Even I still have a bit of trouble to figure it out as-is.
You don't have to specify Topology here. I think it's better to keep the trait bindings to the minimum. DiscordWebhookSender should be enough.