nightingale · Issues· 251 open

Changing the business group of an alert rule does not take effect despite save success

[Bug] MySQL datasource is not connectivity-checked on add/save; invalid configs save successfully

elasticsearch 8.6.2，Encountered an EOF error while configuring alert rules.

Migrate Apache IoTDB table-model SQL query execution from REST API to iotdb-client-go

After configuring the relevant policies and rules, the tasks and alerts are still not being triggered. Could you please help me investigate why?

[BUG] method renderField in message_tpl.go will cause the alert info to generate line break error on third-party platform

CVE-2026-58167: `/api/n9e/datasource/list` still discloses URL-embedded credentials

Add to the official website homepage image IoTDB

[Feature] Add separate controls for Target tags and heartbeat host_tags

Prometheus-Categraf Integration: ident Label Rewrite Configuration

The dashboard cannot be queried victorialogs

VictoriaLogs log querying does not have a feature for viewing surrounding documents.

Label issue with notification rules

It is hoped that alert notification templates will support distinguishing between the current/recovery value and the value at the time of triggering.

Regarding appending API request paths /chat/completions