November 17
Derek
Tune triggers from your email inbox
When you get started with Scout, we try to setup sensible default triggers for events you may need to investigate on your servers.
For example, Scout generates an alert if your disk usage exceeds 85% or CPU Load over the last minute exceeds 3.
However, every server and application is different. For example, a CPU load of 3 is fine on some servers but a problem on others. We’ve made it easier to tune Scout for your setup if Scout is sending too many alerts.
Tune from your email inbox
When you receive an alert from Scout in your inbox, you’ll see a link at the bottom to adjust your triggers. If Scout seems too noisy, just follow the link.
Time between alerts
When you edit a trigger in Scout, we now provide a past history of how often the trigger has fired over the past 7 days. If a trigger is firing more than once per-day, you may want to adjust the thresholds.
Metric history
When creating or editing a trigger, Scout provides the highest value and average value of a metric over the past 7 days to give a better idea of how a particular metric varies. Using this data, you can set a more appropriate threshold (for example, closer to the highest value and not the average).
What are these triggers anyway?
Most of the alerts generated from Scout come from triggers (plugins can also generate alerts on their own). Triggers watch the metrics as they come into Scout, firing alerts when thresholds are met or exceeded.
You can create a trigger for any metric reported to Scout. Triggers can be accessed in the Server Admin area of Scout.
