Khazi Peppers
Automation & Orchestration
Automation Tasks
Automation is based on tasks. Each task has its own specific job to perform.
- Device UP/DOWN - Poll if device up or down?
- CPU Utilization - Poll if CPU too high?
- Send Email - Send email to notify team of events
- Relay information to 3rd party application - Send information to 3rd party app (Like a Ticketing system to have ticket auto-generated)
- Server Services UP/DOWN - Poll if service running?
- Services Restart - Just like it sounds.
Orchestration Tasks
Orchestration coordinates tasks into a process flow. If the results of specific tasks (UP/Down State, High CPU, etc) meet a specific criteria then it will trigger other tasks. Below are two examples of what I mean.
Scenario One
For this scenario the task responsible for checking UP/DOWN status on devices finds a device is down, this is classified as an event. Thanks to orchestration the event triggers two responses; 1, is to relay the information to a 3rd party application (likely a ticketing system), and another response which will send an email to the interested parties.
- ↱ (Event) Device UP/DOWN
- ↳ (Triggered Response) Relay information to 3rd party application
- ↳ (Triggered Response) Send Email
For the second scenario a service is found to be down by a monitoring task. This triggers the same responses as Scenario one, but it also triggers an action for another task to restart the down/hung service.
- ↱ (Event) Server Services UP/DOWN
- ↦ (Triggered Action) Services Restart
- ↳ (Triggered Response) Relay information to 3rd party application
- ↳ (Triggered Response) Send Email
I hope this is helpful and based on feedback I'll be happy to edit and add/amend anything.
All
