Skip to content

Actions: ccfos/nightingale

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
107 workflow runs
107 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Support VictoriaTrace Issue Translator #39: Issue #3030 opened by zhushiyang
6s
6s
Subscription alert matching error: Missing parameter "json" Issue Translator #38: Issue #3026 opened by liuxin638507
7s
7s
n9e v8.5.0 disk_used_percent value is abnormal Issue Translator #37: Issue #3025 opened by lyitt1987
6s
6s
Subscription blocking rules are not effective Issue Translator #36: Issue #3023 opened by liuxin638507
6s
6s
read: connection reset by peer Issue Translator #35: Issue #3022 opened by yanming-zhang
5s
5s
Add context view to ElasticSearch log search results Issue Translator #34: Issue #3021 opened by flyhai
7s
7s
In the notification message for alert using SQL queries, how to use non-tag alias columns Issue Translator #33: Issue #3018 opened by a43412340-bit
6s
6s
Does Nightingale support directly configuring the data source as MySQL or PostgreSQL and querying SQL for alert? Issue Translator #32: Issue #3016 opened by licaishui88
8s
8s
Through the cloned built-in email medium, notify the test error Issue Translator #31: Issue #3005 opened by maolinglinux
7s
7s
Calling the API keeps prompting unauthorized. I have followed the documentation, but it still doesn't work Issue Translator #30: Issue #3004 opened by MengProject-923
7s
7s
fix: vlogs query Release #1692: Commit 9bee3e1 pushed by 710leo
4m 49s v8.5.0
v8.5.0
4m 49s
fix: vlogs query Release #1691: Commit 9bee3e1 pushed by 710leo
4m 51s v8.5.0
v8.5.0
4m 51s
refactor: trim prom param Release #1690: Commit c214580 pushed by 710leo
4m 53s v8.5.0
v8.5.0
4m 53s
The alarm rule enables level suppression and recovery notification; recovery notifications will be sent multiple times. Issue Translator #29: Issue #3000 opened by a517363523
8s
8s
When the alarm rule is configured such that PromForDuration=0 (duration is 0) and RecoverDuration>0 (observation duration is greater than 0), even if the alarm condition is no longer met, the alarm cannot be automatically recovered, resulting in the alarm remaining active all the time Issue Translator #28: Issue #2999 opened by xzhaoxz
9s
9s
go_modules in /. for github.com/expr-lang/expr - Update #1184525159 Dependabot Updates #21: by dependabot bot
59s main
main
59s
Issues regarding the duration of historical monitoring data that can be queried. Issue Translator #27: Issue #2997 opened by young-2023
7s
7s
The version of Nightingale 8.4.1, when using ES8.18.4 as the data source, an error will be reported when configuring an alert Issue Translator #26: Issue #2992 opened by ReggieYao
8s
8s
Configured the S1 alarm, and also enabled the threshold judgment, why no S1 alarm is generated Issue Translator #25: Issue #2991 opened by xtzeng
8s
8s
In the workflow eventDrop, $value is a string and cannot be compared Issue Translator #24: Issue #2987 opened by blessmylovexy
10s
10s
How to use group by on a field in Elasticsearch alert Issue Translator #23: Issue #2984 opened by Puhan-Zhou
8s
8s
Some issues in the template center Issue Translator #22: Issue #2977 opened by doublewaters
9s
9s
Feature request: metric alerting - advanced mode Issue Translator #21: Issue #2974 opened by Direktor799
7s
7s
When using ClickHouse as the data source and configuring the alarm rules, the error "Error executing query: err:cluster not exists" will occur Issue Translator #20: Issue #2973 opened by chenjf5534
6s
6s
Edge configuration ES alarm query error Issue Translator #19: Issue #2972 opened by lcy0828
8s
8s