public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[DOC] Changed so max_spans_per_span_set can't be changed in Cloud Traces (#115914)

Browse Source 
Changed so max_spans_per_span_set can't be changed in Cloud Traces
This commit is contained in:
Kim Nylander
2026-01-07 15:46:02 -05:00
committed by GitHub
parent 9598ae6434
commit a53875e621
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/shared/datasources/tempo-editor-traceql.md
+4 -1
View File
@@ -135,9 +135,12 @@ You can use the **Span Limit** field in **Options** section of the TraceQL query
This field sets the maximum number of spans to return for each span set. This field sets the maximum number of spans to return for each span set.
By default, the maximum value that you can set for the **Span Limit** value (or the spss query) is 100. By default, the maximum value that you can set for the **Span Limit** value (or the spss query) is 100.
In Tempo configuration, this value is controlled by the `max_spans_per_span_set` parameter and can be modified by your Tempo administrator. In Tempo configuration, this value is controlled by the `max_spans_per_span_set` parameter and can be modified by your Tempo administrator.
Grafana Cloud users can contact Grafana Support to request a change.
Entering a value higher than the default results in an error. Entering a value higher than the default results in an error.
{{< admonition type="note" >}}
Changing the value of `max_spans_per_span_set` isn't supported in Grafana Cloud.
{{< /admonition >}}
### Focus on traces or spans ### Focus on traces or spans
Under **Options**, you can choose to display the table as **Traces** or **Spans** focused. Under **Options**, you can choose to display the table as **Traces** or **Spans** focused.