Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-6.1] LOG-6755 add timestamp to fix console #2964

Open
wants to merge 1 commit into
base: release-6.1
Choose a base branch
from

Conversation

cahartma
Copy link
Contributor

Description

Manual backport for 6.1. This fixes the console and aligns timestamp with the existing @timestamp We are still awaiting a Loki update to time-based sharding that will prevent any date concern as originally discussed in the ticket.

We will want to wait until the Loki update is implemented before marking this as resolved.

/cc @Clee2691 @vparfonov @xperimental
/assign @jcantrill

Links

Copy link
Contributor

openshift-ci bot commented Feb 19, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cahartma

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 19, 2025
Copy link
Contributor

openshift-ci bot commented Feb 19, 2025

@cahartma: 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.

@jcantrill
Copy link
Contributor

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 20, 2025
@jcantrill
Copy link
Contributor

added comment to #2965 which apply here as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. release/6.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants