Skip to content

Conversation

@kruskall
Copy link
Member

Motivation/summary

apm-server registry could already exist, causing a failure on agent reload when trying to be recreated

Checklist

For functional changes, consider:

  • Is it observable through the addition of either logging or metrics?
  • Is its use being published in telemetry to enable product improvement?
  • Have system tests been added to avoid regression?

How to test these changes

Related issues

@kruskall kruskall requested a review from a team as a code owner July 31, 2025 12:51
@github-actions
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@mergify
Copy link
Contributor

mergify bot commented Jul 31, 2025

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

  • backport-7.17 is the label to automatically backport to the 7.17 branch.
  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • backport-9./d is the label to automatically backport to the 9./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
Member

@carsonip carsonip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

backport 9.1 and 8.19?

@kruskall kruskall added backport-9.0 Automated backport to the 9.0 branch backport-8.19 Automated backport to the 8.19 branch backport-9.1 Automated backport to the 9.1 branch labels Jul 31, 2025
@kruskall kruskall added this pull request to the merge queue Jul 31, 2025
Merged via the queue into elastic:main with commit b17e61d Jul 31, 2025
21 checks passed
@kruskall kruskall deleted the fix/get-or-create-telemetry-registry branch July 31, 2025 13:31
mergify bot pushed a commit that referenced this pull request Jul 31, 2025
mergify bot pushed a commit that referenced this pull request Jul 31, 2025
(cherry picked from commit b17e61d)

# Conflicts:
#	internal/beater/telemetry.go
mergify bot pushed a commit that referenced this pull request Jul 31, 2025
mergify bot added a commit that referenced this pull request Jul 31, 2025
mergify bot added a commit that referenced this pull request Jul 31, 2025
@marclop marclop mentioned this pull request Aug 4, 2025
@lahsivjar lahsivjar mentioned this pull request Aug 4, 2025
1 task
@rubvs rubvs mentioned this pull request Aug 6, 2025
1 task
@rubvs
Copy link
Contributor

rubvs commented Aug 6, 2025

Manually tested with BC for:

  • 9.1.0-SNAPSHOT
Screenshot 2025-08-06 at 11 54 10 AM
  • 8.19.0-SNAPSHOT
Screenshot 2025-08-06 at 11 54 19 AM
  • 9.1.1
Screenshot 2025-08-06 at 11 54 46 AM
  • 8.19.1
Screenshot 2025-08-06 at 11 54 35 AM

@1pkg 1pkg mentioned this pull request Aug 7, 2025
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-8.19 Automated backport to the 8.19 branch backport-9.0 Automated backport to the 9.0 branch backport-9.1 Automated backport to the 9.1 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants