The topology map provides a graph-like representation of the entities that exist in a given model (i.e., graph nodes), as well as their general status based upon their governing metrics.
Relationships in the model (i.e., graph edges) describe an impact / status dependency relationship between the entities.
Use cases highlights
This module provides the following set of use cases:
Single pane of glass for multi-type, multi-level entities defining a complex service
Automatic entities discovery and mapping
Flexible, adaptable set of models
Real-time status assessment the discovered entities
The Service Topology module provides a visual, multi-layered view of all entities defined in a data model together with their status. That way, it is possible to summarize the status complex business services or applications, and pinpoint any problems or issues that might be affecting it.
Visually, the module is divided into the following sections:
Visual map: graph-like visualization that shows entities, their relationships based upon different criteria (impact, dependency, etc.) and their current status using a color code (green, orange, red).
Entities list and status: provides a detailed list of all entities shown in the map at a given time, with a summary of their status and a status trend indicator.
Incidents: While the status code provides an answer to "what is happening" based on the definition of the entities and their values, the incidents list tries to provide a guidance to the "why" question. In the service topology section it is possible to access the list of detected incidents and browse it via the button on the right hand side of the screen.
Entity details: detailed information of a selected entity in the map or from the full list of entities.
Each entity is represented as a node in a multi-level, hierarchical graph, where its root summarizes the overall status of the monitored service, whereas the lower elements (leaf nodes) commonly represent the most fundamental building blocks the service is composed of.
Once a model has been selected and the topology module loaded, Service Operations will display the current hierarchical / impact model with all identified entities and metrics and their overall status using the green = normal, orange = warning, and red = critical status color code.
The following actions are available to be performed on the topology map visualization:
Mouse over: a small overlay box is displayed / hidden when hovering over an entity on the map. The information shown includes:
Overall status of the entity as color code.
Current metric value.
Mouse click: clicking on an entity will focus on it and unroll the additional information panel on the right hand side of the screen. To hide the panel, click on a blank zone of the map or on the 'X' button in the upper right corner of the panel.
Overall status of the entity as color code.
Graphical representation of the metric value.
General entity information: description, metadata values, associated metrics.
List of affecting entities: child nodes in the impact hierarchy that do have an impact on the status of the selected node. Click on any items in the list to navigate to the details of that particular entity.
List of impacted entities: parent nodes in the impact hierarchy that are affected by the status of the selected node. Click on any items in the list to navigate to the details of that particular entity.
Right mouse click: A contextual menu will be displayed, providing additional actions to be performed on the entity:
Zoom-in: Creates a visual representation of the subtree that starts with the selected entity as root. Click on the 'X' at the ‘Zoom-in’ bar (bottom part of the screen) to go back to the full tree representation. NOTE: it is possible to chain ‘zoom-in’ actions, which will result in more trimmed subtrees.
Send to monitor: The selected entity will be displayed in the Monitors section of Service Operations for a more detailed analysis and comparison with other entities. Please check the information related to the Monitors module for more details.
Send all to monitor: All currently displayed entities will be sent at once to a new monitor. If the total number of entities to send is too large, the operation will not be performed and a warning message will be displayed.
View query: The LinQ query that governs the behavior of the entity will be shown in a modal.
Run query: The LinQ query that governs the behavior of the entity will be executed in Devo’s search window. NOTE: It is possible to return to Service Operations by clicking on the 'X' button in the search window.
Create alert: A modal for the creation of an alert associated to the values of the entity will be displayed. The user can introduce the necessary fields for the alert to be created and, once done, it will be registered and treated as any other Devo alert in the platform.
The graphical representation of the topology (graph chart) offers different visualization options, all of them available through the menus and controls available on the left menu.
The list of available options is as follows:
Zoom and positioning tool: Allows setting the zoom level applied to the overall map.
Click on the "+" and "-" buttons to increase or decrease respectively the zoom level applied to the visualization.The same function can be accomplished through the mouse wheel.
Click on the home button to reset to the default view.
Click on any blank area and drag the mouse while keeping pressed the left mouse button. That allows adjusting the displayed area on the screen with the current zoom level.
Auto-zoom mode: This tool enables an entity-by-entity zooming based on the level of criticalness specified using the three colored buttons in the tool bar. Click on the play button to start this mode and pause to stop it. Also, you can navigate to the previous or advance to the next entity by clicking on the arrow buttons.
Maximum topology depth selector: Select the number of represented levels in all trees using the level selector. The selector adjusts automatically from levels 1 (i.e., show only root nodes) to the max depth level detected in all represented trees (i.e., full representation of all trees).
Layout options: Displays / hides a menu with additional visualization options for the map.
Enable geolocation: When enabled, the entire layout of the map will change to a geographical mode. Entities will be drawn using their geolocation data. NOTE: This option will only be available when there are entities defined with geolocation information -i.e., their defined queries contain both "longitude" and "latitude" grouping keys in the last grouping section.
View mode: Allows the changing of the map visualization layout. Available options are Standard, Hierarchy, Lens, Organic, Sequential, Radial and Structural. NOTE: Depending on the map size (number of nodes), certain layouts can take longer to be rendered due to the calculations needed to position the nodes in the map.
Orientation: Certain layout options allow for an orientation configuration (e.g., Hierarchy). Use the selector to modify the representation from "Left to right", "Right to left", "Top to bottom" and "Bottom to top".
Filtering options: Allows filtering the set of nodes in the topology model by different criteria:
Filter by text: allows the application user to enter any free text description of the nodes. Those nodes matching the text as it is entered will be highlighted, while graying out the rest. Click on the enter button of your keyboard to apply the filter by the entered text.
Filter by tree, status, type, subtype, metadata field and value: allows for the entering of additional filtering criteria by these fields. Note the resulting map is a combination of the nodes that match all criteria.
The entities panel summarizes the status of all entities in the current model by listing them in the form of data boxes.
Overall status: Summarizes the status of the entire model, considering all defined entities and metrics, and consolidates it into a single indicator with a color code. The overall status indicator should be interpreted as the current status for the represented business service.
Individual status counters: Each of these text elements indicates the number of entities in the model presenting that status currently. Note that these counters are clickable elements and that they will act as filters in both the entities status panel as well as in the entities map, representing only the entities matching that criteria (i.e., status level).
Entities order: this dropdown allows you to select the way entities will be displayed in the panel, based on their level of criticality, within their respective levels. Higher criticality first shows those entities with a ‘critical’ status first, then the ones with a ‘warning’ status and finally the ‘normal’ ones.
Level show / hide: Click on the arrow in the level separator section to display or hide the entire level. This will make the entire list of entities within that level be displayed or hidden accordingly.
Entity details box: When not filtered out, every entity identified in the model will have its representation as an entity box in the panel. These provide information of the current status of the entity based on its value or scoring mechanism (query + thresholds) using the already mentioned color code.
Numeric value: current (i.e., the last one in the specified time range) value retrieved from the entity-defining query.
Unit: unit in which the numeric value is measured.
Variation percentage: numeric variation between the first and the last (i.e., current) value of the entity.
Calculation period: time period used between metric calculations (i.e., sample rate).
Trend graph: Graphical evolution of the entity value within the specified time range.
All metric boxes are actionable, providing more information of the entity they represent. The available actions are:
Left click on the mouse: Toggles the visualization of the entity details in the right panel.
Right click on the mouse: "View query", "Run query" and "Create alert", as described in the previous section for the visual map, are also available here.
Entity details panel
This information panel shows up any time an entity is selected (clicked on) in either the visual map or the entities list panel. Its goal is to provide a deeper level of detail on the selected entity, and allow for certain analysis options.
All information related to the entity is categorized as follows:
Description: Textual description of the monitored entity
Type / subtype: Metadata fields describing the category and subcategory of the entity (e.g., KPI / performance). The two fields are actionable, so clicking on each value will configure a filtering option using that value as filtering criteria. For example, if the type of the entity is KPI and that value is clicked on, Service Operations will recalculate the displayed map, offering only those defined as KPIs.
Chart type and options: Select different types of representation of the data related to the entity (time series, histogram, pie chart). Clicking on the options icon allows users to set additional configurations to the displayed chart, e.g., setting historic comparisons, enabling / disabling the display of value thresholds, etc.
Key performance indicators: List of children entities related to the node that are defined with type = KPI.
Affected by: List of children entities whose type is not KPI and that, based on the topology model defined, can potentially impact the status of the selected entity.
Impacts: List of father nodes in the tree whose the selected entity might impact their status.
Whenever one or more incidents are detected by Service Operations, the application will show an indicator on the upper right corner of the topology map illustrating the overall impact those incidents are having on the service. Similar to how the service status panel works, hovering on that indicator will expand that element and will provide an estimate of the total service impact.
The information provided in this list is identical to the one given in the corresponding section of the incidents viewer module. In this case, however, the list includes a summary status of the impact all incidents have on the service in terms of the number of entities defined in the impact assessment section of the entity creation process. For example, if a model specifies the number of end-users connected to a platform as the driving parameter, any detected incident will be qualified against that metric, generating an overall impact score based on the percentage of affected users vs. the total number of them. Should impact criteria not be defined, Service Operations will still continue detecting and reporting incidents but the level of severity will be stated as "unknown". This is the case of the example screenshot below, where elements, impacted elements and impact ratio have a "n/a" value because of the absence of an impact query.
When it comes to individual incidents, the information provided is as follows:
Description: Top level entity affected.
Incident detection timestamp: Date and time the first event included in the incident has been registered.
Entity status: Entity status level for the top level affected entity.
Top level entity affected definition: Identification of the top level entity affected (same value as in description).
Incident impact: Impact level of the incident in terms of overall level.