USE CASE
Orchestral's sensors combined with syslog services enables users to have continuous data monitoring so that in the event of a critical outbound interface going down an operations team member will be immediately notified with a message indicating which interface has gone down and whether a standard bring up operation is able to resolve the issue.
Continuous Real-Time Monitoring
Orchestral.ai is able to automate existing tasks without having to rip and replace any existing services utilized by the company.
Build Upon Existing Processes & Tooling
Not only saving money by reducing network down time, but also reducing the stress of the IT teams by automatically being able to assign the incident ticket a priority 1 or a priority 5, thus allowing the team to know whether they can relax or if they need to jump to action.
Reduce Downtime While Improving Resource Utilization
Orchestral Platform Benefits
Challenge: Responding to Every Network Problem
-
A user complains about an application not working, only to realize that there is a connectivity issue. The user then must open a service ticket which then alerts the company that it faces the inevitable issue of a critical outbound interface going down. The ticket gets moved by the service team to the network team with a priority 1 for immediate action regardless of the time of day.
-
The network team, oftentimes woken up in the middle of the night to deal with the issue, must then troubleshoot and run diagnostics to discover which interface is Once identified the remediation action of bringing up the interface occurs, the connection is verified and the service ticket is updated and closed.
-
These user complaints pile up leading to an overwhelmed service ticket system, meanwhile the network team must always respond to the event as though they are priority 1 until they are correctly identified, even if a simple interface-up command would resolve the issue. This leads to increased stress for the network team and increased employment costs through overtime worked for issues that could wait until the morning.
The Conventional Workflow Approach
Manual Process: 2-4 Stressful Hours for Network Operations (see Figure 1 below).
Figure 1 – Manual Interface Outage Response
Orchestral Platform Solution
Orchestral.ai introduces a completely automated solution for this problem that is able to perform all of the existing operations to ensure that the companies existing IT tools and practices are maintained.
To begin, the Orchestral Data Bot, a multi-vendor data collector, collects statistical data from all the infrastructure end points and publishes the data to Maestro’s infrastructure telemetry data store. The Data Bot also collects all syslog information from network switches which enables Maestro to recognize immediately when a critical outbound interface goes down. Once recognized, Maestro will trigger a Composer auto_remediation_workflow without delay. Composer then executes the following steps:
-
If the router is accessible: Informs the operations teams about the outage through omni-communicational chatops and indicates the start of the auto_remediation_workflow.
-
Collects the show tech information on the router before and after the remediation action. Zips the two files as the artifact of the incident.
-
Composer then opens a service ticket with priority 5 on the ticketing system and attaches the troubleshooting artefact for further analysis.
-
Lastly, informs the Ops team through chatops of the new incident created and the number for analysis.
Maestro + Composer: 20-40 Stress Free Seconds (see Figure 2 below).
Figure 2 – Composer Automated Security Policy Update
Getting Started
Orchestral's solutions are available as free 30-day Proof of Value evaluations. To get started, just click the "FREE TRIAL" button at the top of this page and complete the Trial Request Form. If you'd like to see a demo first, just click the "Book a Demo" button below to book a date/time that works best for you. Otherwise, you can get started by emailing us at info@orchestral.ai.