-
Notifications
You must be signed in to change notification settings - Fork 186
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
Comments
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. |
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 |
We need to confirm is this error appears in previous versions. |
Testing PR
|
I reopen this issue as the toast was fixed but some paths do not return any information when they should. |
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) |
Hello, I would like to know if the issue discussed was resolved?? |
NO still issue appears and many users face this issue, i think all |
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
Steps to reproduce
Expected Result
Actual Result
/tmp/agent.conf
Screenshots
agent_fim.mp4
The text was updated successfully, but these errors were encountered: