Hybrid Data Pipeline supports correlated logging. Correlated logging enables you to track and relate activity across Hybrid Data Pipeline and client components by tagging each request with a unique correlation or trace ID. As requests move through Hybrid Data Pipeline services, this ID is included in logs, making it easy to follow the flow of operations from start to finish.

You may specify a correlation or trace ID for JDBC, ODBC, and OData clients.

JDBC

For JDBC clients, you may specify a correlation ID using the TraceID property in the JDBC driver. For example:

jdbc:datadirect:ddhybrid://myhost:8443;hybridDataPipelineDataSource=myDS;TraceID=<your-unique-id>

See also TraceID.

ODBC

For ODBC clients, you may specify a correlation ID with the Trace ID option in the ODBC driver. For example, a connection string or DSN would include TraceID=<your-unique-id>.

For programmatic configuration, use the SQL_ATTR_TRACE_ID connection attribute.

See also Trace ID.

OData

For OData clients, you may specify a correlation ID by passing the ID in the Trace-ID HTTP header. For example:

Trace-ID: <your-unique-id>

See also Correlated Logging HTTP header.