NH-143529 ResponseTime processor handles HTTP status code if non-compliant string

[tammy-baylis-swi]

Adds ResponseTime metrics processor handling and debug logging if HTTP status code is a string, to prevent stacktrace from APM library.

String status code is non-compliant but can still happen easily in practice, e.g. AWS Lambda function responses. Status code should be a 3-digit integer according to:

• RFC
• AWS WAF (no Lambda equivalent doc but good links)
• OTel semconv

[Copilot]

Pull request overview

This PR hardens ResponseTimeProcessor so response-time metrics generation doesn’t raise when instrumentations emit non-compliant HTTP status code types (notably string values, e.g., some AWS Lambda responses). It fits into the SolarWinds APM OpenTelemetry distribution by making the span-to-metrics attribute extraction more resilient while keeping existing fallback behavior.

Changes:

• Convert http.response.status_code / deprecated http.status_code to int when possible, with debug logging on invalid values.
• Ensure HTTP request method values are coerced to str before being added to metric attributes.
• Add unit tests covering string/invalid HTTP status codes and fallback behavior.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
solarwinds_apm/trace/response_time_processor.py	Adds status-code type coercion and debug logging; coerces request method to string for metric attributes.
tests/unit/test_processors/test_response_time_processor.py	Adds coverage for string/invalid status code handling and expected logging behavior.

[cheempz]

LGTM