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

Fix service destination max group scaling based on memory #11905

Merged

Conversation

carsonip
Copy link
Member

Motivation/summary

Fix regression introduced in #11739

  • Fix bug where code is never executed
  • Fix wrong log message

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

Fix regression introduced in elastic#11739

- Fix bug where code is never executed
- Fix wrong log message
@carsonip carsonip requested a review from a team as a code owner October 19, 2023 17:02
@carsonip carsonip requested a review from lahsivjar October 19, 2023 17:02
@mergify
Copy link
Contributor

mergify bot commented Oct 19, 2023

This pull request does not have a backport label. Could you fix it @carsonip? 🙏
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.

NOTE: backport-skip has been added to this pull request.

@mergify mergify bot added the backport-skip Skip notification from the automated backport with mergify label Oct 19, 2023
@carsonip carsonip added backport-8.11 Automated backport with mergify test-plan v8.11.0 and removed backport-skip Skip notification from the automated backport with mergify labels Oct 19, 2023
simitt
simitt previously approved these changes Oct 19, 2023
…com:carsonip/apm-server into fix-auto-service-destination-agg-max-groups
Copy link
Contributor

@lahsivjar lahsivjar left a comment

Choose a reason for hiding this comment

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

Thanks for fixing this.

@simitt simitt merged commit 791f582 into elastic:main Oct 20, 2023
mergify bot pushed a commit that referenced this pull request Oct 20, 2023
* Fix service destination max group scaling based on memory

Fix regression introduced in #11739

- Fix bug where code is never executed
- Fix wrong log message
- Fix failing test

(cherry picked from commit 791f582)
mergify bot added a commit that referenced this pull request Oct 23, 2023
…11906)

* Fix service destination max group scaling based on memory

Fix regression introduced in #11739

- Fix bug where code is never executed
- Fix wrong log message
- Fix failing test

(cherry picked from commit 791f582)

Co-authored-by: Carson Ip <[email protected]>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
@lahsivjar
Copy link
Contributor

Tested with 8.11.0 BC4, observed the required log lines:

Screenshot 2023-10-27 at 4 58 14 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants