More recent posts from the Servicenav team
Alerts from monitored applications, with their numerous dependencies, can cause problems with information clarity; especially when it comes to creating a “dashboard” type representation. Ambiguity of information can prevent you from taking the right actions at the right time – the technician being flooded with an array of unstructured information.
A good application mapping begins with a well structured resume of the components of the application. A blog article is dedicated to this subject, using a web application as its example. The MAP widget allows for different maps. It is perfect for mapping an application.
Depending on its nature and its complexity, it should be possible to represent:
The addition of images and tables will give structure the data presented.
Endeavour to use user services, in order to have a minimum of items on the screen.
Define a user service grouping ‘databases’, and another for the ‘infrastructure’ that carries the application. These two user services can then be combined as elements of another user service which bears the name of the application.
According to the needs and the number of applications to monitor, you can choose to represent an application by a service, or be able to drill down into the details.
here are some examples of visualisaing Applications using the ServiceNav MAP feature: