Service Operations

[ 1 Purpose ] [ 2 Introduction ] [ 3 Accessing maps ] [ 4 Domain vs. Global maps ]

Deprecated application

Note that the Service Operations application is deprecated and no longer supported by Devo. For more information and alternative solutions, please contact support@devo.com

Purpose

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 to virtualize any environment or industry. The solution has been built with a strong focus on ease of configuration, yet it is versatile enough to cater to 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.

Introduction

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, entities' definitions, and the relationships (hierarchies, impact rules, traffic, and so forth) between them.

Use maps to:

Visualize technologies and/or use cases.
In end-to-end scenarios: for example, the e-commerce global map is built upon Devo’s demo.ecommerce.data streaming data flow is available in all domains and implements a cross-domain management tool that touches upon the operational monitoring of a web application, customer experience management metrics, as well as business-related performance monitoring.
As templates for the creation of more complex models.

Users of Service Operations can create their own maps using the built-in editor, or use the library of global maps provided by default. Refer to the Configuration section for more details.

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.

Furthermore, incidents can be also created and reported upon, consisting of 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. 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 can be considered as an application execution framework that runs at the top of the Devo Platform, where each map defines the implementation logic of an individual application.

Service Operations is available in all Devo domains via the Applications gallery. Refer to the Installation section of the documentation for more details.

Creation and maintenance

Devo, through the Service Operations team, is responsible for the creation, maintenance, and evolution of maps. Contact your Devo representative for any assistance or suggestions you might have on the available model set.

Pre-requisites

As with any model in Service Operations, maps require all associated technologies and data sources to be available and ingest data into the Devo core. In those situations where data sources are unavailable, the map will continue to be accessible and usable but no data will be presented.

To go back to the list of maps available to you, open the selector in the top left, or go to the Configuration section.

Accessing maps

You can access maps in two different ways:

If you have installed Service Operations. Then you can manage all your installed maps through Applications → Service Operations.

Here you can choose between domain maps and global maps.

If you have installed your application via Devo Exchange, then the application will appear in the Application tab.

You need to have Service Operation installed to access any application. Once you have Service Operation installed, you can access the application in either of the two ways explained. Service Operation allows you to have a better overview of all the applications you have assigned to your role. Is the easiest way of configuring and opening applications. Refer to Service Operations to know more.

If it is not your first time accessing a map, the last one you have opened will be shown by default. To go back to the list of maps available to you, open the selector in the top left, or go to the General Settings.

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 Configuration section.

If you want to know how to work with maps go to Working with maps.

Domain vs. Global maps

When opening Service Operations, you can choose between domain maps or global maps. Domain maps are the ones that you as a user can configure and create or that have been created for you. Global maps are configured by default; you can download them and install them in your domain on the Exchange panel. Refer to Installing content section to know more about it.