Rationale behind default HTTP Port 80 #4945
Closed
martialblog
started this conversation in
General
Replies: 1 comment 2 replies
-
Hi @martialblog. You bring a good point. I don't think there's a good explanation besides it's been carried over since the beginning of the project. It would make sense to be changed to |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I was just curious about the default HTTP port being set to 80:
Is there any reason behind this? Generally this is considered a privileged port, which I don't see for an application like Tempo.
Obviously this does not matter that much, since port 3200 is set in most of the configuration and the packages provided by Grafana Labs, but still wouldn't it be simpler to just have the default 3200?
Also, when looking at Mimir and Tempo, the default HTTP ports don't have a pattern, right? I'm strictly speaking Golang code, not additional configuration:
Personally, I would expect them to either all have the same port (I think this is the case for gRPC and Gossip ports) or to have something like 3100, 3200, 3300 (given that the grafana-server uses 3000 by default).
Thanks
Markus
Beta Was this translation helpful? Give feedback.
All reactions