influxdata / influxdata/kapacitor

Last Value in Stream, waiting to be pushed

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

Description

@nathanielc had explained Kapacitor stream behavior as -

**That last value is not skipped its just still sitting in the window waiting to be pushed out by then next point behind it.** from https://github.com/influxdata/kapacitor/issues/221

you have mentioned, implementing flush is feasible for valid use case.

1/ **logparser** : using logparser to push only ERROR messages in Influx, tick job expected to raise an alert on each measurement on STREAM as "logparser" inserting only ERROR lines.

since, each line in log file is not an ERROR message i.e. data is not being inserted every seconds or 10S window,
TICK script is raising alert on previous LAST Message only when next point arrives. This is delaying alerting on LAST message sitting on Window.

Please suggest how can we achieve this ? Is there any other way alerts can be trigger

Contributor guide

Open the contributing guide

Research direction

The issue names Kapacitor stream windows, logparser, Influx, and a TICK alert but no source file, test, or entry point. Start by tracing the stream-window behavior for ERROR-only input; done would be a clear decision or implementation for flushing the final value and triggering an alert without a subsequent point.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability-sre, stream-processing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.