feat: Add OpenTelemetry instrumentation for ActiveJ HTTP server

[kcsurapaneni]

Overview

This PR introduces OpenTelemetry instrumentation for the ActiveJ framework, enabling distributed tracing and context propagation for ActiveJ-based HTTP servers. The changes allow developers to monitor and debug ActiveJ applications in distributed systems by capturing trace context from incoming requests and propagating it through responses.

Key Features

• Distributed Tracing: Automatically propagates trace context using the traceparent header.
• HTTP Attribute Extraction: Captures detailed HTTP attributes (e.g., method, path, headers, status code) for enriched telemetry data.
• Error Handling: Maps exceptions to appropriate HTTP status codes and associates them with spans for better error visibility.

Changes Included

1. Instrumentation:

   • ActiveJHttpServerConnectionInstrumentation: Instruments the serve method of ActiveJ servlets to capture and propagate trace context.

2. Testing:

   • Added test cases to validate tracing behavior and ensure compliance with W3C Trace Context.

3. Documentation:

   • Added README with details about the instrumentation, usage, and configuration.

Testing

• All existing tests pass successfully.
• New test cases have been added to validate:
  • Trace context propagation via the traceparent header.
  • Correctness of HTTP attribute extraction.
  • Error handling and span enrichment.

Benefits

• Observability for ActiveJ applications, making it easier to monitor and debug distributed systems.
• Seamless integration with OpenTelemetry exporters (e.g., Jaeger, Zipkin, HyperDX) for visualizing traces.

Related Issues

Closes #13202

Acknowledgments

This implementation was inspired by and adapted from the ActiveJ framework codebase. Special thanks to the ActiveJ community for their excellent work and contributions.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: trask / name: Trask Stalnaker (1420a18, c0b67a3, 20d00a0, c098084, 583801e)
• ✅ login: kcsurapaneni / name: Krishna Chaitanya Surapaneni (d5bb920, e1a29dc, 5a4d2dd, 429ad65, b287f78, 1662b23, ce368c1, a07317e, 4fd797f, b7aff9d, ac95594, 1cc6c5f, b241b45, b52c49d, b4e8e29, 7bf1776, 583e063, 6f01a1c, 65e6d57, 99a4c21, 7269a0e, f1cfe0e, 418a259, ef5ceec, 81827bc, dc94afa)
• ✅ login: renovate[bot] (2c31d8f, aba23a3, bb75dab, f6ef942, 0748348, f167d99, 6ec9373, bf3fe1f, 18b3cde, 2332b12, 483ec98, ad7692a, f6ee0dc, 036ae0b, dfb73d1)
• ✅ login: otelbot[bot] (fea36de, 4c149bd)
• ✅ login: laurit / name: Lauri Tulmin (5a92938, 37032d2, 87345f0, 9023ad8)
• ✅ login: jakobjoachim / name: Jakob Joachim (fe1151c)
• ✅ login: anuraaga / name: Anuraag (Rag) Agrawal (2f40b7f)
• ✅ login: masonedmison / name: Mason Lazalier Edmison (148a91a)
• ✅ login: zeitlinger / name: Gregor Zeitlinger (c142d7f)
• ✅ login: SylvainJuge (e802708)

[jaydeluca]

we will want integration tests for any new instrumentation

[kcsurapaneni]

we will want integration tests for any new instrumentation

@jaydeluca I have added test cases and resolved most of the workflow job failures. But, still there are couple of them are failing and not able to understand the cause after checking the raw logs as well. Could you please help me to understand what causing them to failure so that I can fix them. Thank you!

CC: @trask @laurit

[laurit]

See https://scans.gradle.com/s/dy73bc67fptxo/tests/task/:instrumentation:activej-http-6.0:javaagent:test/details/(N%2FA)/Gradle%20Test%20Executor%2045?top-execution=1
Framework seems to require java 17

[kcsurapaneni]

See https://scans.gradle.com/s/dy73bc67fptxo/tests/task/:instrumentation:activej-http-6.0:javaagent:test/details/(N%2FA)/Gradle%20Test%20Executor%2045?top-execution=1 Framework seems to require java 17

@laurit Thanks for the link. So, all the agents should support minimum java 8?

[laurit]

@laurit Thanks for the link. So, all the agents should support minimum java 8?

If the framework does not support java 8 then you shouldn't run the tests for it with java 8. Add

opentelemetry-java-instrumentation/instrumentation/spring/spring-security-config-6.0/library/build.gradle.kts

Lines 18 to 20 in 4c8f2dc

	otelJava {
	minJavaVersionSupported.set(JavaVersion.VERSION_17)
	}

[kcsurapaneni]

@laurit Thanks for the link. So, all the agents should support minimum java 8?

If the framework does not support java 8 then you shouldn't run the tests for it with java 8. Add

opentelemetry-java-instrumentation/instrumentation/spring/spring-security-config-6.0/library/build.gradle.kts

Lines 18 to 20 in 4c8f2dc

	otelJava {
	minJavaVersionSupported.set(JavaVersion.VERSION_17)
	}

Thanks for the help! @laurit . Build looks good now. Please review