More recent posts from the Servicenav team
A User Service is an aggregation of one or more:
IT Weather (Monitoring> IT Weather) presents the user services through 4 states and 3 trends:
OK / degraded / out of order / unknown constant / up / down
Before designing an IT Weather service, ask the right questions:
Once this analysis has been conducted, it becomes possible to list all the Hosts and Services that make up the User Service; to define time slots and a target availability rate.
If the User Service is complex, it is better to use a hierarchy and create additional User Services, which will comprise this overall User Service.
The relationship between a User Service and its different elements can be of a “blocking” or “degrading” type. To determine which type is correct, it is beneficial to ask the right questions:
If an element of a service is essential to its operation, and is not covered by another component (redundancy) à the element will have a “blocking” impact
If a component of a service may be covered by another component, or is not essential for the minimal functioning of my service à the element will have a “degrading” impact
A properly configured IT Weather is an asset; good reports and dashboards even more so.
A dedicated dashboard: The weather map (“Weather services (map)”)
This dashboard presents the list of User Services, by site / by customer, on a background map.
It is particularly useful in multi-site contexts and also offers value when planning technical interventions (by allowing a technician to reorganize their movements based on nearby breakdowns and their impact).
Other dashboards that present User Services: the “MAP”, the “Monitoring of the estate by family”, …
A high value report: the availability report (“Availability Analysis”)
A real decision-making tool that can be used both internally, or by clients, to testify to the quality of service or to identify areas for improvement, the availability report makes it possible to view:
These indicators allow the stakeholder to: