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

docs: document metrics-generator ring #1316

Merged
merged 2 commits into from
Apr 13, 2022

Conversation

kvrhdn
Copy link
Member

@kvrhdn kvrhdn commented Mar 1, 2022

What this PR does:
Extend the API reference and the consistent hash ring page to list the new metrics-generator ring.

This is the first (of many) PRs to document the metrics-generator. We will also have to describe the new config options in the configuration section and update various other pages.

Which issue(s) this PR fixes:
Related to #1303

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

docs/tempo/website/api_docs/_index.md Outdated Show resolved Hide resolved
docs/tempo/website/api_docs/_index.md Outdated Show resolved Hide resolved
docs/tempo/website/api_docs/_index.md Outdated Show resolved Hide resolved
docs/tempo/website/operations/consistent_hash_ring.md Outdated Show resolved Hide resolved
docs/tempo/website/operations/consistent_hash_ring.md Outdated Show resolved Hide resolved
docs/tempo/website/operations/consistent_hash_ring.md Outdated Show resolved Hide resolved
Co-authored-by: Karen Miller <84039272+KMiller-Grafana@users.noreply.github.com>
@kvrhdn
Copy link
Member Author

kvrhdn commented Mar 3, 2022

Thank you for the suggestions @KMiller-Grafana. Should I apply the same changes to the other sections on these pages?
Every ring has more or less the same information, but the new ring will have improved wording now.

**Participants:** Metrics-generators
**Used by:** Distributors

This ring is used by distributors to load balance traffic to the metrics-generators. When spans are received, the trace ID is hashed, and the traces are sent to the appropriate metrics-generators based on token ownership in the ring.
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we mention what the hash is?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think that's an implementation detail of the ring in dskit. How a hash ring works is explained here: https://cortexmetrics.io/docs/architecture/#the-hash-ring (this link is also on the top of this page in the docs)

@kvrhdn kvrhdn dismissed KMiller-Grafana’s stale review April 13, 2022 14:57

Comments have been addressed

@kvrhdn kvrhdn merged commit 872c121 into grafana:main Apr 13, 2022
@kvrhdn kvrhdn deleted the kvrhdn/metrics-generator-ring-docs branch April 13, 2022 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants