IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-02-16 18:34:52 -06:00
Code Issues Packages Projects Releases Wiki Activity
d8d97d15ba
grafana/pkg/services/ngalert/CHANGELOG.md

106 lines
6.2 KiB
Markdown
Raw Normal View History

Alerting: Introduce an internal changelog (#47390) * Alerting: Introduce an internal changelog Please note that this is not intented to replace Grafana's "add to changelog" label. It is _mostly_ for internal consumption of the Alerting team that owns this part of Grafana. * Fix markdown formatting * Fix changelog entry
2022-04-07 09:24:26 -05:00
# 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
Alerting: Rule api to fail update if provisioned rules are affected (#50835) * add function that checks whether changes mention provisioned rules * update API that updates group of rules to fail if check does not pass
2022-06-15 15:01:14 -05:00
- [CHANGE] Rule API to reject request to update rules that affects provisioned rules #50835
Alerting: Add first Grafana reserved label grafana_folder (#50262) * Alerting: Add first Grafana reserved label g_label g_label holds the title of the folder container the alert. The intention of this label is to use it as part of the new default notification policy groupBy. * Add nil check on updateRule labels map * Disable gocyclo lint on schedule.ruleRoutine will remove later in a separate refactoring PR to reduce complexity. * Address doc suggestions * Update g_folder for rules in folder when folder title changes * Remove global bus in FolderService * Modify tests to fit new common g_folder label * Add changelog entry * Fix merge conflicts * Switch GrafanaReservedLabelPrefix from `g_` to `grafana_`
2022-06-17 12:10:49 -05:00
- [FEATURE] Add first Grafana reserved label, grafana_folder is created during runtime and stores an alert's folder/namespace title #50262
Alerting: Support for optimistic locking for alert rules (#50274) * add support for optimistic locking for alert_rule table * return 409 in the case of opitimistic lock
2022-06-13 11:15:28 -05:00
- [FEATURE] use optimistic lock by version field when updating alert rules #50274
Alerting: State manager to use tick time to determine stale states (#50991) * use correct stale timestamp * calculate stale using tick time instead of time.now * remove unused dependency on sql store
2022-06-21 17:16:53 -05:00
- [BUGFIX] State manager to use tick time to determine stale states #50991
Alerting: Scheduler to drop ticks if a rule's evaluation is too slow (#48885) * drop ticks if evaluation of a rule is too slow. * add metric schedule_rule_evaluations_missed_total
2022-06-08 11:50:44 -05:00
- [ENHANCEMENT] Scheduler: Drop ticks if rule evaluation is too slow and adds a metric grafana_alerting_schedule_rule_evaluations_missed_total to track missed evaluations per rule #48885
Alerting: Make ticker to tick at predictable time (#50197)
2022-06-10 09:27:17 -05:00
- [ENHANCEMENT] Ticker to tick at predictable time #50197
Alerting: Don't stop the migration when alert rule tags are invalid (#51253) * Alerting: Don't stop the migration when alert rule tags are invalid As we migrate we expect the `alertRuleTags` on a dashboard alert to be a JSON object. However, it seems this is not really validated by Grafana and an user can change the format to something else that the JSON parser is not able to marshal into a `map[string]string`. Let's do a bit better by "attempting" to parse the tags and if we can't we'll simple return an empty map. The data is still there so if the user wishes they can go back, fix the data and attemp the migration again.
2022-06-22 11:39:17 -05:00
- [ENHANCEMENT] Migration: Don't stop the migration when failing to parse alert rule tags #51253
Alerting: Prevent evaluation if "for" shorter than "evaluate" (#51797) Co-authored-by: Armand Grillet <armand.grillet@outlook.com>
2022-07-19 03:30:26 -05:00
- [ENHANCEMENT] Prevent evaluation if "for" shorter than "evaluate" #51797
Alerting: Scheduler to drop ticks if a rule's evaluation is too slow (#48885) * drop ticks if evaluation of a rule is too slow. * add metric schedule_rule_evaluations_missed_total
2022-06-08 11:50:44 -05:00
Alerting: Logs should not be capitalized and the errors key should be "err" (#50333) * Alerting: decapitalize log lines and use "err" as the key for errors Found using (logger|log).(Warn|Debug|Info|Error)\([A-Z] and (logger|log).(Warn|Debug|Info|Error)\(.+"error"
2022-06-07 12:54:23 -05:00
## 9.0.0
Alerting Changelog: Cut & Fix (#48402)
2022-04-28 05:20:35 -05:00
- [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`
Alerting: Create folder for alerting when start from the scratch (#48866) * create folderHelper struct
2022-05-13 10:49:04 -05:00
- [ENHANCEMENT] Create folder 'General Alerting' when Grafana starts from the scratch #48866
Alerting: Use UID scope for folders authorization (#48970)
2022-05-13 11:05:25 -05:00
- [ENHANCEMENT] Rule changes authorization logic to use UID folder scope instead of ID scope #48970
Alerting: Update alert rule diff to not see difference between nil and empty map (#50192)
2022-06-03 14:27:29 -05:00
- [ENHANCEMENT] Scheduler: ticker to support stopping #48142
Optional custom title and description for OpsGenie (#50131) * optional custom description for OpsGenie * custom title and message, tests * update changelog * check for empty / whitespace only strings * truncate the title to 130 characters if needed * unnecessary validation removed * truncate title to 127 characters and add three dots
2022-06-08 15:55:31 -05:00
- [ENHANCEMENT] Optional custom title and description for OpsGenie #50131
Alerting: Schedule Alert rules metric tracking (#50415) * Alerting: Schedule Alert rules metric tracking Change the record of metrics from one place to two as an attempt to have a semi-accurate record.
2022-06-08 12:37:33 -05:00
- [ENHANCEMENT] Scheduler: Adds new metrics to track rules that might be scheduled #49874
- `grafana_alerting_schedule_alert_rules `
- `grafana_alerting_schedule_alert_rules_hash `
- [CHANGE] Scheduler: Renaming of metrics to make them consistent with similar metrics exposed by the component #49874
- `grafana_alerting_get_alert_rules_duration_seconds` to `grafana_alerting_schedule_periodic_duration_seconds`
- `grafana_alerting_schedule_periodic_duration_seconds` to `grafana_alerting_schedule_query_alert_rules_duration_seconds`
Alerting: indicate whether contact point is provisioned (#48323)
2022-04-27 13:53:36 -05:00
- [FEATURE] Indicate whether routes are provisioned when GETting Alertmanager configuration #47857
- [FEATURE] Indicate whether contact point is provisioned when GETting Alertmanager configuration #48323
Alerting: indicate whether an alertrule is provisioned (#48458)
2022-04-28 14:27:34 -05:00
- [FEATURE] Indicate whether alert rule is provisioned when GETting the rule #48458
Alerting: Remove double quotes from matchers (#50038) * Alerting: Remove double quotes from matchers With #38629 a new Alertmanager configuration object was introduced with `object_matchers`, it was meant to circumvent around the fact that Prometheus label names don't support a set of characters that Grafana needs to support for alerts, silences, matchers, etc. (with a common example being elasticsearch's `.`). This new object does not include the label of sanitzation or validation that its Prometheus equivalent supports in `matchers` and therefore are semantically not equivalent. This triggered the problem that when the migration is run, we use `matchers` as the object to populate in configuration for routing policies, but when the UI does its first save this object is transformed to `object_matchers`. Matchers that were previously running just fine would immediately stop working as soon as the configuration is saved. This problem surfaced with the introduction of #49952 where we stopped stripping double quotes from matchers (not just regex but _all_ of them). * Add comment explaining rationale and future removal Co-authored-by: Alex Weaver <weaver.alex.d@gmail.com>
2022-06-01 16:05:24 -05:00
- [FEATURE] Alert rules with associated panels will take screenshots. #49293 #49338 #49374 #49377 #49378 #49379 #49381 #49385 #49439 #49445
Alerting: Persist rule position in the group (#50051) Migrations: * add a new column alert_group_idx to alert_rule table * add a new column alert_group_idx to alert_rule_version table * re-index existing rules during migration API: * set group index on update. Use the natural order of items in the array as group index * sort rules in the group on GET * update the version of all rules of all affected groups. This will make optimistic lock work in the case of multiple concurrent request touching the same groups. UI: * update UI to keep the order of alerts in a group
2022-06-22 09:52:46 -05:00
- [FEATURE] Persistent order of alert rules in a group #50051
Alerting: Update migration to migrate only alerts that belong to existing org\dashboard (#49192) * Update migration to migrate only alerts that belong to existing org\dashboard
2022-05-18 15:00:08 -05:00
- [BUGFIX] Migration: ignore alerts that do not belong to any existing organization\dashboard #49192
Alerting: Logs should not be capitalized and the errors key should be "err" (#50333) * Alerting: decapitalize log lines and use "err" as the key for errors Found using (logger|log).(Warn|Debug|Info|Error)\([A-Z] and (logger|log).(Warn|Debug|Info|Error)\(.+"error"
2022-06-07 12:54:23 -05:00
- [BUGFIX] Allow anonymous access to alerts #49203
Alerting: Fix RBAC actions for notification policies (#49185) * squash actions "alert.notifications:update", "alert.notifications:create", "alert.notifications:delete" to "alert.notifications:write" * add migration * update UI to use the write action * update docs * changelog
2022-05-20 09:55:07 -05:00
- [BUGFIX] RBAC: replace create\update\delete actions for notification policies by alert.notifications:write #49185
Alerting: Fix access to alerts for viewer with editor permissions when RBAC is disabled (#49270) * Add folder edit permission for users with Viewer role * relax permissions required to create an alert when RBAC is disabled
2022-05-23 08:58:20 -05:00
- [BUGFIX] Fix access to alerts for Viewer role with editor permissions in folder #49270
Alerting: Logs should not be capitalized and the errors key should be "err" (#50333) * Alerting: decapitalize log lines and use "err" as the key for errors Found using (logger|log).(Warn|Debug|Info|Error)\([A-Z] and (logger|log).(Warn|Debug|Info|Error)\(.+"error"
2022-06-07 12:54:23 -05:00
- [BUGFIX] Alerting: Remove double quotes from double quoted matchers #50038
Alerting: Update alert rule diff to not see difference between nil and empty map (#50192)
2022-06-03 14:27:29 -05:00
- [BUGFIX] Alerting: rules API to not detect difference between nil and empty map (Annotations, Labels) #50192
Alerting Changelog: Cut & Fix (#48402)
2022-04-28 05:20:35 -05:00
Alerting: Fix & Cut the changelog (#48714)
2022-05-04 10:05:48 -05:00
## 8.5.3
- [BUGFIX] Migration: Remove data source disabled property when migrating alerts #48559
## 8.5.2
- [FEATURE] Migration: Adds `force_migration` as a flag to prevent truncating the unified alerting tables as we migrate. #48526
- [BUGFIX] Use `NaN` and do not panic when captured alert values are empty #48370
Alerting Changelog: Cut & Fix (#48402)
2022-04-28 05:20:35 -05:00
## 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
Alerting: Wrap legacy alerting metrics with `legacy_` (#48190) * Alerting: Wrap legacy alerting metrics with `legacy_`
2022-04-25 10:19:36 -05:00
- [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
Reference in New Issue Copy Permalink