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

Elastic search showing VM ray indicators/observables entities as unknown type #3536

Open
rogeliodc12 opened this issue Mar 2, 2025 · 1 comment
Labels
bug use for describing something not working as expected needs more info Intel needed about the use case

Comments

@rogeliodc12
Copy link

Description

Elastic Search showing observables from VMray as unknown instead of domains, ips, etc. Attached is the JSON information from Elastic and VMray. We are trying to see if we may need to add parameters and or change

Environment

On prem octi Version 6.5

Reproducible Steps

Ingest data through elastic search and view thing information coming in as uknown and see it load in the console the same occurs. Information can bee seen in observables that come back with uknown type of entity causing this to be a problem when attempting to analyze data and create accurate information.

Expected Output

Entity types created correctly

Actual Output

Incorrect entity type information

Additional information

Connector information can be sent over upon request.

@rogeliodc12 rogeliodc12 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 2, 2025
@romain-filigran
Copy link
Member

@rogeliodc12 : Hello, I'm not sure I understand the problem you're raising. Which connector are you using? Can you provide some screenshots illustrating the problems you describe?

@romain-filigran romain-filigran added needs more info Intel needed about the use case and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected needs more info Intel needed about the use case
Projects
None yet
Development

No branches or pull requests

2 participants