Current Harness Delegate logs do not distinguish whether errors such as SocketTimeoutException, ConnectionRefused, or UnknownHostException are caused by internal failures or external services being down/unreachable. This makes it difficult to troubleshoot and classify issues in Splunk.

Request:

Enhance logging to include:

Dependency name (e.g., artifactory, github, vault etc)

Full endpoint or hostname used

Structured error type (timeout, dns_failure, connection_refused, etc.)

JSON‑structured log format for machine parsing

Business Impact:

Clearer logging will reduce troubleshooting time, enable reliable Splunk alerting, and help quickly identify outages of upstream dependencies.

Acceptance Criteria:

Dependency identified in all related log entries

URL/hostname included

Error type classified

Logs emitted in structured format (JSON preferred)