Skip to content

Commit ccd27f7

Browse files
committed
chore: introduce metrics interface in change doc
1 parent 280a894 commit ccd27f7

File tree

2 files changed

+37
-0
lines changed

2 files changed

+37
-0
lines changed
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
[//]: # "Copyright Amazon.com Inc. or its affiliates. All Rights Reserved."
2+
[//]: # "SPDX-License-Identifier: CC-BY-SA-4.0"
3+
4+
# Interacting with a Metrics Interface in the AWS Encryption SDK family of products (Background)
5+
6+
## Definitions
7+
8+
### Conventions used in this document
9+
10+
The key words
11+
"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
12+
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
13+
in this document are to be interpreted as described in
14+
[RFC 2119](https://tools.ietf.org/html/rfc2119).
15+
16+
## Issues and Alternatives
17+
18+
### collecting metrics from customers?
19+
20+
Crypto Tools (CT) publishes software libraries. The latest
21+
versions of these libraries have no logging or metrics publishing
22+
to either a local application or to an observability service like AWS CloudWatch.
23+
24+
25+
26+
27+
### Why should supported libraries collect metrics?
28+
29+
Metrics collection has long been an outstanding feature request
30+
that has been
31+
32+
### Default Behavior?
33+
34+
35+
### Should Data Plane APIs fail if metrics fail to publish?
36+
37+

changes/2025-09-12_introduce-metrics-interface/proposal.md

Whitespace-only changes.

0 commit comments

Comments
 (0)