Skip to content

Add Query activity documentation for 9.4#5739

Open
florent-leborgne wants to merge 16 commits intomainfrom
query-activity-docs
Open

Add Query activity documentation for 9.4#5739
florent-leborgne wants to merge 16 commits intomainfrom
query-activity-docs

Conversation

@florent-leborgne
Copy link
Copy Markdown
Member

Summary

Adds documentation for the new Query activity page in Kibana, a new feature shipping in 9.4 that provides real-time visibility and control over queries currently running in an Elasticsearch cluster.

  • New page: deploy-manage/monitor/query-activity.md — covers prerequisites, accessing the page, viewing and filtering running queries, inspecting query details in the flyout, canceling queries, and configuring the minimum running time threshold
  • TOC update: added under deploy-manage/monitor alongside cluster health and task manager monitoring
  • Cross-link: added a tip in the query tracing troubleshooting page pointing to the new Query activity page

Screenshots

Warning

The screenshots included in this PR are temporary placeholders taken during development. They need to be properly captured from a final build before this PR is merged.

Related

Test plan

  • Preview the page at deploy-manage/monitor/query-activity and verify rendering
  • Verify the cross-link from the tracing troubleshooting page resolves correctly
  • Replace temporary screenshots with final ones before merging
  • Coordinate merge timing with the Kibana feature PR

Made with Cursor

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 1, 2026

Vale Linting Results

Summary: 1 suggestion found

💡 Suggestions (1)
File Line Rule Message
deploy-manage/monitor/logging-configuration/elasticsearch-deprecation-logs.md 63 Elastic.WordChoice Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

Copy link
Copy Markdown
Contributor

@consulthys consulthys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great start! A few comments below

: The unique identifier for the {{es}} task. Select the task ID to open the [query details flyout](#inspect-query-details).

**Query type**
: The query language used: ES|QL, DSL, EQL, SQL, MSearch, Async search, or Other.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only ES|QL, DSL, EQL, SQL

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lmk when this is confirmed, i'll adjust

Adds documentation for the new Query activity page in Kibana
(Stack Management → Cluster performance → Query activity), which
provides real-time visibility into running queries and the ability
to cancel them.

- New page: deploy-manage/monitor/query-activity.md
- TOC entry under deploy-manage/monitor
- Cross-link from the query tracing troubleshooting page
- Temporary screenshots (to be replaced before GA)

Closes #5451

Made-with: Cursor
- Fix setting name: query_activity:minRunningTime (not running_queries:)
- Add serverless: unavailable to page-level applies_to

Made-with: Cursor
- Fix Source column/flyout: text only, not a link
- Fix query type filter: dynamic options based on current data
- Fix Source description: extracted from X-Opaque-Id set by Kibana
- Fix Vale ellipsis warning
- Add cross-links between Query activity and background search pages

Made-with: Cursor
- Opening now explains the problem Query activity solves
- Note that this is real-time only, with links to slow logs and AutoOps
- Clarify relationship between Trace ID, Source, and Opaque ID

Made-with: Cursor
- Trace ID: describe actual behavior (Discover link with 10min range)
- Opaque ID: remove editorial framing, keep factual relationship to Source

Made-with: Cursor
Made-with: Cursor
@florent-leborgne florent-leborgne marked this pull request as ready for review April 1, 2026 14:18
@florent-leborgne florent-leborgne requested review from a team as code owners April 1, 2026 14:18
Copy link
Copy Markdown
Contributor

@wajihaparvez wajihaparvez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! ⭐️

- Remove pain-point opening sentence (rayafratkina)
- Link "required privileges" to prerequisites section (wajihaparvez)
- Move flyout intro sentence after screenshot (wajihaparvez)
- "including" → "such as" in troubleshoot tip (wajihaparvez)

Made-with: Cursor
@shainaraskas
Copy link
Copy Markdown
Collaborator

can you introduce this in the parent monitoring page too?

@shainaraskas
Copy link
Copy Markdown
Collaborator

also, is this the same as this feature? #5039

@consulthys
Copy link
Copy Markdown
Contributor

also, is this the same as this feature? #5039

No, but they complement each other, you can find more on this here #5741


To learn more about the health and performance tools in {{ecloud}}, refer to [](/deploy-manage/monitor/cloud-health-perf.md).

## Query activity
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fyi @consulthys in your PR, we should reframe this so we can see that there is one util for current query activity and one for historic activity (under one heading). let me know if you need a hand there

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Internal]: Docs for the new "Query Activity" UI in Kibana

5 participants