Global models purpose
In order to provide maximum value with minimum effort and time to readiness, Devo incorporates a number of predefined models preconfigured within Service Operations and available in all Devo installations and domains without any necessary configuration. These so-called global models 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 models for common cloud services providers (AWS, Azure, GCP), applications monitoring, micro-services management, etc.
As examples of the capabilities of the tools in end-to-end scenarios: for example, the e-commerce global model is built upon Devo’s demo.ecommerce.data streaming data flow available in all domains, and implements cross-domain management tool that touches upon 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 existing sets of models 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 models. Please contact your Devo representative for any assistance or suggestions you might have on the available models set.
As with any models in Service Operations, global models 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.
Access and configuration
Access to the global models can be done from all common models loading section in Service Operations, namely:
Welcome screen - models loading tab
Active model selector in Service Operations main menu
Through the administration tool, under Models > Available models
Global models do not allow any reconfiguration of their source technologies or general behavior, such as active modules, etc.
Extending global models
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, extended models generated from global models don’t become global themselves, but they restrict their accessibility to the local domain where they were defined.
Deletion of cloned models
Once cloned, global models become localized to the current domain and are treated as local. Any deletion action applied to them does not affect the original global map.