Token to include DataSource raw output in email and alert body
We have script DataSources that output useful diagnostics information that help Operations to understand the number valuewhen an alert is generated. We want to include the raw output from a DataSource in the alert and email body. What we need is a##DSRAWOUTPUT## token which contains the complete raw output sent to standard out from a DataSource script. For example, we monitor for processes running under credentials they are no supposed to be running under, and we want to include that info as textual information in the alert/email body.21Views3likes2Comments
Reports as body of email instead of attachment
Our CTO is asking me to provide a daily email report of some key metrics to our clients and internal stakeholders. I'm able to create a suitable report and email it, however his concern is the number of clicks to view the report. The belief is that the email will just go straight to trash if our clients can't see the report in the email body. For me, using gmail, I have to download the attachment first, then open it from my laptop. Two options we talked about were: 1. Use the HTML report as the body of the email rather than an attachment (surely the days of text-only email clients are gone) 2. Aconfigurable/dynamic subject to provide some hint of what the report actually contains, e.g. the uptime for a particular service over the last 24 hours.If the subject said "100% Uptime", there is no reason to open the report, if the subject said "98% Uptime" I can open to see more detail. Does anyone else have any ideas on how to makereports a little more effective for asomewhat apathetic audience?11Views3likes7Comments