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 meter registry processor causing incompatibility with Armory's Observability plugin #4224

Merged

Conversation

massimo-pacher-tw
Copy link
Contributor

@massimo-pacher-tw massimo-pacher-tw commented Feb 28, 2022

This PR fixes armory-plugins/armory-observability-plugin#32 (comment).

It allows other BeanPostProcessor (e.g. Spring MeterRegistryBeanPostProcessor) to process registry implementations, restoring the exported metrics and aligning the behavior to the other spinnaker services.

I've retrofitted a test showing the missed processing of a dummy BeanPostProcessor, but more details are available on the issue.

We noticed this issue extends to Kayenta too, given it pulls in orca-core modules and the affected classes, preventing the Observability plugin to export standard metrics (due to the binders - e.g. JvmMetrics - not being bound ).

@spinnakerbot
Copy link
Contributor

The following commits need their title changed:

  • ea5f84d: retrofit integration test

  • 4717b56: allow registry implementations to be processed by other BeanPostProcessors

Please format your commit title into the form:

<type>(<scope>): <subject>, e.g. fix(kubernetes): address NPE in status check

This allows us to easily generate changelogs & determine semantic version numbers when cutting releases. You can read more about commit conventions here.

Allow registry implementations to be processed by other BeanPostProcessors
Fix armory-plugins/armory-observability-plugin#32
@mattgogerly
Copy link
Member

Thank you for fixing this!

@mattgogerly mattgogerly added the ready to merge Approved and ready for merge label Feb 28, 2022
@mergify mergify bot added the auto merged Merged automatically by a bot label Feb 28, 2022
@mergify mergify bot merged commit d168010 into spinnaker:master Feb 28, 2022
@dbyron-sf
Copy link
Contributor

Yes, thanks much @massimo-pacher-tw! If kayenta picks up the fix by releasing a new version of orca, and doesn't have any place to fix directly within kayenta, then I think we're set. We'll figure out a good time to tag orca and bump the version in kayenta.

@massimo-pacher-tw
Copy link
Contributor Author

Yes, thanks much @massimo-pacher-tw! If kayenta picks up the fix by releasing a new version of orca, and doesn't have any place to fix directly within kayenta, then I think we're set. We'll figure out a good time to tag orca and bump the version in kayenta.

It seems that's enough yes, I've just deployed our fork using the new, fixed, orca version and metrics appear correctly.

@dbyron-sf
Copy link
Contributor

I tagged v8.21.0 of orca with this fix. Here's the kayenta PR to pick up the change.

@massimo-pacher-tw
Copy link
Contributor Author

I did the exact same fix in our fork, thanks for the bump 🙇‍♂️

@massimo-pacher-tw massimo-pacher-tw deleted the fix_meter_registry_processor branch March 3, 2022 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto merged Merged automatically by a bot ready to merge Approved and ready for merge target-release/1.28
Projects
None yet
Development

Successfully merging this pull request may close these issues.

NaN Values on some JVM metrics
4 participants