Details
-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
0
Description
Release notes: The metrics-micrometer module's behaviour is changed to accommodate Micrometer issue 877. From core-io 2.4.10, SDK metrics were output in the following form, with the bucket, scope and/or collection tags added only to operations where they applied:
db.couchbase.operations{service="kv",db.name="bkt",db.couchbase.scope="scp",db.couchbase.collection="coll",outcome="success"}
|
db.couchbase.operations{service="query",outcome="success"}
|
However, this lead to Micrometer silently dropping some metrics due to the issue linked above. To avoid this, the SDK now outputs empty values for non-relevant tags, like so:
db.couchbase.operations{service="kv",db.name="bkt",db.couchbase.scope="scp",db.couchbase.collection="coll",outcome="success"}
|
db.couchbase.operations{service="query",db.name="",db.couchbase.scope="",db.couchbase.collection="",outcome="success"}
|
This change only affects the metrics-micrometer module. The metrics-opentelemetry module is unchanged.
See CBSE-17070
Attachments
Issue Links
- is duplicated by
-
JVMCBC-1518 Global Micrometer Registry ignores entries without all tags. query and transaction do not have all tags
- Closed
For Gerrit Dashboard: JVMCBC-1528 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
211401,3 | JCBC-2154: Provide default values for tags for Micrometer | master | couchbase-jvm-clients | Status: MERGED | +2 | +1 |