aboutsummaryrefslogtreecommitdiff
path: root/kamon-core-tests/src/test/resources/reference.conf
diff options
context:
space:
mode:
Diffstat (limited to 'kamon-core-tests/src/test/resources/reference.conf')
-rw-r--r--kamon-core-tests/src/test/resources/reference.conf119
1 files changed, 119 insertions, 0 deletions
diff --git a/kamon-core-tests/src/test/resources/reference.conf b/kamon-core-tests/src/test/resources/reference.conf
index 0d7ae9e2..d165249e 100644
--- a/kamon-core-tests/src/test/resources/reference.conf
+++ b/kamon-core-tests/src/test/resources/reference.conf
@@ -2,4 +2,123 @@ kamon {
context.codecs.string-keys {
request-id = "X-Request-ID"
}
+}
+
+
+
+kamon {
+ instrumentation {
+ http-server {
+ noop {
+
+ #
+ # Configuration for HTTP context propagation
+ #
+ propagation {
+
+ # Enables or disables HTTP context propagation on this HTTP server instrumentation. Please note that if
+ # propagation is disabled then some distributed tracing features will not be work as expected (e.g. Spans can
+ # be created and reported but will not be linked across boundaries nor take trace identifiers from tags).
+ enabled = no
+
+ # HTTP propagation channel to b used by this instrumentation. Take a look at the kamon.propagation.http.default
+ # configuration for more details on how to configure the detault HTTP context propagation.
+ channel = "default"
+ }
+
+
+ #
+ # Configuration for HTTP server metrics collection
+ #
+ metrics {
+
+ # Enables collection of HTTP server metrics
+ enabled = no
+
+ # Tags to include on the HTTP server metrics. The available options are:
+ # - method: HTTP method from the request.
+ # - status-code: HTTP status code from the responses.
+ #
+ tags = [
+ "method",
+ "status-code"
+ ]
+ }
+
+
+ #
+ # Configuration for HTTP request tracing
+ #
+ tracing {
+
+ # Enables HTTP request tracing. When enabled the instrumentation will create Spans for incoming requests
+ # and finish them when the response is sent back to the clients.
+ enabled = no
+
+ # Select a context tag that provides a custom trace identifier. The custom trace identifier will be used
+ # only if all these conditions are met:
+ # - the context tag is present.
+ # - there is no parent Span on the incoming context (i.e. this is the first service on the trace).
+ # - the identifier is valued in accordance to the identity provider.
+ trace-id-tag = "none"
+
+ # Enables collection of span metrics using the `span.processing-time` metric.
+ span-metrics = on
+
+ # Select which tags should be included as span and span metric tags. The possible options are:
+ # - span: the tag is added as a Span tag (i.e. using span.tag(...))
+ # - metric: the tag is added a a Span metric tag (i.e. using span.tagMetric(...))
+ # - off: the tag is not used.
+ #
+ tags {
+
+ # Use the http.url tag.
+ url = span
+
+ # Use the http.method tag.
+ method = metric
+
+ # Use the http.status_code tag.
+ status-code = metric
+
+ # Copy tags from the context into the Spans with the specified purpouse.
+ from-context {
+
+ # The peer tag identifiest the service that is calling the current service. It is added by default with
+ # the HttpClient instrumentation.
+ peer = metric
+ }
+ }
+
+ # Custom mappings between routes and operation names.
+ operations {
+
+ # Operation name for Spans created on requests that could not be handled by any route in the current
+ # application.
+ unhandled = "unhandled"
+
+ # Provides custom mappings from HTTP paths into operation names. Meant to be used in cases where the bytecode
+ # instrumentation is not able to provide a sensible operation name that is free of high cardinality values.
+ # For example, with the following configuration:
+ # mappings {
+ # "/organization/*/user/*/profile" = "/organization/:orgID/user/:userID/profile"
+ # "/events/*/rsvps" = "EventRSVPs"
+ # }
+ #
+ # Requests to "/organization/3651/user/39652/profile" and "/organization/22234/user/54543/profile" will have
+ # the same operation name "/organization/:orgID/user/:userID/profile".
+ #
+ # Similarly, requests to "/events/aaa-bb-ccc/rsvps" and "/events/1234/rsvps" will have the same operation
+ # name "EventRSVPs".
+ #
+ # The patterns are expressed as globs and the operation names are free form.
+ #
+ mappings {
+
+ }
+ }
+ }
+ }
+ }
+ }
} \ No newline at end of file