Model configuration
Setting up the model
Follow the next steps to translate the desired business logic in the form of a Service Operations model:
Step | Description | Screenshot |
|---|---|---|
1 | Go to Service Operations administration. Click on the manage models subsection and then on the create new model button. A new, blank model is created. | |
2 | Expand the global settings menu on the right hand side of the screen and set an appropriate name for the new model, for example, “E-commerce” and click on the apply changes button. Then, click on publish to save the configuration into Service Operations' database. |
|
3 | Create a new node for the model by clicking on the '+' button. Configure it as follows:
Click on apply changes, then click on publish. If no errors are raised, the new node should appear in the model. |
|
4-7 | Repeat the process to create 4 new nodes:
Apply changes by the definition of each new metric and then publish. |
|
8 | Click on user errors and then on the clone button on the top buttons menu. A new icon called Duplicated user errors should be created. Repeat the process for application errors and traffic. Two more nodes are created as a result of these operations. Click on publish to save all changes. |
|
9 | Hover on the user errors node until a ‘+' shows at the node border. The click on the ‘+’ icon and, without releasing the click, drag the arrow to the border of the duplicated user errors entity. A link between the two nodes should be established. Repeat the process to link application errors with Duplicated application errors. Finally, link traffic, conversion rate and avg. ticket individually with Duplicated traffic. Publish to save all changes. |
|
10 | Change the name of the duplicated entities as follows:
Publish to save all changes. | |
11 |
Publish to save all changes. |
|
12 | Click on the link between user errors and individual user status. In the menu that appears on the right-hand side of the screen, set both from column to column with clientIpAddress. Click on apply to keep this configuration. Repeat the previous procedure with application errors and app module status. |
|
13 | Click on the user errors node. In the entity definition form, click on the metadata tab. In there, select its type as KPI, and subtype as operational. Apply to keep the changes. Repeat the same process to for all leaf nodes in the tree, i.e., application errors, traffic, conversion rate and avg. ticket. The subtype of the last three can be set as "business" as that is the type of metric measured in their case. Note that entities of type "KPI" are displayed as squares in the model. Publish to save all changes. |
|
14 | Click one-by-one on all non-KPI entities in the model and, in the entity definition form, configure the following for them:
Apply all individual changes and publish to save them all. | |
15 | Finally, click on the model global properties menu to show all options relative to the e-commerce model and set time range > amount and unit to ‘1 d’ (one day). This setting specifies the rolling time window the application will consider for all data analysis processes. |
|
Once all these steps are finished, the model will be available for its first execution. To do that, navigate to the available models section in the administration main menu and verify that "e-commerce" appears in the list of available models. Click on the play button to run the model from there.
After the loading process is finished, something similar to the next screenshot should be displayed:
