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

Data could not be fetched in agent's FIM events #4104

Open
juliamagan opened this issue Apr 26, 2022 · 10 comments · Fixed by #4124
Open

Data could not be fetched in agent's FIM events #4104

juliamagan opened this issue Apr 26, 2022 · 10 comments · Fixed by #4124
Assignees
Labels
qa/report QA Team: Reporting possible bug type/bug Bug issue

Comments

@juliamagan
Copy link
Member

juliamagan commented Apr 26, 2022

Wazuh Elastic Rev Security
4.3 7.x 4301-1 Basic, ODFE, Xpack
Browser
Firefox

Description
When accessing an agent, if we click on the path of any FIM event, we cannot obtain information. In addition, the option to see the complete error does not work.

*Preconditions

  1. Demo environment

Steps to reproduce

  1. Navigate to Agents>Specific agent
  2. Click on FIM: Recent events>Path
  3. Click on See the full error

Expected Result

  1. Get more information
  2. If it fails, see the full error

Actual Result

  1. Data could not be fetched for /tmp/agent.conf
  2. See full error button does nothing

Screenshots

Uncaught TypeError: right-hand side of 'in' should be an object, got boolean
agent_fim.mp4
@gdiazlo
Copy link
Member

gdiazlo commented Apr 29, 2022

The API does not return data sometimes in the environment. The UI does not render the error adequately.

image

@gdiazlo gdiazlo moved this from Triage to To do in Release 4.3.0 Apr 29, 2022
@davidjiglesias
Copy link
Member

The failing paths do not appear to be included in the agent's inventory. We need to further investigate the error and check the database. It might be related with a problem in FIM core side.

@gdiazlo
Copy link
Member

gdiazlo commented Apr 29, 2022

The issue with the toast not showing an error string and the button of ¨Show the full error¨ not working might be related to #4030

@davidjiglesias
Copy link
Member

We need to confirm is this error appears in previous versions.

@Machi3mfl
Copy link
Member

Testing PR

  • The solution only fixes the error when click on error toast to see more details ("See full error")
    Could be tested using Sample Data FIM

@mauceballos
Copy link
Contributor

testing on kibana 7.10 OK

error-toast

@gdiazlo gdiazlo moved this from Triage to In review in Release 4.3.0 Apr 29, 2022
@matiasmoreno876 matiasmoreno876 linked a pull request Apr 29, 2022 that will close this issue
Repository owner moved this from In review to Done in Release 4.3.0 Apr 29, 2022
@davidjiglesias
Copy link
Member

I reopen this issue as the toast was fixed but some paths do not return any information when they should.

@j2vielchi
Copy link

Hello, greetings to the community.

I would like to know if this point could be solved. I currently have wazuh version 4.7.5, app revision: 02 and I have this problem:

Data could not be fetched for c:\users\user\directory\file.txt (example)

Full error:

Error: File not found at FlyoutDetail._callee$ (https://xxxxx/47402/bundles/plugin/wazuh/wazuh.chunk.10.js:1:6181020) at tryCatch (https://xxxxx/47402/bundles/plugin/customImportMapDashboards/customImportMapDashboards.plugin.js:13:786910) at Generator.invoke [as invoke] (https://xxxxx/47402/bundles/plugin/customImportMapDashboards/customImportMapDashboards.plugin.js:13:790926) at Generator.next (https://xxxxx/47402/bundles/plugin/customImportMapDashboards/customImportMapDashboards.plugin.js:13:788105) at flyout asyncGeneratorStep (https://xxxxx/47402/bundles/plugin/wazuh/wazuh.chunk.10.js:1:6175519) at _next (https://xxxxx/47402/bundles/plugin/wazuh/wazuh.chunk.10.js:1:6175836)

@j2vielchi
Copy link

Hello, I would like to know if the issue discussed was resolved??

@Tools-Security-Integrations

NO still issue appears and many users face this issue, i think all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
qa/report QA Team: Reporting possible bug type/bug Bug issue
Projects
No open projects
Status: Known issues
Development

Successfully merging a pull request may close this issue.

8 participants