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

discuss: did we really care about the report elapsed? #12

Open
woodgear opened this issue Aug 13, 2022 · 2 comments
Open

discuss: did we really care about the report elapsed? #12

woodgear opened this issue Aug 13, 2022 · 2 comments

Comments

@woodgear
Copy link

if d > time.Duration(o.config.PushInterval.Duration) {

as long as influxdb store our data without eror, i thought it does not matter how long it takes.

@woodgear
Copy link
Author

maybe we could just delete this warning?. i am happy to fire a pr to remove this. what do you think?

@javaducky
Copy link
Contributor

javaducky commented Aug 15, 2022

Are you seeing this entry in your logs a lot? Is this something you should just increase the K6_INFLUXDB_PUSH_INTERVAL when running your scripts? This may be a helpful issue if your network encounters unexpected latency and/or you are attempting to push too frequently. 🤷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants