ServiceNav 4.17

We offer the possibility to migrate your ServiceNav Box to Ubuntu 20.04 LTS.
The operation is performed directly from the interface, no provisioning is necessary.

Responding to feedback following the previous OS upgrade (12.04 → 16.04), we were keen to deliver a much more packaged solution, allowing for effortless and mass updating.

Where previously it was necessary to provision a second box in order to migrate the configuration from the current ServiceNav Box, you are now able to launch the upgrade from the ServiceNav interface for suitable ServiceNav boxes.

Our teams have worked hard to bring you this easy migration, and we are proud of it.

However, there are a few precautions to be taken and you should be aware of them before undertaking the procedure on your ServiceNav Box.

>> Follow the guide!

The ServiceNav Box Ubuntu 20.04 - 4.17 master will be available in a few days on our usual download area, to facilitate your future ServiceNav Box installations.

In order to assist you in the use of mass import/update activities, and when using the APIs, we we now display the IDs associated with the main elements of the application:

End-of-life service templates (replaced by more generic ones or adapted to support newer versions of the target host/application) are now identified as depreciatedand can no longer be used to with a service (either creation or modification).

The templates associated with services already deployed are of course preserved, in order to guarantee the continuity of your monitoring operations.

The description of deprecated templates has been updated to point you to the most suitable replacement template.

For this version, the templates affected are :

It is now possible to search the list of metricsin the detail record of a host or service.
This is particularly useful on checks that return a large number of metrics, and where the names of the metrics are likely to change over time (the old names remaining historical and therefore visible).

Several improvements were made to theintegration with ITSM Artis v3 :

• The default value of the "codeOrgInt" field can now relate to the tag assigned to the host associated with the alert (or the service that triggered the alert)
• The default value of the "domain code" field can now relate to the tag assigned to the host associated with the alert (or the service that triggered the alert)

Several improvements were made to theintegration with the ITSM Akuitéo :

• Linking an acknowledgment to an existing ticket
• Include instructions in the text of the alert
• Management of the default criticality (configurable in the connection)