From 3a537d2caa9a9ddf0b5c2546eb27e22458e49dfc Mon Sep 17 00:00:00 2001 From: Roni Dover Date: Mon, 18 Mar 2024 22:08:23 +0000 Subject: [PATCH] GITBOOK-47: No subject --- .../covering-more-of-your-code-with-observability.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/instrumentation/spring-spring-boot-dropwizard-and-default/covering-more-of-your-code-with-observability.md b/instrumentation/spring-spring-boot-dropwizard-and-default/covering-more-of-your-code-with-observability.md index 41f8511..9f5f0ba 100644 --- a/instrumentation/spring-spring-boot-dropwizard-and-default/covering-more-of-your-code-with-observability.md +++ b/instrumentation/spring-spring-boot-dropwizard-and-default/covering-more-of-your-code-with-observability.md @@ -2,12 +2,14 @@ Beyond the automatic instrumentation of server and client libraries, you may wish to achieve a better understanding of your code and domain logic by collecting more tracing data. -### Using the @WithSpan annotations to observe specific methods +### Using the @WithSpan or @Observe annotations to observe specific methods Digma makes it easy to add additional observability coverage to any location. Placing the cursor inside any method you can click on the Observability icon in the Insights side panel to quickly add an annotation that will include its data in the traces.
+Note: If you're using the Micrometer Tracing observability strategy in Digma, clicking on `Add Observability` will add an @Observe annotation. Otherwise, the @WithSpan annotation will be used. + ### Keeping track of specific values or parameters Sometimes you may wish to include additional data in the trace, such as parameters, results, counters, or any other data that may later be useful when reviewing the trace.