IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2024-12-02 05:29:42 -06:00
Code Issues Packages Projects Releases Wiki Activity
d4616cfe26
grafana/pkg/services/ngalert/CHANGELOG.md
gotjosh d451d02628
Alerting Changelog: Cut & Fix (#48402)
2022-04-28 11:20:35 +01:00

3.5 KiB
Raw Blame History

Changelog

Please note that this is not a direct replacement of Grafana's "add to changelog" label. It is mostly for internal consumption of the Alerting team that owns this part of Grafana.

Scope Glossary

[ADMIN]

The ADMIN scope denotes a change that affect the structure and layout of this repository. This includes updates to the following:

  • CODEOWNERS
  • README
  • DotFiles (.gitignore, .git-attributes, etc)

Anything that a developer working on this repo should be aware of from a standards and practice perspective.

[BUGFIX]

The BUGFIX scope denotes a change that fixes an issue with the project in question. A BUGFIX should align the behaviour of the service with the current expected behaviour of the service. If a BUGFIX introduces new unexpected behaviour to ameliorate the issue, a corresponding FEATURE or ENHANCEMENT scope should also be added to the changelog.

[CHANGE]

The CHANGE scope denotes a change that changes the expected behavior of the project while not adding new functionality or fixing an underling issue. This commonly occurs when renaming things to make them more consistent or to accommodate updated versions of vendored dependencies.

[FEATURE]

The FEATURE scope denotes a change that adds new functionality to the project/service.

[ENHANCEMENT]

The ENHANCEMENT scope denotes a change that improves upon the current functionality of the project/service. Generally, an enhancement is something that improves upon something that is already present. Either by making it simpler, more powerful, or more performant. For Example:

An optimization on a particular process in a service that makes it more performant Simpler syntax for setting a configuration value, like allowing 1m instead of 60 for a duration setting.

Order

Scopes must have an order to ensure consistency and ease of search, this helps us identify which section do we need to look for what. The order must be:

  1. [CHANGE]
  2. [FEATURE]
  3. [BUGFIX]
  4. [ENHANCEMENT]
  5. [ADMIN]

Grafana Alerting - main / unreleased

  • [BUGFIX] Use NaN and do not panic when captured alert values are empty #48370
  • [ENHANCEMENT] Scheduler: Ticker expose new metrics. In legacy, metrics are prefixed with legacy_ #47828, #48190
    • grafana_alerting_ticker_last_consumed_tick_timestamp_seconds
    • grafana_alerting_ticker_next_tick_timestamp_seconds
    • grafana_alerting_ticker_interval_seconds
  • [FEATURE] Indicate whether routes are provisioned when GETting Alertmanager configuration #47857
  • [FEATURE] Indicate whether contact point is provisioned when GETting Alertmanager configuration #48323

8.5.1

  • [BUGFIX] Silences: Invalid silences created through the API made grafana panic, they are now validated. #46892
  • [ENHANCEMENT] Migration: Migrate each legacy notification channel to its own contact point, use nested routes to reproduce multi-channel alerts #47291

8.5.0

  • [CHANGE] Prometheus Compatible API: Use float-like values for api/prometheus/grafana/api/v1/alerts and api/prometheus/grafana/api/v1/rules instead of the evaluation string #47216
  • [CHANGE] Notification URL points to alert view page instead of alert edit page. #47752
  • [BUGFIX] (Legacy) Templates: Parse notification templates using all the matches of the alert rule when going from Alerting to OK in legacy alerting #47355
  • [BUGFIX] Scheduler: Fix state manager to support OK option of AlertRule.ExecErrState #47670
  • [ENHANCEMENT] Templates: Enable the use of classic condition values in templates #46971