Skip to content

[DOC-14397]: DOC: Application Telemetry needs additional info.#4123

Open
RayOffiah wants to merge 3 commits into
release/8.0from
DOC-14397--8.0--Application-Telemetry-needs-additional-info
Open

[DOC-14397]: DOC: Application Telemetry needs additional info.#4123
RayOffiah wants to merge 3 commits into
release/8.0from
DOC-14397--8.0--Application-Telemetry-needs-additional-info

Conversation

Added more information on application telemetry to application-telemetry.adoc

Added link to the new information on metrics-reference.adoc
@RayOffiah RayOffiah self-assigned this Jun 3, 2026
@RayOffiah RayOffiah added the enhancement New feature or request label Jun 3, 2026
@RayOffiah RayOffiah requested review from Copilot, ggray-cb and hyunjuV June 3, 2026 09:22

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds more guidance on enabling Couchbase Server application telemetry and surfaces a new navigation link from the metrics reference to the application telemetry documentation.

Changes:

  • Added an “Enabling telemetry” IMPORTANT callout with example curl commands and SDK tracing links.
  • Added an “Application Telemetry” link entry to the metrics reference index.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File Description
modules/rest-api/pages/application-telemetry.adoc Adds an IMPORTANT block documenting how to check/enable telemetry and where to find SDK tracing guidance.
modules/metrics-reference/pages/metrics-reference.adoc Adds a new link entry referencing the application telemetry documentation from the metrics reference page.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread modules/rest-api/pages/application-telemetry.adoc Outdated
Comment thread modules/rest-api/pages/application-telemetry.adoc
Comment thread modules/rest-api/pages/application-telemetry.adoc
Comment thread modules/metrics-reference/pages/metrics-reference.adoc
Made corrections following the Copilot review

Signed-off-by: Ray Offiah <ray.offiah@couchbase.com>

@ggray-cb ggray-cb left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Added diagram and section for the histograms.

Signed-off-by: Ray Offiah <ray.offiah@couchbase.com>
@RayOffiah RayOffiah requested review from avsej and programmatix June 10, 2026 11:34

@avsej avsej left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, only couple of markup fixes. And also I am not sure what is the accepted format for hostname in cURL snippets, personally I like how one of your examples used placeholders which got highlighted with yellow, but maybe the other variant with just localhost:8091 is more copy/paste friendly. But they must be consistent throughout the document, I believe


[source, bash]
----
curl -u Administrator:password -X GET http://localhost:8091/settings/appTelemetry | jq

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
curl -u Administrator:password -X GET http://localhost:8091/settings/appTelemetry | jq
curl -u Administrator:password -X GET http://##{host}##:##{port}##/settings/appTelemetry | jq

[source, bash]
----
curl -u Administrator:password -X POST \
http://localhost:8091/settings/appTelemetry \

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
http://localhost:8091/settings/appTelemetry \
http://##{host}##:##{port}##/settings/appTelemetry \


[#histogram-output]
.Histogram output
====

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
====
[source]
----

sdk_kv_retrieval_duration_milliseconds_bucket{le="+Inf",agent="sdk/2.4.5.0",bucket="travel-sample",node="node1",node_uuid="91442eb8202e0e16bbb59624d9ccdb0a"} 144320
sdk_kv_retrieval_duration_milliseconds_sum{agent="sdk/2.4.5.0",bucket="travel-sample",node="node1",node_uuid="91442eb8202e0e16bbb59624d9ccdb0a"} 53423000
sdk_kv_retrieval_duration_milliseconds_count{agent="sdk/2.4.5.0",bucket="travel-sample",node="node1",node_uuid="91442eb8202e0e16bbb59624d9ccdb0a"} 144320
====

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
====
----

[#histogram-output]
.Histogram output
====
#sdk_kv_retrieval_duration_milliseconds_bucket{le="1",agent="sdk/2.4.5.0",bucket="travel-sample",node="node1",node_uuid="91442eb8202e0e16bbb59624d9ccdb0a"} 24054#

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#sdk_kv_retrieval_duration_milliseconds_bucket{le="1",agent="sdk/2.4.5.0",bucket="travel-sample",node="node1",node_uuid="91442eb8202e0e16bbb59624d9ccdb0a"} 24054#
sdk_kv_retrieval_duration_milliseconds_bucket{le="1",agent="sdk/2.4.5.0",bucket="travel-sample",node="node1",node_uuid="91442eb8202e0e16bbb59624d9ccdb0a"} 24054


<<histogram-output>> demonstrates a series of `kv` retrieval times for the buckets in a node.
Each line gives the retrieval count for a particular range.
(The count for retrieval durations for milliseconds stem:[le 1] is 24,054, milliseconds stem:[le 10] is 33,444, etc).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
(The count for retrieval durations for milliseconds stem:[le 1] is 24,054, milliseconds stem:[le 10] is 33,444, etc).
The retrieval duration counts are grouped by latency buckets: for example, requests completed in `<= 1 ms` total `24,054`, those in `<=10 ms` total `33,444`, and so on.

this paragraph is not clear. I believe "bucket" term will be better fit here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants