influxdata / influxdata/kapacitor

Feature Request - Require the field name being used in tickscripts

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

Description

Scenario - Need a solution to dynamically get the field name, apart from the measurement name, in tickscripts.

Example - I'm setting up for number of cpus. The measurement name is system, but the field name is n_cpus. When I send an email, in case of the value crossing a threshold, and I cannot send n_cpus in the mail without hardcoding the name into the tickscript.

Problem - Sending an email saying System is alerting isn't very intuitive and doesn't point to the actual issue.

Request - Add a solution to get the field name, in addition to the field value, which we already get.

Contributor guide

Open the contributing guide

Research direction

Start by tracing how Kapacitor exposes field values to TICKscripts and how alert emails receive those values. Define how the originating field name should be made available alongside the value, then verify that an email can identify the triggering field without hardcoding n_cpus.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.