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

Subscriptions to Influx v1.11.7 do not seem to work properly #2837

Open
beheh opened this issue Oct 29, 2024 · 2 comments
Open

Subscriptions to Influx v1.11.7 do not seem to work properly #2837

beheh opened this issue Oct 29, 2024 · 2 comments

Comments

@beheh
Copy link

beheh commented Oct 29, 2024

We have a series of alerts setup in kapacitor, which we've been using fine for years. After upgrading to InfluxDB OSS v1.11.7, we've seen a few things broken in kapacitor (using Kapacitor OSS v1.7.5 on Debian):

  • deadman alerts started firing, because no data arrived
  • the kapacitor log was spammed with messages such as Oct 29 14:23:00 [redacted] kapacitord[11831]: ts=2024-10-29T14:23:00.613Z lvl=error msg="failed to parse points" service=influxdb cluster=localhost listener_id=udp:[redacted].default err="unable to parse '[redacted]': missing fields"

We use a setup with kapacitor subscribing via udp to instance on the same server. My suspicion is something isn't working properly anymore - this may be an Influx issue? Or is kapacitor using some kind of legacy way to subscribe to v1 instances that is no longer functional?
I did try switching to http subscriptions which fixes the log spam, but does not fix data being seen by kapacitor.

In the meantime we'll probably download to InfluxDB OSS v1.8.10 again.

@beheh
Copy link
Author

beheh commented Oct 29, 2024

Some more data: the subscriptions are seemingly added to Influx correctly, both by their presence after running SHOW SUBSCRIPTIONS and by the kapacitor log spam whenever an Influx message arrives. However it seems kapacitor just struggles to use them correctly.

@Global990
Copy link

Facing the same issue, any response please ?

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