tempo
tempo copied to clipboard
Document the scaling approach for each service
The Operations section in the docs needs a snippet on the recommended scaling approach for each service and any gotchas associated.
For instance - can we scale up ingesters rapidly - impact on read/write path, can we scale up query frontends beyond 2 - impact on read path?
This might be associated with the capacity planning. See #543
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity. Please apply keepalive label to exempt this Issue.