.NET Instrumentation (Running on Kubernetes)

this document explains how to instrument the net application with kloudmate, using opentelemetry this instrumentation can be possible using the opentelemetry operator, which supports injecting and configuring auto instrumentation libraries for net, java, node js, python, and go service pre requisites running a kubernetes cluster the https //cert manager io/docs/installation/ must be installed if you use the helm chart, there is an option to generate a self signed cert instead step 1 first, install the https //github com/open telemetry/opentelemetry operator into your cluster you can do this with the https //github com/open telemetry/opentelemetry operator#getting started , the https //github com/open telemetry/opentelemetry helm charts/tree/main/charts/opentelemetry operator#opentelemetry operator helm chart , or with https //operatorhub io/operator/opentelemetry operator bash kubectl apply f https //github com/open telemetry/opentelemetry operator/releases/latest/download/opentelemetry operator yaml step 2 create an opentelemetry collector to send telemetry from containers to a collector instead of directly to a backend for example, here is a demo collector used kubectl apply f <\<eof apiversion opentelemetry io/v1beta1 kind opentelemetrycollector metadata name demo namespace default #change namespace spec config receivers otlp protocols grpc endpoint 0 0 0 0 4317 http endpoint 0 0 0 0 4318 processors memory limiter check interval 1s limit percentage 75 spike limit percentage 15 batch send batch size 10000 timeout 10s exporters debug {} otlphttp endpoint 'https //otel kloudmate com 4318' headers authorization kloudmate api key service pipelines traces receivers \[otlp] processors \[memory limiter, batch] exporters \[debug, otlphttp] metrics receivers \[otlp] processors \[memory limiter, batch] exporters \[debug, otlphttp] logs receivers \[otlp] processors \[memory limiter, batch] exporters \[debug, otlphttp] eof change your kloudmate workspace api key to configure the collector to export data to kloudmate step 3 configure automatic instrumentation to be able to manage automatic instrumentation, the operator needs to be configured to know what pods to the instrument and which automatic instrumentation to use for those pods this is done via the https //github com/open telemetry/opentelemetry operator/blob/main/docs/api/instrumentations md for our example, we used net sdk auto instrumentation the following command creates a basic instrumentation resource that is configured for instrumenting net services to get metrics, logs, and traces yaml kubectl apply f <\<eof apiversion opentelemetry io/v1alpha1 kind instrumentation metadata name demo instrumentation namespace default #change namespace spec exporter endpoint http //demo collector 4318 propagators \ tracecontext \ baggage sampler type parentbased traceidratio argument "1" eof the endpoint used under exporter must be the same as the service name of the collector created in step 2 use only one instrumentation command as per the requirement step 4 now opt in your services to automatic instrumentation this is done by updating your service’s spec template metadata annotations spec template metadata annotations to include a language specific annotation net instrumentation opentelemetry io/inject dotnet "true" "true" to patch your existing net application with the necessary annotation use the below command bash kubectl patch deployment \<deployment name> n \<namespace> p '{"spec" {"template" {"metadata" {"annotations" {"instrumentation opentelemetry io/inject dotnet" "true"}}}}}'