Skip to content

Conversation

@dsessler7
Copy link
Contributor

…y collector 0.125.0.

Checklist:

  • Have you added an explanation of what your changes do and why you'd like them to be included?
  • Have you updated or added documentation for the change, as applicable?
  • Have you tested your changes on all related environments with successful results, as applicable?
    • Have you added automated tests?

Type of Changes:

  • New feature
  • Bug fix
  • Documentation
  • Testing enhancement
  • Other

What is the current behavior (link to any open issues here)?

OTel collector 0.125.0 fails to run with our current transform processor configuration for postgres logs.

What is the new behavior (if this is a feature change)?

  • Breaking change (fix or feature that would cause existing functionality to change)

OTel collector 0.125.0 will now run; however, these changes are not backwards compatible with collector 0.119.0.

Other Information:

@dsessler7 dsessler7 force-pushed the log-context-for-collector-0.125.0-fix branch from 33f5bf4 to 53fd3ea Compare May 9, 2025 01:24
@dsessler7
Copy link
Contributor Author

The otel-logging-and-metrics kuttl test will fail here as this change to the operator is not compatible with the 0.119.0 collector. Once the 0.125.0 collector image is released, the kuttl test will start passing again.

@jmckulk jmckulk merged commit 5593bbe into CrunchyData:main May 9, 2025
13 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants