Skip to content

Actions: ccfos/nightingale

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
97 workflow runs
97 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

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
[v8.4.0] alert number is not as expected when using variables Issue Translator #18: Issue #2971 opened by EnyaWong
6s
6s
Request support for automatic cleaning of historical alarms Issue Translator #17: Issue #2969 opened by a517363523
10s
10s
Support VictoriaLogs Issue Translator #16: Issue #2967 opened by skycyan
7s
7s
go_modules in /. for golang.org/x/crypto - Update #1159555996 Dependabot Updates #20: by dependabot bot
59s main
main
59s
Add a manual option to refresh the index on the log search page. Issue Translator #15: Issue #2965 opened by doublewaters
6s
6s
Request permissions for active alert management. Issue Translator #14: Issue #2963 opened by Throb-zjl
7s
7s
[v8.0.0-beta.10] There are occasional cases where alerts are triggered but notifications are not sent Issue Translator #13: Issue #2956 opened by yuanrui01
8s
8s
Pagination not working in metric view after adding new metrics in Template Center Issue Translator #12: Issue #2944 opened by doublewaters
7s
7s
Compatibility of Nightingale v8 with ES9 data sources Issue Translator #11: Issue #2940 opened by shkctl
8s
8s
When saving the basic information of a message template, the system also saves the template field content from the previous version on the frontend Issue Translator #10: Issue #2937 opened by zerosyn
8s
8s
There is an issue with the log context display when performing log searches. Issue Translator #9: Issue #2936 opened by Myifan610
7s
7s
The alert rule you added is not taking effect. Does Nightingale have a limit on the number of alert rules? Issue Translator #8: Issue #2935 opened by jianghuitheoutsider
5s
5s