Documentation OVH

Code Instrumentation : Monitor an App

Monitor your apps through code instrumentation

Last updated 15th May, 2018

This page is a Work in Progress.

Why instrumenting your app?

Monitor your applications

Sometimes, server monitoring is not enough. You may need deep insights about your application. Questions like "How is my latency doing since the last upgrade?" are keys to provide a fast and reliable service, especially when you're using micro-services, as you're multiplying points of failures. Every library, subsystem and service should have at least a few metrics to give you a rough idea of how it is performing.

There's many libraries to help you create metrics from the runtime of your application. In most of the languages, you'll be able to find a client library to exposes them. Prometheus has a "client libraries" list compatible with Metrics, as we support Prometheus thanks to "Beamium", our opensource Warp 10™ & Prometheus metrics scraper.

Monitor your third-party applications

Now that you are monitoring both your servers and application, you can also monitor third-party applications like HAProxy or PostgreSQL. There are a number of libraries and servers which help in exporting existing metrics from third-party systems as metrics. This is useful for cases where it is not feasible to instrument a given system. You'll be able to find multiples exporters for each supported protocols. We recommend the list provided by "Prometheus".

Cette documentation vous a-t-elle été utile ?

Génial ! Ravi d'avoir pu vous aider.

Images, contenu, structure... N'hésitez pas à nous dire pourquoi afin de la faire évoluer ensemble !

Merci beaucoup pour votre aide ! Vos retours seront étudiés au plus vite par nos équipes..

Ces guides pourraient également vous intéresser...