Skip to content

Conversation

jcantrill
Copy link
Contributor

Description

This PR:

  • Modifies the default datamodel when forwarding to LokiStack to be 'Otel'
  • Updates the API documentation to identify 'Viaq' to be deprecated and not honored in a future release

Links

https://issues.redhat.com/browse/LOG-7618

@jcantrill
Copy link
Contributor Author

/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 Sep 2, 2025
Copy link
Contributor

openshift-ci bot commented Sep 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill

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 Sep 2, 2025
@jcantrill jcantrill changed the title Log7618 LOG-7618: Modify lokistack datamodel to default to 'Otel' in lieu of 'Viaq' Sep 4, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 4, 2025

@jcantrill: This pull request references LOG-7618 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.8.0" version, but no target version was set.

In response to this:

Description

This PR:

  • Modifies the default datamodel when forwarding to LokiStack to be 'Otel'
  • Updates the API documentation to identify 'Viaq' to be deprecated and not honored in a future release

Links

https://issues.redhat.com/browse/LOG-7618

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 4, 2025
@jcantrill jcantrill force-pushed the log7618 branch 2 times, most recently from 67cfc4f to 6a4dcdb Compare September 5, 2025 17:28
@jcantrill
Copy link
Contributor Author

/retest

@Clee2691
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 11, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 11, 2025
@jcantrill
Copy link
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 11, 2025
@Clee2691
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 11, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ca54f0c and 2 for PR HEAD a02aec6 in total

Copy link
Contributor

openshift-ci bot commented Sep 11, 2025

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

@openshift-merge-bot openshift-merge-bot bot merged commit d4f10fa into openshift:master Sep 11, 2025
8 checks passed
@jcantrill jcantrill deleted the log7618 branch September 12, 2025 12:31
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. release/6.4
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants