Creating a map
- Former user (Deleted)
Overview
It is possible to create a map from scratch. To do it, go to the General settings and click on Manage maps under Maps on the left menu side. Then, click on Create a new map button in the right-down corner.
The map editing mode will open showing a blank canvas for the newly created one. Use the following buttons to configure the new map.
Left-side menu |  | Click to expand or collapse the menu. |
Zoom options | Use the + and - buttons to adjust the zoom level of your view, or use the scroll on your mouse. Use the Home button to return to the default zoom. | |
Data sources and entities |
| Use the buttons to add new entities or add data sources. More information More information Refer to the Add data sources and Add entities to know more about this. |
Right-side menu |
| Click to expand or collapse general configuration:
More information Go to the General settings section to know more. |
Publish button |
| Save the current map configuration. |
General configuration
These settings describe the general configuration and behavior of a map. There are three general configurations. Click each of them to see the parameters.
Add data sources
A data source is a query that you will be able to reuse in the configuration of a map. The data sources added are specific to the map you are creating.
To configure data sources on the configuration panel click on the data icon to add a new data source and a form display. Click on Create a data source. You need to use LinnQ format for the data source query. You can also create a data source from the field you select the data source.
Add entities
On the configuration, panel click on the + button to add a new entity to the map, and a form displays with all the necessary parameters that you need to set.
There are three different tabs to configure:
Linking entities
Once you have created at least two entities in the map editor, then it is possible to link them to impact rules.
To link an entity you have to follow these steps:
Click on the source entity. The entity highlights and the + green icon appears.
Click on the + icon. Keep the button pressed and draw it to its destination.
Release the button.
To unlink entities follow these steps:
Click on the arrow that connects the entities to another one.
Click on the paper bin icon at the top of the screen.
Remember
The relationship you are establishing is based upon impact. That means links should be read as source entity impacts the status of the targetted entity.
Linking entities using link criteria
The mechanism described in the Linking entities section is the standard method to link entities in an any-to-any. The following table of results shall be expected when linking entities using this approach:
Cardinality of source entity | Cardinality of target entity | Expected result |
|---|---|---|
One (for example no discovery key defined or only one entity value discovered). | One | The established link is rendered as a one-to-one relationship |
One | Many (for example, a discovery key has been defined and there are multiple discovered entities) | Single one-to-one links are rendered, one per discovered target entity |
Many | One | Single one-to-one links are rendered, one per discovered source entity |
Many | Many | Full all to all relationships mesh |
The procedure to implement linking criteria is as follows:
Assign relative weight
It is possible to assign a relative weight to the established linked. The link weight is used in the calculation of the final score for auto entities, more specifically, as a multiplier to the normalized value of the underlying child node.
For example, if an auto parent entity called Server had two child nodes ('CPU' and ‘Memory’) implemented as KPIs and linked to the parent entity, the overall status score for Server would be automatically calculated using the normalized values for ‘CPU’ and ‘Memory’ and then by applying the weighting factor for each of the two nodes.
If the specified weight for ‘Memory’ were 0, then the overall score of the Server entity would be a normalized version of the ‘CPU’ metric alone. The weight value can be specified either by a static number (for example, 1, 0, 0.5, etc.) or as the result of a query using the Dynamic weight input field. Use that dropdown to specify a query whose evaluated numeric result will be the applicable weighting factor for the link.
Summary view
Summary views consist of a reduced number of high-level entities and metrics displayed on a background image that condenses all information calculated by Service Operations in an efficient, easy-to-interpret interface.
It is possible to create and navigate through different levels of visualizations. While the first level of the Summary always corresponds to the level-1 entities defined with such visualization type, users can navigate to a second and subsequent level by linking level-2, and level-3 entities to the parent ones and defining them also with the Summary value in their respective Visualization type input.
For each entity defined as Summary in the Visualization type, a green box will be shown on the screen, with a sample value and unit text (0 unit). The size of the boxes is easily modifiable by dragging and dropping them with the mouse. Click on the blue box and drag it through the screen to position it in its wished location on top of the defined background image.
A double-click action on the blue boxes will, on its side, show the Summary Mode Settings form for the selected entity:
Summary multicomponent nodes
There is the possibility to configure summary screens with component nodes. To do this, a node must be created with auto-discovery criteria and summary mode activated in its display settings, it is recommended to add an inventory query to ensure that there will be data to display at all times.
When navigating to a summary level with this type of nodes, an editing form will be enabled. This form allows you to execute the query indicated in the inventory query to add the components, you can also add them manually and remove components that no longer apply.
Initiating the data processor
In order to see the maps and be able to work with them, it is necessary to initiate the data processor jobs. To do this, it is necessary to go to Available Maps and click on the play icon.
Three options are displayed:
Sampling period seconds: the period of time in which we want to monitor a map.
Enable incidents module: enable or disable to init or stop the incidents identification processor.
Incidents events module: multiple selectors to active detection modules.