-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Telegraf not writing data continously, needs to be restarted to write kafka data. #9856
Comments
Can you please upload your logs as this will give us a better idea of what is going on? |
Can you provide the full logs, please? When it comes to helping with sending metrics it is good to see what is going on between writes of batches. Also do you have any agent configuration options set? Thanks! |
Yeah i have agent configuration set.
Logs
|
Is there a reason why you set the buffer batch limit and size to 200000? The limit configuration variable determines the maximum number of unwritten metrics. The larger it is, the larger the period of output silence will occur, which is exactly what you are seeing. This really is a support request and not a bug in Telegraf. I suggest you drop your agent parameters and try again as you should then see metrics being sent much faster. |
I would also suggest following up on our Community Slack or Community Page. Thank you! |
The reason for opting buffer batch limit to 200000, was to avoid metrics getting dropped. Can you share some info on how i can calculate the metrics coming and what should be ideal batch size and batch limit. Getting confused on that part. Thanks |
Relevant telegraf.conf:
System info:
Docker Telegraf version - 1.18.0; Os- ec2 instance (type - t2.large)
Steps to reproduce:
Expected behavior:
Telegraf not writing data continuously with above configuration.
Actual behavior:
Telegraf should be writing data continously.
Additional info:
The kafka logs are coming every 5 mins. I also tried with offset oldest but since data comes in bulk, most of metrics get dropped, hence opted for offset newest. Also please explain how this offset with value "newest" and "oldest" behave, does offset gets auto committed after some time.
The text was updated successfully, but these errors were encountered: