I've come across a use case scenario that would require the automatic transition of resources to baseline thresholds after the baseline calculation period has exceeded. This would prevent a slew of manual tasks from being created to transition the resources to their dynamic baseline values. Too many Outlook reminders can get exhausting..
By default, SolarWinds uses 14 days (I think) for its baseline calculation period. It would be an extremely useful feature to have NPM roll out the baseline thresholds as soon as the 14 day period has been exceeded.
A good example is having a newly ingested node automatically transition from hard-set CPU thresholds to baselined thresholds. Below are examples of what the thresholds would be.
Hard-set -- (0 - 14 days after initial ingest)
Warning >= 90%
Critical >= 95%
Baseline -- (15+ days after initial ingest)
Warning >= ${MEAN} + 2 * ${STD_DEV}
Critical >= ${MEAN} + 3 * ${STD_DEV}
I personally believe this would help many SolarWInds customers get recent information, not only from thresholds, but from reporting and alerting as well.
v/r,
Michael M.
