When a server's actual configuration is different than the planned configuration, then it's considered in drift. Sometimes this is expected, because you changed the plan, and sometimes it's not: someone manually made a change on the server. Otter continuously monitors your servers for configuration drift and can either:
This option is configurable per server, and monitoring can be set at specific intervals, determined by your infrastructure priority. When only report drift is configured, you can schedule a configuration job to run immediately, or for some time in the future. You can even run a configuration job as a simulation, so that no changes are made to the drifted server, but a log is created with changes that would have been made. This is often a must-have for complex, or multi-role configurations to assist in testing.
Otter brings Infrastructure as Code to a wider audience because it was built with usability in mind. You can easily create, and simulate, complex configurations and orchestrations using the intuitive, drag-and-drop editor, and then switch to-and-from code/text mode as needed.
The visual, dynamic, and intuitive UI shows, at-a-glance, the configuration state of all your servers. Whether local, virtual, cloud-built, or spread throughout disparate global data centers, you can see what's most important to you.
In Otter, Jobs allow you to remediate configuration drift and run orchestration plans, either on-demand, at a scheduled time, or on a recurring basis. This helps ensure compliance standards are met by minimizing downtime and giving explicit control over when, where, and how your infrastructure changes occur. You can also choose to run a Job in simulation mode, which can help ensure future accuracy by finding any errors that might have occurred in a plan, without effecting current configurations. When a simulation is run, Otter still follows the logic you defined in your plan, and logs all of the things it's doing, and the changes that would have occurred if the job was running normally.