From 2c5e6d9f09da482a2f0805f762b7a014b0376ae5 Mon Sep 17 00:00:00 2001 From: Pablo Baeyens Date: Tue, 26 Sep 2023 14:10:08 +0200 Subject: [PATCH] Add changelog entry --- .chloggen/mx-psi_system.memory.limit.yaml | 28 +++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100755 .chloggen/mx-psi_system.memory.limit.yaml diff --git a/.chloggen/mx-psi_system.memory.limit.yaml b/.chloggen/mx-psi_system.memory.limit.yaml new file mode 100755 index 000000000000..d2c33cea95d4 --- /dev/null +++ b/.chloggen/mx-psi_system.memory.limit.yaml @@ -0,0 +1,28 @@ +# Use this changelog template to create an entry for release notes. + +# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' +change_type: enhancement + +# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver) +component: hostmetricsreceiver + +# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). +note: "Add `system.memory.limit` metric reporting the total memory available." + +# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. +issues: [30306] + +# (Optional) One or more lines of additional information to render under the primary note. +# These lines will be padded with 2 spaces and then inserted directly into the document. +# Use pipe (|) for multiline entries. +subtext: | + This metric is opt-in. To enable it, set `scrapers::memory::metrics::system.memory.limit::enabled` to `true` in the hostmetrics config. + +# If your change doesn't affect end users or the exported elements of any package, +# you should instead start your pull request title with [chore] or use the "Skip Changelog" label. +# Optional: The change log or logs in which this entry should be included. +# e.g. '[user]' or '[user, api]' +# Include 'user' if the change is relevant to end users. +# Include 'api' if there is a change to a library API. +# Default: '[user]' +change_logs: []