aws / aws/aws-encryption-sdk-java

CMM cache has no instrumentation

Open
#2,178 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
240
Forks
125
PR merge metrics
No merged PRs in 30d

Description

### Problem:

when using, and configuring the SDK, it would be good to understand the performance of the CMM cache, as having the cache to small can hurt performance

### Solution:

We could add open telemetry performance, maybe as an optional feature on the cache (that is what I have done in our application)

Happy to contribute this is its useful, and with some steer form the maintainers

In general is there a policy for instrumentation in thi project?

### Out of scope:

Contributor guide

Open the contributing guide

Research direction

Start by locating the CMM cache implementation and reviewing project guidance on instrumentation. Confirm the maintainers' preferred OpenTelemetry policy and define the scope of optional cache performance measurements; done means an agreed, tested instrumentation approach.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.