influxdata / influxdata/kapacitor

Kapacitor alerts not displayed if tick is not human readable

Open
#2,426 3 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

@russorat

I have an alert that is saved in "not human readable":
![image](https://user-images.githubusercontent.com/72392361/97981189-31c0f900-1dd2-11eb-9a8a-42169f639cdc.png)

I make this alert to be raised:
![image](https://user-images.githubusercontent.com/72392361/97981331-6765e200-1dd2-11eb-8746-9150899559e1.png)

I also make another (human readable) alert to be raised:
![image](https://user-images.githubusercontent.com/72392361/97981489-ab58e700-1dd2-11eb-9feb-6c1d2640ff86.png)

Both alerts raised successfully but only one is shown in alert history:
![image](https://user-images.githubusercontent.com/72392361/97981763-130f3200-1dd3-11eb-9506-bfbe9aa269e6.png)

As we forward the kapacitor alerts to another tool we can see that the not human readable tick script is working fine:
![image](https://user-images.githubusercontent.com/72392361/97981983-64b7bc80-1dd3-11eb-94cb-02a990fe1e6e.png)

Thanks in advance

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the alert-history behavior with the human-readable and non-human-readable tick scripts described in the issue, then trace how Kapacitor records and displays each alert. Done means both successfully raised alerts appear in alert history while forwarding continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
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.