Suggestion: Reserve a port number for private exporters

[Till Backhaus]

Prometheus reserves quite a few port numbers for exporters: https://github.com/prometheus/prometheus/wiki/Default-port-allocations

Me and my team wrote prometheus exporters for internal applications and I'd guess other people did as well. Currently people have to think about which port to use and I see two strategies applied:
a) Use a port number that is a little like the application about to be instrumented:
"My app is something like a webserver, so I'm gonna use port number 9113 (assigned to nginx-exporter)."

b) Use a port number that is unlikely to be used in the environment.
"I think no one uses fritzboxes in my environment, so I'm gonna use port number 9173 (assigned to fritzbox-exporter)."

Any way, people are thinking about it more than they should have to in my opinion. I therefore propose to reserve a port number for exporters of internal applications:
Ideally the number is easy to remember and easily found on https://github.com/prometheus/prometheus/wiki/Default-port-allocations. So I propose to officially reserve 9099 for that purpose.
"I'm writing an exporter for a private app so I'm gonna use port 9099 for it.

Yes, all strategies will lead to port-collisions in environments that are prone to it and those people will have to assign port numbers themselves.

Any thoughts? I'll try to add a section to the port allocations document on may 22nd if nobody stops me here.

Cheers,

Till

[Tobias Schmidt]

I don't mind reserving a port number for internal exporters, but is one enough for that?

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To post to this group, send email to promethe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/21b41708-e13c-4e15-b8b3-24a766373cee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brian Brazil]

The default port numbers are suggestions so that if a user trying out a few different components they're unlikely to run into a collision.

If you need numbers that are pure internal, then that's likely to follow your organisation's own internal numbering scheme so there's not much point in us trying to second guess that. If you're trying to pick numbers for this, I'd suggest something completely outside the ranges we use.

--

Brian Brazil

www.robustperception.io

[Ben Kochie]

+1, I would suggest using something completely outside of the Prometheus reserved range for internal systems that use separate ports for telemetry.

--

You received this message because you are subscribed to the Google Groups "Prometheus Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-users+unsubscribe@googlegroups.com.
To post to this group, send email to prometheus-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/CAHJKeLodoVL5to%2BT%3DwUOaz%3DeZQNkpM9xD_c9_Kmx7OirqxAECQ%40mail.gmail.com.

[back...@traum-ferienwohnungen.de]

Ok, I'm fine with that too. I opened https://github.com/prometheus/docs/pull/744 to integrate your suggestions into official docs.

Am Montag, 15. Mai 2017 14:13:01 UTC+2 schrieb Ben Kochie:

+1, I would suggest using something completely outside of the Prometheus reserved range for internal systems that use separate ports for telemetry.

On May 15, 2017 12:29, "Brian Brazil" <brian....@robustperception.io> wrote:

On 15 May 2017 at 11:18, Till Backhaus <ti...@backha.us> wrote:

Prometheus reserves quite a few port numbers for exporters: https://github.com/prometheus/prometheus/wiki/Default-port-allocations

Me and my team wrote prometheus exporters for internal applications and I'd guess other people did as well. Currently people have to think about which port to use and I see two strategies applied:
a) Use a port number that is a little like the application about to be instrumented:
"My app is something like a webserver, so I'm gonna use port number 9113 (assigned to nginx-exporter)."

b) Use a port number that is unlikely to be used in the environment.
"I think no one uses fritzboxes in my environment, so I'm gonna use port number 9173 (assigned to fritzbox-exporter)."

Any way, people are thinking about it more than they should have to in my opinion. I therefore propose to reserve a port number for exporters of internal applications:
Ideally the number is easy to remember and easily found on https://github.com/prometheus/prometheus/wiki/Default-port-allocations. So I propose to officially reserve 9099 for that purpose.
"I'm writing an exporter for a private app so I'm gonna use port 9099 for it.

Yes, all strategies will lead to port-collisions in environments that are prone to it and those people will have to assign port numbers themselves.

Any thoughts? I'll try to add a section to the port allocations document on may 22nd if nobody stops me here.

The default port numbers are suggestions so that if a user trying out a few different components they're unlikely to run into a collision.

If you need numbers that are pure internal, then that's likely to follow your organisation's own internal numbering scheme so there's not much point in us trying to second guess that. If you're trying to pick numbers for this, I'd suggest something completely outside the ranges we use.

--

Brian Brazil

www.robustperception.io

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To post to this group, send email to promethe...@googlegroups.com.