Commit 83f3ae57 authored by Julius Volz's avatar Julius Volz

Improve client lib and exposition format wording.

parent fdfc1adc
......@@ -5,13 +5,9 @@ sort_rank: 1
# Client libraries
If you want to monitor services which do not have existing Prometheus
instrumentation, you will need to instrument your application's code via one of
the Prometheus client libraries.
First, familiarize yourself with the Prometheus-supported
[metric types](/docs/concepts/metric_types/). To use these types programmatically, see
your specific client library's documentation.
Before you can monitor your services, you need to add instrumentation to their
code via one of the Prometheus client libraries. These implement the Prometheus
[metric types](/docs/concepts/metric_types/).
Choose a Prometheus client library that matches the language in which your
application is written. This lets you define and expose internal metrics via an
......@@ -25,6 +21,5 @@ When Prometheus scrapes your instance's HTTP endpoint, the client library
sends the current state of all tracked metrics to the server.
If no client library is available for your language, or you want to avoid
dependencies on a client library, you may also implement one of the supported
[exposition formats](/docs/instrumenting/exposition_formats) yourself to
expose metrics.
dependencies, you may also implement one of the supported [exposition
formats](/docs/instrumenting/exposition_formats) yourself to expose metrics.
......@@ -5,12 +5,14 @@ sort_rank: 2
# Exposition formats
Prometheus implements two different transfer formats which clients may use to
Prometheus implements two different wire formats which clients may use to
expose metrics to a Prometheus server: a simple text-based format and a more
efficient and robust protocol-buffer format. Prometheus servers and clients
use [content negotation](http://en.wikipedia.org/wiki/Content_negotiation)
to establish the actual format to use. A server will prefer receiving the
efficient and robust protocol-buffer format. Prometheus servers and clients use
[content negotation](http://en.wikipedia.org/wiki/Content_negotiation) to
establish the actual format to use. A server will prefer receiving the
protocol-buffer format, and will fall back to the text-based format if the
client does not support the former.
For details on each format, see the [Client Data Exposition Format](https://docs.google.com/document/d/1ZjyKiKxZV83VI9ZKAXRGKaUKK2BIWCT7oiGBKDBpjEY/edit?usp=sharing) document.
For details on each format and the content negotiation options, see the
[Client Data Exposition Format](https://docs.google.com/document/d/1ZjyKiKxZV83VI9ZKAXRGKaUKK2BIWCT7oiGBKDBpjEY/edit?usp=sharing)
document.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment