elastic/kibana

[CCR] Show follower `fatal_exception` in UI

Open

#33,628 opened on Mar 20, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)TypeScript (8,021 forks)batch import
Feature:CCR and Remote ClustersTeam:Kibana Managementbuggood first issuetriage_needed

Repository metrics

Stars
 (19,065 stars)
PR merge metrics
 (Avg merge 1d 16h) (999 merged PRs in 30d)

Description

If a follower falls sufficiently behind a leader that it can no longer replicate operations, this is reported on the get follow stats API as part of indices[].fatal_exception.

Currently this information doesn't surface in the UI. We need to add this to our follower index (de)serialization, and show it in the follower index detail panel, similar to how we surface auto follow pattern errors.

Contributor guide

Research direction
Examine the follower index data model in the Kibana CCR plugin and the get follow stats API response to locate fatal exception. Then, add it to the follower index detail panel UI similar to auto follow pattern errors.
Tech stack
typescriptjavascriptreact
Domain
frontend
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
ElasticsearchKibanaReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60