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 log doesn't work with default setting #195

Open
joshuali925 opened this issue Sep 6, 2024 · 1 comment
Open

[BUG] VPC flow log doesn't work with default setting #195

joshuali925 opened this issue Sep 6, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@joshuali925
Copy link
Member

joshuali925 commented Sep 6, 2024

What is the bug?

  1. the default config when creating vpc flow logs stores logs in text, but integrations only supports parquet. there is no error messages on the UI, so it's hard to debug
  2. after specifying parquet, it is stored in this format: s3://bucket/AWSLogs/1111111111/vpcflowlogs/us-west-2/2024/09/05/xxx.log.parquet. but apparently the integrations query only supports hive format (e.g. year=2024/month=09/day=05). using the integration query directly leads to no results in the response
    1. this can be worked around using OPTIONS (recursiveFileLookup='true') at the end of the create table query, but this way there's no partition
  3. with recursiveFileLookup, the query returns this error
    {
        "data": {
            "ok": true,
            "resp": {
                "status": "FAILED",
                "error": "{\"Message\":\"Fail to run query. Cause: null\"}"
            }
        }
    }
    the actual error says Column: [protocol], Expected: bigint, Found: INT32. so protocol column in create table query should be changed to bigint instead of int

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

  1. create datasource s3 using vpc flow logs bucket
  2. go to dashboards saved objects and import ndjson from https://github.com/opensearch-project/opensearch-catalog/releases/tag/amazon_vpc_flow_1.1.0 with overwrite=true
  3. go to dashboards integrations, add vpc integration
  4. see these issues

What is the expected behavior?
A clear and concise description of what you expected to happen.

What is your host/environment?

  • OS: [e.g. iOS]
  • Version [e.g. 22] 2.13
  • Plugins

Do you have any screenshots?
If applicable, add screenshots to help explain your problem.

Do you have any additional context?
Add any other context about the problem.

@joshuali925 joshuali925 added bug Something isn't working untriaged labels Sep 6, 2024
@andrross
Copy link
Member

[Catch All Triage - 1, 2, 3]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants