Add query logging settings to Elasticsearch configuration reference
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- elasticsearch
- Domain
- documentation
Research direction
Start with the Elasticsearch configuration reference and review PR #5039 to identify the query logging settings it introduced. Add those settings in a new Logging section or an appropriate Monitoring location, and verify that the reference covers the feature and matches the existing documentation structure.
Written by the indexing model from the issue text.
Description
Context
Raised in https://github.com/elastic/docs-content/pull/5039#issuecomment-4338735528.
Impacted page: https://www.elastic.co/docs/reference/elasticsearch/configuration-reference
The new query logging feature (#5039) introduces cluster-level configuration settings, but these are not listed on the Elasticsearch configuration reference page.
Definition of done
- Add a new "Logging" section (or similar) to the configuration reference that includes the query logging settings
- Consider whether to colocate under "Monitoring" or create a standalone "Logging settings" section, since logging configuration lives under Monitoring > Logging in the docs navigation
- Dominant language
- No language data
- Stars
- 47
- Forks
- 262
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 127
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from elastic/docs-content
-
bug community triaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
elastic/docs-content#8393 · 1 comment · 1 reaction ·
-
documentation Team:SKI triaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
elastic/docs-content#8375 · 1 comment · 1 reaction ·
-
documentation Team:SKI triaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
elastic/docs-content#8374 · 1 comment · 1 reaction ·
-
documentation Serverless Team:SKI triaged
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
elastic/docs-content#8352 · 1 comment · 1 reaction ·
-
documentation Team:SKI triaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
elastic/docs-content#8342 · 1 comment · 1 reaction ·
All issues in elastic/docs-content
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100