Manual Instrumentation

manual instrumentation gives you full control over your observability data by using opentelemetry sdks directly in your application code this approach is ideal when you need custom business logic attributes, fine grained span management, or specialized metrics when to use when you need custom business logic attributes on spans and metrics when you want precise control over span boundaries and naming when auto instrumentation doesn't cover your specific libraries or frameworks when you need to add custom metrics beyond what auto instrumentation provides supported sdks the kloudmate agent works with any opentelemetry sdk configure your sdk to export telemetry data via otlp to the agent's endpoint https //docs kloudmate com/python https //docs kloudmate com/go https //docs kloudmate com/nodejs https //docs kloudmate com/java https //docs kloudmate com/net https //docs kloudmate com/php https //docs kloudmate com/ruby configuration point your opentelemetry sdk exporter to the kloudmate agent's otlp endpoint otel exporter otlp endpoint="http //localhost 4318" otel service name="your service name" combining with ebpf 💡 recommended approach start with docid\ fvvk4qsu9f 6j2l4ifil8 for instance, broad coverage, then strategically enrich with manual opentelemetry sdk instrumentation where you need custom business logic attributes