feat(http): added configurable 4xx error classification for exit spans

[aryamohanan]

Added support for configurable HTTP 4xx error classification for HTTP exit (client) spans.

Configuration

Classify all 4xx responses as errors

env var

INSTANA_TRACING_HTTP_EXIT_CLASSIFY_ALL_4XX_AS_ERRORS=true

In code

tracing: {
  http: {
    exit: {
      classifyAll4xxAsErrors: true
    }
  }
}

agent.yaml

com.instana.tracing:
  http:
    exit:
      classify-all-4xx-as-errors: true

Classify only specific 4xx responses as errors

env var

INSTANA_TRACING_HTTP_EXIT_CLASSIFY_AS_ERRORS=401,403

In code

tracing: {
  http: {
    exit: {
      classifyAsErrors: [401, 403]
    }
  }
}

agent.yaml

com.instana.tracing:
  http:
    exit:
      classify-as-errors:
        - 401
        - 403

Precedence

classify-as-errors takes precedence over classify-all-4xx-as-errors. When a non-empty list is configured, only the listed status codes are marked as errors.

TODO

• ENV var support
• IN-code config support
• Agent config support
• Unit tests
• HTTP client instrumentation update
• Integration test
• Public doc update https://github.ibm.com/instana/docs/pull/20187/files

ref https://jsw.ibm.com/browse/INSTA-100637

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[kirrg001]

Great work!

Suggestion:

feat(http): added configurable 4xx error classification for exit spans