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.

Sign up for GitHub

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

Jump to bottom

[Logs UI] Using cross cluster index not showing log data #70048

Closed
pnowak85 opened this issue Jun 26, 2020 · 2 comments · Fixed by #70179
Closed

[Logs UI] Using cross cluster index not showing log data #70048

pnowak85 opened this issue Jun 26, 2020 · 2 comments · Fixed by #70179
Assignees
@weltenwort
Labels
bug Fixes for quality problems that affect the customer experience Feature:Logs UI Logs UI feature Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
Milestone
Logs UI 7.9

Comments

@pnowak85
Copy link

Kibana version: 7.8.0

Elasticsearch version: 7.8.0

Browser version: Chrome 83.0

Browser OS version: Windows 10

Original install method (e.g. download page, yum, from source, etc.): official docker image

Describe the bug:
Logs UI does not show data from a cross cluster index, instead it shows: Looks like you don't have any logging indices. Let's add some!
Logs are definitely available, as Discover shows them.

Steps to reproduce:

  1. Store logs via logstash (7.8.0 - new index) in a remote cluster (remote cluster still version 7.7.1)
  2. Configure the remote cluster access in kibana (name e.g. metrics)
  3. Check Discover for log entries from the remote cluster
  4. Update Logs UI settings to access the remote cluster index e.g.: metrics:logstash-*
  5. Open Logs UI - see Looks like you don't have any logging indices. Let's add some!

Expected behavior:
Show log data from the cross cluster index

Additional info
Did work in Kibana 7.7.1 / ES 7.7.1
@weltenwort weltenwort added bug Fixes for quality problems that affect the customer experience Feature:Logs UI Logs UI feature Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services labels Jun 26, 2020
@elasticmachine
Copy link
Contributor

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

@weltenwort weltenwort added this to the Logs UI 7.9 milestone Jun 26, 2020
@weltenwort weltenwort self-assigned this Jun 26, 2020
@weltenwort
Copy link
Member

I have located the change that has probably introduced this in 7.8 and will create a fix shortly.

@weltenwort weltenwort mentioned this issue Jun 29, 2020
Merged
weltenwort added a commit that referenced this issue Jul 1, 2020
@weltenwort
[Logs UI] Avoid CCS-incompatible index name resolution (#70179)
e70bc81 
This fixes #70048 by avoiding a CCS-incompatible ES API call when determining the existence of log indices.
weltenwort added a commit to weltenwort/kibana that referenced this issue Jul 1, 2020
@weltenwort
[Logs UI] Avoid CCS-incompatible index name resolution (elastic#70179)
9acbda7 
This fixes elastic#70048 by avoiding a CCS-incompatible ES API call when determining the existence of log indices.
# Conflicts:
#	x-pack/plugins/infra/public/containers/logs/log_source/log_source.ts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@weltenwort weltenwort

Labels
bug Fixes for quality problems that affect the customer experience Feature:Logs UI Logs UI feature Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
Projects
None yet
Milestone
Logs UI 7.9
Development

Successfully merging a pull request may close this issue.

[Logs UI] Avoid CCS-incompatible index name resolution weltenwort/kibana
3 participants
@weltenwort @pnowak85 @elasticmachine