elastic/elasticsearch

Feature Request - query/fetch/scroll failure count stats

Open

#46,641 opened on Sep 11, 2019

View on GitHub
 (15 comments) (0 reactions) (0 assignees)Java (25,882 forks)batch import
:Core/Infra/Stats>featureTeam:Core/Infragood first issue

Repository metrics

Stars
 (76,700 stars)
PR merge metrics
 (Avg merge 2d) (1,000 merged PRs in 30d)

Description

Describe the feature: Today there are helpful shard level search stats on query_total/fetch_total etc. Can we augment it with failure stats as well eg. query_failure_total; fetch_failure_total etc?

Is there any other existing way to already get shard/search failure rates except tracking it on the client side?

Contributor guide

Research direction
Locate existing shard level search stats (query total, fetch total) in the Elasticsearch codebase, likely in the search service or shard level stats classes. Understand how they are incremented and add corresponding failure counters (query failure total, fetch failure total) by tracking exceptions in the query/fetch phases.
Tech stack
java
Domain
backendsearchdatabaseobservability
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaElasticsearch
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60