Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update loki's default port to 3100 #6349

Merged
merged 4 commits into from
Jun 24, 2022

Conversation

simonswine
Copy link
Contributor

@simonswine simonswine commented Jun 9, 2022

I was suprised this was not already the case. I think it would be a good change to make, but I am also contious of the breaking nature of this.

I was suprised this was not already the case. I think it would be a good
change to make, but I am also contious of the breaking nature of this.
@grafanabot
Copy link
Collaborator

./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki

Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell.

+           ingester	0%
+        distributor	0%
+            querier	0%
- querier/queryrange	-0.1%
+               iter	0%
+            storage	0%
+           chunkenc	0%
+              logql	0%
+               loki	0%

@simonswine simonswine marked this pull request as ready for review June 9, 2022 14:24
@simonswine simonswine requested a review from a team as a code owner June 9, 2022 14:24
Copy link
Contributor

@dannykopping dannykopping left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure how I feel about this.

On the one hand, I like it (except for the fact that 3100 is already registered) and a lot of documentation refers to this port
But on the other hand I don't see much value in changing it at this stage
But on the other other hand we expose port 3100 in our docker image, so who the hell knows 🤷 🥲

I think this could cause trouble as you say, for relatively meagre gains.

@chaudum
Copy link
Contributor

chaudum commented Jun 13, 2022

IMO, everything that help simplifying the config is a win, of course mainly for new users (think adoption), since existing users already have the overrides in place.

Regarding the Docker image: Yes, we EXPOSE 3100, but it still requires to set the HTTP port to 3100 in the config that needs to be provided. This is already inconsistent!

Copy link
Collaborator

@trevorwhitney trevorwhitney left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good config simplification, I'm on board with it. @dannykopping are you thinking it's going to break a lot of existing installations because they're relying on this being port 80? I'm pretty sure we have this set in all our of deployments, as well as the jsonnet and helm libraries with publish.

Copy link
Contributor

@cyriltovena cyriltovena left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dannykopping
Copy link
Contributor

This is a good config simplification, I'm on board with it. @dannykopping are you thinking it's going to break a lot of existing installations because they're relying on this being port 80? I'm pretty sure we have this set in all our of deployments, as well as the jsonnet and helm libraries with publish.

Not overly worried, let's see what happens and mention it in our changelog/upgrade guide before merging pls @simonswine

@grafanabot
Copy link
Collaborator

./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki

Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell.

+           ingester	0%
+        distributor	0%
+            querier	0%
+ querier/queryrange	0%
+               iter	0%
+            storage	0%
+           chunkenc	0%
+              logql	0%
+               loki	0%

@grafanabot
Copy link
Collaborator

./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki

Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell.

+           ingester	0%
+        distributor	0.3%
+            querier	0%
+ querier/queryrange	0%
+               iter	0%
+            storage	0%
+           chunkenc	0%
+              logql	0%
+               loki	0%

@simonswine
Copy link
Contributor Author

@dannykopping take a look if the changelog entry works for you like this 👍

CHANGELOG.md Outdated Show resolved Hide resolved
@grafanabot
Copy link
Collaborator

./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki

Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell.

+           ingester	0%
-        distributor	-0.3%
+            querier	0%
+ querier/queryrange	0%
+               iter	0%
+            storage	0%
+           chunkenc	0%
+              logql	0%
+               loki	0%

Copy link
Contributor

@KMiller-Grafana KMiller-Grafana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small grammatical changes to docs.

CHANGELOG.md Outdated Show resolved Hide resolved
docs/sources/upgrading/_index.md Outdated Show resolved Hide resolved
@grafanabot
Copy link
Collaborator

./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki

Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell.

+           ingester	0%
+        distributor	0%
+            querier	0%
+ querier/queryrange	0%
+               iter	0%
+            storage	0%
+           chunkenc	0%
+              logql	0%
+               loki	0%

@simonswine simonswine merged commit b8c9672 into grafana:main Jun 24, 2022
@osg-grafana osg-grafana added type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories and removed area/docs labels Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/S type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants