Modernize OTel semantic conventions, add diverse API endpoints, and fix trace ID uniqueness

[manojhosk]

Summary

This PR modernizes the test-telemetry-generator to align with the latest OpenTelemetry semantic conventions, adds configurable diverse API endpoint generation, fixes a trace/span ID uniqueness bug, and improves load generation configurability.

Changes

1. Update to latest OTel semantic conventions

All example definition files (simple, demo, QA, JSON) have been updated to use current stable attribute names:

HTTP attributes:

• http.method → http.request.method
• http.target → url.path
• http.scheme → url.scheme
• net.host.name → server.address
• http.client_ip → client.address
• Added: http.route, http.response.status_code, server.port, network.protocol.version

Database attributes:

• db.system → db.system.name
• db.operation → db.operation.name
• net.peer.ip → network.peer.address
• net.peer.name → server.address
• Added: db.namespace, db.collection.name, network.peer.port

Messaging attributes:

• messaging.backend.topic → messaging.destination.name

Resource attributes:

• http.host → server.address
• http.port → server.port

2. Add diverse API endpoint generation via roundRobin

Expanded roundRobin lists to 20 entries across HTTP methods (GET, POST, PUT, DELETE), URL paths, routes, DB operations, and collection names. This enables realistic load testing with diverse API traffic patterns without any code changes — just edit the YAML lists.

3. Fix trace structure for inter-service calls (demo)

Restructured the demo trace definition to include proper SPAN_KIND_CLIENT / SPAN_KIND_SERVER span pairs for inter-service communication (frontend → checkout → email/currency), with url.full on client spans and url.path on server spans per OTel spec.

4. Fix trace/span ID uniqueness bug

Fixed a bug in SpansGenerator.java where Protobuf Span.Builder objects were mutated in-place, causing all copies within a payload cycle to share the same trace and span IDs. The fix clones the builder for each copy.

5. Configurable load generation rate

• Added payloadCount, copyCount, and payloadFrequencySeconds to all example trace definitions with inline documentation explaining the formula:
  • Traces/sec = copyCount / payloadFrequencySeconds
  • Total traces = payloadCount × copyCount
  • Duration = payloadCount × payloadFrequencySeconds
• Lowered minimum payloadFrequencySeconds from 15s to 1s in RootSpanDefinition.java
• Default config: 5 traces every 10 seconds, 150 total traces, 5-minute run

6. Improve error messages

Extracted hardcoded threshold into a variable and fixed missing spaces and unit suffixes in validation error messages for payloadFrequencySeconds.

Files changed (9 files)

File	Change
example-definitions/simple/trace-definition.yaml	Updated semconv, added roundRobin entries, rate control
example-definitions/demo/trace-definition.yaml	Updated semconv, restructured with CLIENT/SERVER pairs, rate control
example-definitions/qa/trace-definition.yaml	Updated messaging attribute
example-definitions/simple/resource-definition.yaml	Updated resource attributes
example-definitions/qa/resource-definition.yaml	Updated resource attributes
example-definitions/json/trace-definition.json	Mirrored demo YAML changes
example-definitions/json/resource-definition.json	Updated resource attributes
src/.../traces/SpansGenerator.java	Fixed span ID uniqueness via builder cloning
src/.../traces/dto/RootSpanDefinition.java	Lowered min frequency, improved error messages

Test plan

• Build passes: `./gradlew clean build fat