Skip to content

Conversation

swiatekm
Copy link
Contributor

What does this PR do?

Why is it important?

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

Copy link
Contributor

mergify bot commented Sep 29, 2025

This pull request does not have a backport label. Could you fix it @swiatekm? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

Copy link

@swiatekm swiatekm force-pushed the feat/self-monitoring-otel-default branch from ca48a67 to 91a3eee Compare September 30, 2025 13:19
Copy link
Contributor

mergify bot commented Oct 1, 2025

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b feat/self-monitoring-otel-default upstream/feat/self-monitoring-otel-default
git merge upstream/main
git push upstream feat/self-monitoring-otel-default

@swiatekm swiatekm force-pushed the feat/self-monitoring-otel-default branch 2 times, most recently from 0b48117 to 58c6ae1 Compare October 1, 2025 12:03
@cmacknz cmacknz added the backport-9.2 Automated backport to the 9.2 branch label Oct 1, 2025
@swiatekm swiatekm force-pushed the feat/self-monitoring-otel-default branch from f4f4aee to 9d1eabf Compare October 2, 2025 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-9.2 Automated backport to the 9.2 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants