Using the Panopta Monitoring Policy Framework for monitoring configuration
The Panopta Monitoring Policy Framework is a tool meant to help manage your monitoring configuration, and quickly onboard new instances to an existing environment, or rapidly setup monitoring in a new environment. By bringing all of your configuration into one place, monitoring policies can help you automate adding templates, tags, manifest files, APIs, and other essential monitoring features to your infrastructure, getting you one step closer to fully-automated configuration.
What is the Monitoring Policy Framework?
By bringing your monitoring configuration into one, central location and providing a workflow-like interface, Monitoring Policies allow you to manage your monitoring configuration easily. Coupled with Panopta’s robust tagging and template system, Monitoring Policies can be used to configure an entirely new environment, or it can be used when bringing new instances into an already existing environment. Instances can quickly be added and configured for monitoring using the rulesets you create in the Monitoring Policy Workflow.
Why set up a Monitoring Policy Framework?
In a highly dynamic environment, it gets difficult to track and account for auto-scaling in your monitoring configuration. When working with VMs, containers, microservices, or some combination of these auto-scaling services, monitoring policies will ensure you never lose visibility on your environment. The monitoring policy rulesets will automatically take the actions needed to configure new instances as they’re created.
There are three main types of actions you can take with monitoring policies:
- Configure monitoring on new instances by applying templates
- Enrichment of instance data by selectively applying tags which will get picked up by reporting, dashboards, maintenance, and other useful features of Panopta
- Situating new instances in the environment by fitting it into the group structure, applying alert settings, and determining its monitoring needs
The list of actions you can take, and the dimensions you can use to filter your instances in the monitoring policy workflow is growing. So you will be able to adjust the rules as necessary and configure your monitoring quickly even as updates are made to your environment.
In addition, the Monitoring Policy workflow includes both default rulesets you can use out of the box, or you can create your own monitoring policies to meet your needs. The default and custom rulesets operate on a simple condition and outcome rule which form an “If…then” statement like, such as the example below:
How can the Monitoring Policy Workflow benefit your monitoring configuration?
Using the Monitoring Policy Workflow can help configure new instances, organize your environment, and expose more data, here’s just one example use case:
Problem: A large financial institution is looking for a new monitoring solution, the IT team has found several good options, but they know selling any new solution to upper management will be difficult given their large number of instances which will need to be onboarded into the new system. In addition, they have several legacy systems that the monitoring solution needs to cover, and ultimately require the highest level of security possible.
Solution: Even in the case of new customers, the Monitoring Policy Framework will make their transition to Panopta faster and more efficient than a transition to other monitoring solutions. The IT team will be able to set up Monitoring Policies which account for the different types of instances they’re working with, including legacy instances, and customize rulesets to apply appropriate templates, tags, and alert timelines to each instance. Coupled with Panopta’s POC process, which usually has about 80% of a potential customer’s instances onboarded within 30 days, the IT team will be able to convince their upper management that a new monitoring solution isn’t unapproachable and can be onboarded in a reasonable amount of time.