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.

Sign up for GitHub

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

[DOC] Add flush_to_storage to metrics-gen config doc #4627

Merged
merged 1 commit into from
Jan 28, 2025
+7 −3
Merged

[DOC] Add flush_to_storage to metrics-gen config doc #4627

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/sources/tempo/configuration/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -494,7 +494,11 @@ metrics_generator:
# If enabled, only parent spans or spans with the SpanKind of `server` will be retained
[filter_server_spans: <bool> | default = true]

# Number of blocks that are allowed to be processed concurently
# Whether server spans should be flushed to storage.
# Setting `flush_to_storage` to `true` ensures that metrics blocks are flushed to storage so TraceQL metrics queries against historical data.
[flush_to_storage: <bool> | default = false]

# Number of blocks that are allowed to be processed concurrently.
[concurrent_blocks: <uint> | default = 10]

# A tuning factor that controls whether the trace-level timestamp columns are used in a metrics query.
Expand Down
2 changes: 1 addition & 1 deletion docs/sources/tempo/release-notes/v2-6.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -170,7 +170,7 @@ metrics_generator:

**For historical data**

To run metrics queries on historical data, you must configure the local-blocks processor to flush rf1 blocks to object storage:
To run metrics queries on historical data, you must configure the local-blocks processor to flush RF1 blocks to object storage:

```yaml
metrics_generator:
Expand Down
2 changes: 1 addition & 1 deletion docs/sources/tempo/setup/upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,7 +205,7 @@ metrics_generator:

**For historical data**

To run metrics queries on historical data, you must configure the local-blocks processor to flush rf1 blocks to object storage:
To run metrics queries on historical data, you must configure the local-blocks processor to flush RF1 blocks to object storage:

```yaml
metrics_generator:
Expand Down
Loading