ExpertWhen a resource has an alert with an escalation chain that contains an email, I was under the assumption that no exchange server or imap or anything else has to be set up on the collector. Or so I thought.
This doesn’t happen in the Collector. It happens from the LM platform in the cloud.
One very tedious way would be to create configsource instances for each user and have the config check look for the message indicating the expiration is imminent. That would generate a separate alert for each user. You could then route, using alert rules, based on the instance name (this is the tedious part) to each user.
Instead of routing based on alert rules, you could use external alerting with the multi-instance configsource. That would pass all alerts to a script that runs on the collector. That script would have to ignore all alerts that you don’t want it emailing about. But the rest of the alerts could be processed by the script and send the email. You wouldn’t be tied to groovy at that point, but any script that you could run from the collector bash/zsh shell (i.e. python).
Alternatively still, there are services out there that let you post data (webhook) and they send the data as an email to the address you specify. You could build a custom HTTP integration to send alerts to that service and have them send the email for you.
All of these are options, each with advantages and disadvantages. YMMV.
