Global maps
Purpose
In order to provide maximum value with minimum effort and time to readiness, Devo incorporates a number of predefined maps preconfigured within Service Operations and available in all Devo installations and domains without any need for configuration. These so-called global maps are conceived for their usage in a number of scenarios:
As off-the-shelf management, visualization and dashboarding tools for well-known technologies and/or use cases. As such, Service Operations comes with ready-made configurations for the most popular data sources, or for common use cases.
As examples of the capabilities of the tools in end-to-end scenarios: for example, the e-commerce global map is built upon Devo’s demo.ecommerce.data streaming data flow available in all domains, and implements 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: All provided maps can be utilized as a template or baseline to iterate or evolve for more comprehensive services monitoring via the models cloning feature.
Creation and maintenance
Devo, through the Service Operations team, is responsible for the creation, maintenance, and evolution of global maps. Contact your Devo representative for any assistance or suggestions you might have on the available models set.
Pre-requisites
As with any models in Service Operations, global maps require all associated technologies and data sources to be available and ingesting data into the Devo core. In those situations where data sources are unavailable, the map will continue being accessible and usable but no data will be presented.
Access and configuration
Access to the global maps library can be done from the following sections in Service Operations, namely:
Welcome screen, in the maps loading tab.
Active model selector in Service Operations main menu.
Through the administration tool, under Maps > Available maps.
Configuration
Global maps do not allow any reconfiguration of their source technologies or general behavior, such as active modules, and so on. However, they can be cloned for customization, extension or combination with other existing maps.
Extending global maps
It is possible to extend the functionality or set of covered technologies of all available global maps by means of the clone functionality. This way, Devo curated maps can be utilized as a baseline to expand their original coverage or to adapt their general behavior to embrace the particular needs of a user or Devo customer in their specific domain.
By definition, extensions generated from global maps do not become global themselves, but they restrict their accessibility to the local domain where they were created.
Deletion of cloned maps
Once cloned, global maps become localized to the current domain and are treated as local. Any deletion action applied to them does not affect the original global map.