EV Observe - Configure Service Templates
Service templates are used to configure a common set of properties that will be applied to services. Each service will then automatically inherit the information defined for the associated service template. This information can be customized, e.g. arguments, periods, control intervals, warning and critical thresholds, etc.
Each service template:
- Is associated with a company/site.
- Can be used to define the availability and controls required for monitoring services.
Examples
- The F_MS-Azure-PaaS-Metrics service template is used to define the information required for monitoring Azure PaaS metrics.
- The SQL - Connection failed service is created using this service template and will inherit the controls for monitoring Azure PaaS metrics.
Notes
- EasyVista provides a service template catalog with over 1,500 service templates. You cannot delete or modify an existing one.
- Customers can add service templates based on their requirements.
Best Practice
- Duplicate a service template from the catalog and adapt the default parameters based on your requirements.
- Give a prefix to the custom service templates so that you can identify them easily among those available in the service template catalog.
Menu access
Configuration > Services > Templates
Screen description
General Information
Name: Name of the service template.
Business impact: Impact of the service template within the corporate information system in the event of failure.
Category: Report category of the service template.
Must be updated after adding:
BI category: BI category associated with the service template, used in performance analysis activity reports.
Inventory: Used to associate inventory data with the service template. This data is returned in reports that associate inventory data with monitoring data.
Instruction: User-defined text or automatically clickable link displayed when the status is not OK. This enables the operations team to process the incident faster and more efficiently.
See Instruction URLs
Information on availability rate
Availability rate: Target availability rate for the services created using the service template.
Availability period: Timeslot during which the availability rate is calculated. This usually corresponds to the SLA availability target.
Check properties
Is volatile: Used to indicate if the services created using the service template are subject to frequent and brief changes in status.
example Unstable network link
Normal check interval: Interval between the running of two controls (in minutes), applicable to the services created using the service template.
Check Timeslot: Default control period applicable to the services created using the service template.
Additional checks: Number of times the control is repeatedly run, if its initial status is not OK, before sending the first notification.
- If additional controls are defined, the status to be confirmed (SOFT) corresponds to the initial control status and the confirmed status (HARD) corresponds to the status returned after the last additional control is run.
- The sending of notifications and the calculation of the availability rate are based on the confirmed status.
- Interval: Interval between the running of two additional controls (in minutes).
- Time before first notification: Time automatically calculated based on the number of additional controls and the interval between the running of two additional controls.
example Additional controls = 4; Interval = 5
- If an incident is detected during the initial control, the monitoring control will be run every five minutes, up to a maximum of four times, as long as the status to be confirmed is not OK.
- The time before the first notification is sent or before the first confirmed status will be equal to 20 minutes (4 * 5).
Command: Command run by the services created using the service template. The command runs a plugin on the Box and returns a result, i.e. a metric or status.
Active checks: Used to indicate if controls for the services created using the service template will be run automatically based on the control interval.
Passive checks: Used to indicate if controls for the services created using the service template will be run manually and immediately on demand.
Description
Description: Role of the service template within the corporate information system.
Procedures
How to create a service template
Step 1: Select the company where you want to implement the new service template
SelectCompanyInCompanyTree_Procedure
1. Go to the Web app.
2. Select the company from the company tree structure.
Notes:
- The selected company must be associated with a Box.
- You can create a new company. See the procedure
Step 2: Create the new service template
1. Select Configuration > Services > Templates in the menu.
2. Click Add.
3. Specify the information on the new service template.
4. Click Apply.
The service template will be created.
- It will be visible to the company and all lower-level sites.
- It can be used to deploy new services.