OBSDOCS-2326: Logging Z-Stream Release Notes - 6.1.8 #98302
Conversation
|
@theashiot: This pull request references OBSDOCS-2326 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci
bot
added
the
size/M
|
🤖 Wed Sep 10 10:53:00 - Prow CI generated the docs preview: |
|
@theashiot: This pull request references OBSDOCS-2326 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
theashiot
force-pushed
the
OBSDOCS-2326
branch
from
a7f0acb to
8bff96a
Compare
openshift-ci
bot
added
size/S
theashiot
force-pushed
the
OBSDOCS-2326
branch
from
8bff96a to
1351907
Compare
|
/lgtm |
|
/lgtm |
theashiot
force-pushed
the
OBSDOCS-2326
branch
from
1351907 to
419e124
Compare
|
New changes are detected. LGTM label has been removed. |
openshift-ci
bot
added
size/M
|
@theashiot: This pull request references OBSDOCS-2326 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Thanks, @vparfonov, @anpingli ! |
|
@theashiot: This pull request references OBSDOCS-2326 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Thanks, @gabriel-rh! |
theashiot
force-pushed
the
OBSDOCS-2326
branch
from
419e124 to
4cd280a
Compare
theashiot
force-pushed
the
OBSDOCS-2326
branch
2 times, most recently
from
a0d4ca5 to
9748612
Compare
theashiot
force-pushed
the
OBSDOCS-2326
branch
from
9748612 to
9092531
Compare
| [id="logging-release-notes-6-1-8_{context}"] | ||
| = Logging 6.1.8 Release Notes | ||
|
|
||
| This release includes includes link:https://access.redhat.com/errata/RHBA-2025:15565[RHBA-2025:15565]. |
There was a problem hiding this comment.
| This release includes includes link:https://access.redhat.com/errata/RHBA-2025:15565[RHBA-2025:15565]. | |
| This release includes link:https://access.redhat.com/errata/RHBA-2025:15565[RHBA-2025:15565]. |
|
|
||
| * Before this update, the `vector_buffer_byte_size` and `vector_buffer_events` metrics incorrectly reported negative values under certain system load and timing conditions. This led to unreliable monitoring, potentially masking buffer issues. With this update, a concurrent, centralized state tracker ensures that these metrics are always reported as non-negative values. This ensures that the metrics correctly report buffer sizes helping with accurate monitoring. (link:https://issues.redhat.com/browse/LOG-7594[LOG-7594]) | ||
|
|
||
| * Before this update, a log record with a malformed timestamp could cause the Vector agent to panic when attempting to forward logs to Loki. With this update, error handling for out-of-range timestamp values has been improved resolving the issue. (https://issues.redhat.com/browse/LOG-7600[LOG-7600]) |
There was a problem hiding this comment.
Shouldn't this have "link" in the link?
| * Before this update, a log record with a malformed timestamp could cause the Vector agent to panic when attempting to forward logs to Loki. With this update, error handling for out-of-range timestamp values has been improved resolving the issue. (https://issues.redhat.com/browse/LOG-7600[LOG-7600]) | |
| * Before this update, a log record with a malformed timestamp could cause the Vector agent to panic when attempting to forward logs to Loki. With this update, error handling for out-of-range timestamp values has been improved resolving the issue. (link:https://issues.redhat.com/browse/LOG-7600[LOG-7600]) | |
| [NOTE] | ||
| ==== | ||
| For detailed information on Red{nbsp}Hat security ratings, review link:https://access.redhat.com/security/updates/classification/#important[Severity ratings]. | ||
| ==== No newline at end of file |
There was a problem hiding this comment.
| ==== | |
| ==== | |
theashiot
force-pushed
the
OBSDOCS-2326
branch
from
9092531 to
272ed1a
Compare
|
Thanks, @briandooley, I've made the required changes. Best, |
|
@theashiot: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
briandooley
merged commit c020f18
into
openshift:standalone-logging-docs-6.1
9 participants
Version(s): 6.1
Issue: https://issues.redhat.com/browse/OBSDOCS-2326
Link to docs preview: https://98302--ocpdocs-pr.netlify.app/openshift-logging/latest/release_notes/logging-release-notes-6.1.html
QE review:
Additional information: Note that this PR includes 6.17 release notes because they were missing. The contents of the 6.17 release notes had been reviewed here: #94862