More recent posts from the Servicenav team
Use case: You manage an infrastructure on the Azure and / or AWS Cloud. You want to have unified monitoring, and to aggregate in a readable and efficient way the various information coming from the dedicated platforms? Service templates for Azure PaaS and AWS Cloudwatch allow you to monitor all metrics associated with PaaS objects and, using ServiceNav as a hypervisor for your cloud environments, complement Azure and AWS management consoles.
We offer two new generic Service Templates : MS-Azure-PaaS-Metrics_v2 & AWS-Paas-cloudwatch
Do you want to know more and understand the value of these new templates and implement them in your production environment? see this article
When a Dashboard is shared via the Dashlink feature, the share button will now appear, allowing you to know which dashboard is already shared, and avoid additional clicks.
The “Site” column is now present in the list of deployed services (Configuration> Services> List)
It is now possible to define a connection to ITSM (ticketing tool) at the level of a managed client.
Use case: you are a managed service provider, you use several ITSM tools (or instances), according to your customers requirements.
You want to enable a customer-specific ServiceNav – ITSM integration so that tickets created on an alert appear in the customer-specific instance.
We introduce, at ServiceNav 4.6, the first version of our new Import and Mass Update module.
Continuing with the export of services checks, instigated in version 4.4, we have implemented a mass import and update mechanism for services.
Use case: You are a managed service provider or end customer, wishing to integrate or update a large number of services. The use of mass import saves time on configuration operations, and reduces production lead time for your new environment.
This feature is not currently available via the interface, and should be used by a consultant as part of a customer network project or integration.
In future releases, this feature will be extended to hosts and user services, and will have a graphical interface for end-user configuration.
Reminder: in accordance with our strategy of transitioning to a Ubuntu 16.04 SNBox estate, and as indicated in the release note of version 4.3.0, new plug-ins are no longer deployed on SNBox version Ubuntu 12.04 as of version 4.3. 0.