makarandhinge opened a new pull request, #8095:
URL: https://github.com/apache/geode/pull/8095

   <!-- Thank you for submitting a contribution to Apache Geode. -->
   
   <!-- In order to streamline review of your contribution we ask that you
   ensure you've taken the following steps. -->
   
   ### For all changes, please confirm:
   - [x] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?
   - [x] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?
   - [x] Is your initial contribution a single, squashed commit?
   - [x] Does `gradlew build` run cleanly?
   - [x] Have you written or updated unit tests to verify your changes?
   - [x] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   
   ### Description
   
   Adds Micrometer Observation support to Apache Geode.
   
   The changes introduce observation support for cache and server operations 
using Micrometer's `ObservationRegistry`.
   
   ### Changes
   
   - Added Geode observation services and session management.
   - Added `ObservationRegistry` support to the cache lifecycle.
   - Added Micrometer observations for region `get` and `put` operations.
   - Added observation support around server command processing.
   - Added error recording for failed observations.
   - Added the Micrometer Observation dependency.
   - Added integration tests covering observation creation and error handling.
   
   ### Testing
   
   - Existing `geode-core` tests pass.
   - Added integration tests for Micrometer Observation support.
   - Verified observations are created for region `get` and `put` operations.
   - Verified failed operations record errors correctly.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to