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: Replace SSD sizing tool with cluster tiers for distributed/microservices mode #15820

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

poyzannur
Copy link
Contributor

@poyzannur poyzannur commented Jan 17, 2025

What this PR does / why we need it:
We are retiring the existing loki sizing tool for SSD mode sizing which was inaccurate.
This PR replaces the tool with a guide to size 3 tiers for Loki clusters based on their expected ingestion patterns. It Adds general notes and guidelines for query performance.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:
Follow up PRs will add

  • retire the code for the sizing tool.
  • guide for RAM based and Disk Based memcached sizing to this doc.
  • update node types on this doc.

Checklist

  • Reviewed the CONTRIBUTING.md guide (required)
  • Documentation added
  • Tests updated
  • Title matches the required conventional commits format, see here
    • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
  • Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
  • If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

@github-actions github-actions bot added the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label Jan 17, 2025
@poyzannur poyzannur changed the title add new tables Update cluster sizing page for distributed/microservices mode Jan 17, 2025
@poyzannur poyzannur changed the title Update cluster sizing page for distributed/microservices mode docs: Update cluster sizing page for distributed/microservices mode Jan 17, 2025
Copy link
Contributor

github-actions bot commented Jan 17, 2025

@poyzannur poyzannur force-pushed the poyzan/update-sizing-calculator branch 2 times, most recently from fd55781 to 2032ba6 Compare January 17, 2025 21:03
@JStickler
Copy link
Contributor

Looking at the preview for this, we probably want to add some instructions so that people know what to do with the information presented here.
I would add a line before the "Node Type?" that says something like, "Select your node type from the following menu." and then before the table add an explanation of what's being displayed in the table, and also make it clear that there are three tabs, because the UI indicator is rather subtle.

@poyzannur poyzannur marked this pull request as ready for review January 20, 2025 16:28
@poyzannur poyzannur requested a review from a team as a code owner January 20, 2025 16:28
@poyzannur poyzannur changed the title docs: Update cluster sizing page for distributed/microservices mode docs: Replace SSD sizing tool with cluster tiers for distributed/microservices mode Jan 20, 2025
@poyzannur poyzannur force-pushed the poyzan/update-sizing-calculator branch from 33bc13f to 995f7a4 Compare January 22, 2025 11:58
Copy link
Contributor

@Jayclifford345 Jayclifford345 left a comment

Choose a reason for hiding this comment

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

Just a couple of notes from me! Such a great win for the docs @poyzannur !

This tool helps to generate a Helm Charts `values.yaml` file based on specified
expected ingestion, retention rate and node type. It will always configure a
[scalable]({{< relref "../../get-started/deployment-modes#simple-scalable" >}}) deployment. The storage needs to be configured after generation.
This section is a guide to size base resource needs of a Loki cluster.
Copy link
Contributor

Choose a reason for hiding this comment

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

I can't select the right line as a comment but lines 2 - 4 will need to be removed so it appears in the docs

_build:
  list: false
noindex: true


Based on the expected ingestion volume, Loki clusters can be categorised into three tiers. Recommendations below are based on p90 resource utilisations of the relevant components. Each tab represents a different tier.
Please use this document as a rough guide to specify CPU and Memory requests in your deployment. This is only documented for microservices/distributed mode at this time.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Please use this document as a rough guide to specify CPU and Memory requests in your deployment. This is only documented for microservices/distributed mode at this time.
Please use this document as a rough guide to specify CPU and Memory requests in your deployment. This is only documented for [microservices/distributed](https://grafana.com/docs/loki/<LOKI_VERSION>/get-started/deployment-modes/#microservices-mode) mode at this time.


<blockquote v-if="help">
<span v-if="help === 'ingest'">
Defines the log volume in gigabytes, ie 1e+9 bytes, expected to be ingested each day.
</span>
<span v-else-if="help === 'node'">
Defines the node type of the Kubernetes cluster. Is a vendor or type
Copy link
Contributor

Choose a reason for hiding this comment

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

Just looking at how this renders:
https://deploy-preview-loki-15820-zb444pucvq-vp.a.run.app/docs/loki/latest/setup/size/

I wonder if we move this span up and change the wording

<span v-else-if="help === 'node'">
We currently recommend these nodes when running a production cluster of Loki. If a vendor, type or latest release is missing please let us know!
</span>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/L 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.

3 participants