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

[BUG] VPC Flow Integration shows many errors when trying sample data #792

Closed
Swiddis opened this issue Aug 1, 2023 · 3 comments · Fixed by #809
Closed

[BUG] VPC Flow Integration shows many errors when trying sample data #792

Swiddis opened this issue Aug 1, 2023 · 3 comments · Fixed by #809
Assignees
Labels
bug Something isn't working integrations Used to denote items related to the Integrations project untriaged

Comments

@Swiddis
Copy link
Collaborator

Swiddis commented Aug 1, 2023

What is the bug?
The current VPC Flow integration isn't configured correctly, when trying the sample data it reports a lot of errors.

How can one reproduce the bug?
Steps to reproduce the behavior:

  1. Start a clean instance with OSD, or clear the existing instance:
DELETE ss4o_*
DELETE _data_stream/ss4o_*
DELETE _index_template/*
DELETE _component_template/*
  1. Access the VPC integration
  2. Click "Try it"
  3. Access the dashboard
  4. See lots of errors

What is the expected behavior?
The panels of the VPC integration should not show errors. They may show "no data" if and only if the sample data does not actually supply any data matching the panel.

What is your host/environment?

Do you have any screenshots?
image

Do you have any additional context?
N/A

@Swiddis Swiddis added bug Something isn't working untriaged integrations Used to denote items related to the Integrations project labels Aug 1, 2023
@derek-ho
Copy link
Collaborator

derek-ho commented Aug 2, 2023

Checking

@derek-ho
Copy link
Collaborator

derek-ho commented Aug 2, 2023

Able to reproduce - @wanghd89 we may need to take another look at your contribution, but I remember it was working, maybe some schema changed or something after the change went in

@Swiddis Swiddis self-assigned this Aug 2, 2023
@Swiddis
Copy link
Collaborator Author

Swiddis commented Aug 2, 2023

git bisect says first faulty commit is be9b2d4, from #740

Update: Found fix, making PR now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working integrations Used to denote items related to the Integrations project untriaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants