More recent posts from the Servicenav team
We saw in the previous article the issues and methodology surrounding selection of monitoring tools.
Now let’s see how to implement this using a real case and the ServiceNav approach
To illustrate our point, let’s start with a practical case: a French commercial company of about 3000 users, spread over ten network sites, hosting its information system in a hybrid cloud on about 1500 virtual machines (office and email at Microsoft , a business application for CAPM accessed using thick-clients from each site, an e-commerce web application developed and maintained by the R & D team based on Microsoft Azure PaaS objects).
Monitoring is provided using open source software. The two employees in charge of its configuration have just left the company, 20% of the 3000 checks are not in OK condition. No availability stats are published.
The company is engaged in an ISO 9001 certification renewal process.
Evaluation of an APM solution is in its final phase. At the same time, the network team has just completed a collection and analysis of system and security logs with an open source SIEM tool. Finally, the CAPM application manager has been impressed with what he saw during a webinar on a scenario recording tool.
The IT environment is changing, with the implementation of Citrix virtual desktop technology across all sites. The IT department estimates that the whole business will express desires to have an overall and correlated view of key indicators. Such technical indicators will have to be maintained.
The IT department agrees to move onto the next stage…
Firstly, collection and presentation of data at all levels; both technical and business: hardware, network, system and middleware, databases and applications, health status and metrics on IaaS instances and PaaS objects . Tool selection was made on the relevance and completeness of the monitoring capabilities, the software publishers roadmap for the future, the flexibility of the software, its ergonomics and ease of configuration and migration from the current Open Source configuration. Thus, the company was able to immediately produce availability KPIs, and securely monitor its environment.
A SaaS solution was chosen, in order to allow the teams to focus on the business of management, and not on performing monitoring solution upgrades, nor ensuring its availability. Then, it was decided to integrate the monitoring with the ticket management tool: thereby, traceability of changes to the information system to correct deficiencies in the IT infrastructure was achieved. The IT department and R & D then decided to implement, in a DevOps way, automation of the deployment, monitoring and removal of all devices, based on the CMDB of an ITSM and the Web Services integration offered by the monitoring tool.
Finally, the e-commerce web application was instrumented using a market APM tool. A SIEM tool was implemented to enhance the real-time security log collection and monitoring. The main APM and SIEM indicators are forwarded into the monitoring tool and enrich existing business-service dependencies, allowing a quick diagnosis between a network problem, system or application, or security.
These application ‘bricks’ complement each other. The monitoring tool collects all the data, performs the correlations and the calculation of the indicators presented in the management committee, produces the dashboards, for management or communication purposes.
By using this real example, we wanted to position the ServiceNav product within a monitoring project journey: optimized migration from Open Source solutions based on Nagios, a catalog with more than 1500 multi-technology templates, one of the most innovative SaaS Big Data offers in the monitoring market, IT Weather services, Dataviz driven dashboards, multiple integrations with APM applications, ticketing and synthetic transaction platforms…
… and above all, the passion and desire of our team from which all our Customers and Partners benefit.
Does this sound interesting to you? Contact us …