max_outstanding_per_tenant config worng

[lovesharepc]

Describe the bug
follow doc
https://grafana.com/docs/tempo/latest/configuration/#:~:text=max_outstanding_per_tenant

query_frontend:
  search:
    max_outstanding_per_tenant: 10000

will get error

failed parsing config: failed to parse configFile /etc/tempo.yaml: yaml: unmarshal errors:
line 100: field max_outstanding_per_tenant not found in type frontend.SearchConfig

use api check
real config is

query_frontend:
  max_outstanding_per_tenant: 10000
  search:
    

To Reproduce

Expected behavior

Environment:

• Infrastructure: [docker]
• Deployment tool: [docker]

Additional Context

tempo, version 2.1.1 (branch: HEAD, revision: 4157d7620)
  build user:       
  build date:       
  go version:       go1.20.3
  platform:         linux/amd64
  tags:             unknown

[joe-elliott]

Nice, Thanks for the report!

cc @knylander-grafana

[github-actions]

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.

[knylander-grafana]

Thank you for reporting this!

I searched through the doc and max_outstanding_per_tenant is listed in three files:

• configuration/_index.md (page you highlighted) - Fixed in latest release.
• backend_search.md - Indent is correct
• manifest.md (auto-generated) - Indent is correct

I don't think we need any additional changes.