influxdata / influxdata/kapacitor

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

Open
#2,837 2 comments 1 reaction 0 assignees View on GitHub
Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

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](https://github.com/influxdata/docs-v2/pull/5648), 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 downgrade to InfluxDB OSS v1.8.10 again.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with InfluxDB OSS v1.11.7 and Kapacitor OSS v1.7.5 on Debian, using the UDP and HTTP subscription paths described. Compare whether data reaches Kapacitor and whether the `failed to parse points` errors and deadman alerts persist; done means subscriptions deliver data without those failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, go
Domain
observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.