Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Introduction

Devo Services Operations is a flexible, multi-purpose, multi-environment monitoring solution that aims to maximize visibility, increase operational efficiency and improve issue detection and troubleshooting tasks for virtually any environment or industry. The solution has been built with a strong focus on ease of configuration, yet it is versatile enough to cater for a wide array of scenarios and customer needs, including:

  • ITOps / AIOps use cases
  • Security use cases
  • Services and IT infrastructure monitoring
  • Applications performance monitoring
  • Networks status and performance
  • Customer experience management
  • Multi-cloud / hybrid environments

Service Operations relies on the use of maps, which are logical representations of the scenario to handle, and that define the general configuration and behavior of the application to achieve a particular set of business goals. Typically, maps include general execution rules and the definition of entities and the relationships (hierarchies, impact rules, traffic, and so forth) between them. From a different perspective, Service Operations can also be considered as an application execution framework that runs on top of the Devo Platform, where each map defines the implementation logic of an individual application.

Users of Service Operations can create their own maps using the built-in editor or use the library of global maps provided by default. Upon execution, maps help Service Operations' core to discover and gather real-time data, and execute the built-in data correlation and analysis models to calculate results and trigger actions, where applicable. The result of this entire process, which is executed cyclically, generates an up-to-date status of the service defined in the model, thus achieving the first goal of providing a comprehensive, end-to-end status of the monitored elements. Besides, incidents might be also created and reported upon, consisting on an actionable summary of discrete events that ease the diagnosis and troubleshooting of anomalous behavior. 



The diagram below summarizes the general working principles of Service Operations. Please refer to the basic concepts section of the documentation for more details on maps, entities and their relationships, as well as other fundamental concepts:


 

Service Operations is available in all Devo domains through the Applications gallery. Please refer to the installation section of the documentation for more details.

Navigating the Application

Starting a Map

Once launched, and right after the welcome splash screen, Service Operations asks users to select one map for execution. In that dialogue, it is possible to choose between domain or global maps by clicking on the tab selector.


 

Only one map can be loaded at a time, although there is no limitation on the number of processing jobs per domain working in the background. Find out more on processing jobs in the Maps Configuration section.

Main Interface and Application Modules

Once a map is selected for execution, all related data (discovered entities, relationships, incidents, and so forth), as well as their current statuses, are presented to the user in the default section configured.

Although all modules that make up Service Operations can be individually enabled, disabled or placed arbitrarily in the main menu (top bar in the user interface), the first execution of the application usually sets the user in the Service Overview section, which provides a visual representation of the topology of the monitored service as well as its overall, real-time status. Navigation across the different modules is achieved using the icons available in the same main menu bar.



 The complete list of modules included within Service Operations is as follows:

  • Service overview: Full, detailed visualization and analysis of the model in the form of a multi-layered map.
  • Incidents viewer: List of incidents and access to detailed information related to each one.
  • Monitors: Multi-entity visualization tool for incidents troubleshooting and follow-up activities.
  • User experience: Real user experience monitoring element with individual user drill-down capabilities.

The Administration module provides access to the general configuration of Service Operations as well as to the available maps and technologies.

Switching the Active Map

Use the top bar submenu for a quick access to all available maps:



Exiting Service Operations

To leave Service Operations, simply select any other section or application in Devo by accessing them in the platform's main menu (left-hand side). Alternatively, you can close the application by closing the active window in the Internet browser.

  • No labels