-
Notifications
You must be signed in to change notification settings - Fork 174
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] Using filebeat software to get logs is not real time #734
Comments
Can you share your filebeat config? |
this is filebeat config,
logs: OS:centos 7.9 give it a try and see how it goes |
I deleted data folder under filebeat dir before running this. Please try doing that.
|
The configuration does not change, delete all files under /var/lib/filebeat/, still the same delay, need to test a longer time, such as half an hour |
did you test it? It should be reproducible |
Is the log file /data/logs/backend/api.log getting updated continuously? Why do you suggest I should test this for half an hour? With one line of logdata you provided, I could see that line in siglens UI without any delay. I also tested this with another sample log file(siglens.log) and could see the logs in UI.
|
I also noticed that the GUI has a delay of approximatly 2 minutes for displaying ingested data. I don't know exactly where this delay is coming from. Could it be some kind of caching of the front end? I also noticed that the delay could be shorter - but typically I have also this 2 minutes offset. I'm using Vector.dev for log ingesting using the Elasticsearch API endpoint to ingest data. |
Using filebeat software to get logs is not real time, sometimes by more than 10 minutes
i install siglens with docker,docker install
log Ingesting use filebeat filebeat
logs are generated all the time, but rarely are they near real time in the browser (less than 2 minutes), most are 5 or 10 minutes ago
The text was updated successfully, but these errors were encountered: