tag:blogger.com,1999:blog-35032837.post660818599152939316..comments2023-10-20T09:12:43.031-06:00Comments on Diving Deep into Sublime Seas: Data Palette 4.0 is out! Why should you care?Venkat Devrajhttp://www.blogger.com/profile/14463595810339970301noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-35032837.post-36187033490106129592007-10-22T13:43:00.000-06:002007-10-22T13:43:00.000-06:00Let me provide a few quick examples of policies th...Let me provide a few quick examples of policies that need to be defined in one place but used across multiple areas or functions:<BR/><BR/>- Maintenance Windows: Monitoring needs to be disabled (paused) during maintenance windows, but maintenance-related automation routines need to run during this same window. So both multiple monitoring and automation functions need to be aware of these windows, especially when they change so they can behave/adapt accordingly. You don't want to define maintenance windows separately within the monitoring tool(s) and within the automation tool(s). There's got to be one central (shared) definition. And when the maintenance window changes, that single definition needs to be kept updated.<BR/><BR/>Other examples are action triggering thresholds (what are your yellow/red thresholds and what should happen when any of these are exceeded...), notification policies (who should be contacted when monitors need to fire an alert? Chances are, the same set of folks need to be notified when an automation routine fails...) and escalation policies. And how should these things change during different shifts, or when existing employees leave or new ones come onboard? <BR/><BR/>These are some quick examples, but there are several several more. <BR/><BR/>In short, automation is not something you do in isolation with a bunch of silo'd tools and scripts. A change in one area can have ripple effects both upstream and downstream. Having a central platform with a shared policy engine actually makes automation doable.Venkat Devrajhttps://www.blogger.com/profile/14463595810339970301noreply@blogger.comtag:blogger.com,1999:blog-35032837.post-6007930561038674882007-10-18T23:20:00.000-06:002007-10-18T23:20:00.000-06:00Interesting article. While you make a good point a...Interesting article. While you make a good point about shared intelligence across toolsets, I would like some anecdotal evidence or examples of how a single policy can be applied across tools? Since the tools all have different functionality/scope, why would such a thing be even required? <BR/><BR/>Am I missing the obvious?Anonymousnoreply@blogger.com