@prometheus-io/lezer-promql 0.53.0-rc.1 → 0.53.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +9 -8
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,20 +2,21 @@
|
|
|
2
2
|
|
|
3
3
|
## unreleased
|
|
4
4
|
|
|
5
|
-
## 2.53.
|
|
5
|
+
## 2.53.1 / 2024-07-10
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Fix a bug which would drop samples in remote-write if the sending flow stalled
|
|
8
|
+
for longer than it takes to write one "WAL segment". How long this takes depends on the size
|
|
9
|
+
of your Prometheus; as a rough guide with 10 million series it is about 2-3 minutes.
|
|
8
10
|
|
|
9
|
-
* [
|
|
10
|
-
* [BUGFIX] Rules: Fix Group.Equals() to take in account the new queryOffset too. Followup to #14061. #14273
|
|
11
|
+
* [BUGFIX] Remote-write: stop dropping samples in catch-up #14446
|
|
11
12
|
|
|
12
|
-
## 2.53.0
|
|
13
|
+
## 2.53.0 / 2024-06-16
|
|
13
14
|
|
|
14
|
-
This release changes the default for GOGC, the Go runtime control for the trade-off between excess memory use and CPU usage. We have found that Prometheus operates with minimal additional CPU usage, but greatly reduced memory by adjusting the upstream Go default from 100 to
|
|
15
|
+
This release changes the default for GOGC, the Go runtime control for the trade-off between excess memory use and CPU usage. We have found that Prometheus operates with minimal additional CPU usage, but greatly reduced memory by adjusting the upstream Go default from 100 to 75.
|
|
15
16
|
|
|
16
17
|
* [CHANGE] Rules: Execute 1 query instead of N (where N is the number of alerts within alert rule) when restoring alerts. #13980 #14048
|
|
17
|
-
* [CHANGE] Runtime: Change GOGC threshold from 100 to
|
|
18
|
-
* [FEATURE] Rules: Add new option `query_offset` for each rule group via rule group configuration file and `rule_query_offset` as part of the global configuration to have more resilience for remote write delays. #14061 #14216
|
|
18
|
+
* [CHANGE] Runtime: Change GOGC threshold from 100 to 75 #14176 #14285
|
|
19
|
+
* [FEATURE] Rules: Add new option `query_offset` for each rule group via rule group configuration file and `rule_query_offset` as part of the global configuration to have more resilience for remote write delays. #14061 #14216 #14273
|
|
19
20
|
* [ENHANCEMENT] Rules: Add `rule_group_last_restore_duration_seconds` metric to measure the time it takes to restore a rule group. #13974
|
|
20
21
|
* [ENHANCEMENT] OTLP: Improve remote write format translation performance by using label set hashes for metric identifiers instead of string based ones. #14006 #13991
|
|
21
22
|
* [ENHANCEMENT] TSDB: Optimize querying with regexp matchers. #13620
|