Filebeat data not visible under Discover tab
Kibana Build details:
VERSION: 9.2.0 BC2
BUILD: 91433
COMMIT: 7d37e7bee2457c29e10fde5531500b29bcdcc9d5
Artifact Link: https://staging.elastic.co/9.2.0-0276828a/downloads/beats/filebeat/filebeat-9.2.0-windows-x86_64.zip
Preconditions:
- 9.2.0 BC2 Kibana cloud environment should be available.
Steps to reproduce:
- Update cloud id and cloud auth for Filebeat under filebeat.yml.
- Now, enable system module using this command
filebeat modules enable threatintel. - Navigate to 'modules.d/threatintel.yml' and set all
falsevalue totrue. - Save the file.
- Now run:
filebeat setup -efor setup assests. - Observe Dashboards are successfully loaded.
- Then start filebeat using this command
sudo service filebeat start - Navigate to kibana > Discover Tab > Filebeat
- Observe no data under Discover tab is displayed for Agents.
Expected Result: Filebeat logs should be installed successfully and visible under the Discover tab.
Actual Result
No data is displayed in Discover for Filebeat index even after successful setup and service start.
Logs
Filebeat configuration file of modules directory
Screenshot
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)
@amolnater-qasource Kindly review
Secondary review for this ticket is Done. FYI @pierrehilbert
Hey, Could it be similar to https://github.com/elastic/beats/issues/45516?
Hi @pierrehilbert
Thanks for looking into this issue.
Could it be similar to https://github.com/elastic/beats/issues/45516?
We have attempted to reproduce the above issue. However, in their case, running the command .\filebeat.exe setup -e displays an error in the command prompt logs. In our case, we executed the command .\filebeat.exe setup (without the -e flag), which ran successfully. After that, the dashboard loaded correctly, and we started the service using Start-Service filebeat.
Despite the successful setup, dashboard load, and service start, we observed that no data is displayed in Discover for Filebeat.
Screenshot
Please let us know if anything else is required from our end. Thanks
Am I understanding this correctly? the application issues a warning, and the script chose "Do not run" as the follow on option - correct?
Hi @nimarezainia
the application issues a warning, and the script chose "Do not run" as the follow on option - correct?
All the steps for installation as shared under https://github.com/elastic/beats/issues/46958#issue-3490800428 are executed successfully without any errors. However, No data is visible under the Discover Tab.
Please let us know if we are missing anything here. Thanks