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

Filebeat audit resource name visualization uses an invalid field #24899

Closed
pmusa opened this issue Apr 1, 2021 · 2 comments · Fixed by #25038
Closed

Filebeat audit resource name visualization uses an invalid field #24899

pmusa opened this issue Apr 1, 2021 · 2 comments · Fixed by #25038
Assignees
Labels
bug Team:Integrations Label for the Integrations team

Comments

@pmusa
Copy link

pmusa commented Apr 1, 2021

Version: 7.12.0 (it was also in 7.10.1, did not test any other versions)

Steps to Reproduce

  • install and setup filebeat
  • navigate to Dashboard -> [Filebeat GCP] Audit
  • One of the visualizations will show an error:

Could not locate that index-pattern-field (id: gcp.audit.resource_name)

Screenshot 2021-04-01 at 15 14 51

Steps to quickly fix it

  • Inspect the visualization saved object (Audit Resource Name [Filebeat GCP])
  • Update the visState to use googlecloud.audit.resource_name instead of gcp.audit.resource_name

I think the issue is related to the rename that happened here

@pmusa pmusa added the bug label Apr 1, 2021
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 1, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Team:Integrations Label for the Integrations team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants