Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Logs UI] Implement “no data” check to drive the “no data screens” for Logs #111386

Closed
paulb-elastic opened this issue Sep 7, 2021 · 2 comments · Fixed by #107709
Closed
Assignees
Labels
Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services v7.16.0

Comments

@paulb-elastic
Copy link
Contributor

paulb-elastic commented Sep 7, 2021

This PR will add new “no data” screens across the various Observability apps, however this relies on each solution implementing a check that there is no data, which is that this issue is covering.

ACs:

@paulb-elastic paulb-elastic added Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services v7.16.0 labels Sep 7, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

@weltenwort
Copy link
Member

ℹ️ For the Logs UI indices this check already exists and the values is exposed as sourceStatus.logIndexStatus in the return value of the useLogSourceContext() hook:

isResolvingSourceConfiguration,
// Source status (denotes the state of the indices, e.g. missing)
sourceStatus,
loadSourceStatus,
// Source configuration (represents the raw attributes of the source configuration)

It can be one of missing, empty or available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services v7.16.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants