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

Delay of raw ingest to influxDB #57

Closed
DrStS opened this issue Mar 27, 2024 · 6 comments · Fixed by #58
Closed

Delay of raw ingest to influxDB #57

DrStS opened this issue Mar 27, 2024 · 6 comments · Fixed by #58

Comments

@DrStS
Copy link

DrStS commented Mar 27, 2024

How can I configure the delay until a value is written to influxDB. For example, when I receive a temp. which upates every 2s in the signalK dataExplorer there seems to be a pretty long delay (~30sec) until these values are written to influxdb. Moreover, the delay seems to have a random behaviour.

I use the most recent version of singalK and the plugin.

Thanks a lot for your help.

Best

@tkurki
Copy link
Owner

tkurki commented Mar 27, 2024

Influxdb client writes the buffer to db every 60 seconds or max number of points. The params are the in the plugin config, batch something. On my phone so can’t provide the exact param name.

@DrStS
Copy link
Author

DrStS commented Mar 28, 2024

Thanks a lot for the info:
Screenshot 2024-03-28 085143
I have played with these settings. Yet it seems there is no change. I would like that the data is updated every 5 sec. Thanks a lot! Best Stefan

@tkurki
Copy link
Owner

tkurki commented Mar 28, 2024

Lol, looks like these are not passed to influx client! I’ll get back to you.

@DrStS
Copy link
Author

DrStS commented Mar 28, 2024

Thanks!

@tkurki
Copy link
Owner

tkurki commented Mar 28, 2024

Should be fixed in 1.7.2.

@DrStS
Copy link
Author

DrStS commented Mar 29, 2024

Thanks! I can confrim. It works now!

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

Successfully merging a pull request may close this issue.

2 participants