#prometheus (2019-05)

prometheus

Archive: https://archive.sweetops.com/prometheus/

2019-05-30

Abel Luck avatar
Abel Luck

any advice on the simplest prometheus service discovery options? we’ve a small deployment of dynamic services and am looking for something lightweight

Abel Luck avatar
Abel Luck

dns discovery seems like it might be the best. but the docs are lacking, how to provide custom /metrics path and port ?

tamsky avatar
tamsky

@Abel Luck have you checked out the example configs for DNS service discovery?

That’s a full example that touches most of the things you mentioned

  • endpoint lookup by DNS name (Lines 96-99)
  • custom /metrics path (Line 90)
  • and to get a custom port, I’d replace Line 91 (scheme: https) with port: <custom#>
Configuration | Prometheus

An open-source monitoring system with a dimensional data model, flexible query language, efficient time series database and modern alerting approach.

prometheus/prometheus

The Prometheus monitoring system and time series database. - prometheus/prometheus

Abel Luck avatar
Abel Luck

@tamsky thanks for the link to the example configs, I didn’t know about that.

However, when i meant custom path/port I meant a config such that the path and port are discovered from the DNS SRV entry

tamsky avatar
tamsky

Port should be automatic if you’re using SRV records

tamsky avatar
tamsky

You don’t typically need to adjust the path, as it’s always /metrics on standard exporters. What’s your use case where the /metrics endpoint also needs to be discoverable?

tamsky avatar
tamsky

afaik, there’s no custom SRV record type that provides more than service port and weight.

    keyboard_arrow_up