mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Peach (JIRA)" <>
Subject [jira] [Commented] (MESOS-6918) Prometheus exporter endpoints for metrics
Date Fri, 14 Jul 2017 06:09:00 GMT


James Peach commented on MESOS-6918:

Implementation notes:

* I'm proposing this only for the {{/metrics/snapshot}} endpoint
* Prometheus (at least v2) doesn't send an {{Accept}} header, so we can't mux on that to produce
Prometheus output. We need to require a separate endpoint or query parameter.
* [~klueska] suggests using a query parameter to explicitly request Prometheus output
* The standard endpoint for exporters is {{/metrics}} (this is the prometheus configuration
* The mapping from {{Accept}} to exposition format is done in [expfmt.Negotiate|].
The text format is the default.
* As per [#2788|], Prometheus v2 doesn't
support the protobuf exposition; {{text/html+gzip}} is recommended.
* Prometheus does send a {{Accept-Encoding: gzip}} header.
* Prometheus will send the {{X-Prometheus-Scrape-Timeout-Seconds}} header with the request
timeout it is planning to use.

> Prometheus exporter endpoints for metrics
> -----------------------------------------
>                 Key: MESOS-6918
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>          Components: statistics
>            Reporter: James Peach
>            Assignee: James Peach
> There are a couple of [Prometheus|] metrics exporters for Mesos,
of varying quality. Since the Mesos stats system actually knows about statistics data types
and semantics, and Mesos has reasonable HTTP support we could add Prometheus metrics endpoints
to directly expose statistics in [Prometheus wire format|],
removing the need for operators to run separate exporter processes.

This message was sent by Atlassian JIRA

View raw message