Observability

The connector emits OpenTelemetry-compatible activities and .NET metrics under Redis.Iris.AgentMemory.

Activities cover session.load, session.write, and ltm.search. Attributes are limited to operation, outcome, server address, HTTP status, result count, retry count, and error type. Response bodies, credentials, query text, identity values, store IDs, session IDs, and memory IDs are never recorded.

An Agent Framework history lookup for a session that has not yet been created is recorded with redis.iris.outcome=not_found and HTTP status 404, but an unset span status. It contributes to request and duration metrics, not redis.iris.errors. Direct GetSessionMemoryAsync calls retain normal not-found exception and error semantics.

Metrics:

Instrument Type Unit Attributes

redis.iris.requests

Counter

{request}

redis.iris.operation

redis.iris.errors

Counter

{error}

redis.iris.operation

redis.iris.retries

Counter

{retry}

redis.iris.operation

redis.iris.operation.duration

Histogram

ms

operation, outcome

redis.iris.recall.results

Histogram

{memory}

operation

redis.iris.messages.skipped

Counter

{message}

bounded reason

All metric attributes are bounded enums. Do not add endpoint, tenant, owner, session, actor, memory, query, or message content as metric dimensions.

RedisIrisMemoryProvider emits one structured application log containing the number of records returned by each recall search. Query text, identity values, memory IDs, source session IDs, and memory text are not logged or added to traces or metrics.

Context Retriever SDK logging

Context Retriever connector activities and metrics remain available independently of SDK logging. ContextRetrieverClientFactory does not forward its logger factory to the MCP SDK by default: SDK Trace messages can contain full tool arguments and results, which may contain personal data or secrets from the data source. For a controlled synthetic diagnostic session only, explicitly construct new ContextRetrieverClientFactory(loggerFactory, enableSensitiveLogging: true). This opt-in is separate from the host’s logging level; disable it afterward. It does not sanitize tool payloads. Restrict access, retention, and export of the chosen sink. Supplying only a logger factory does not enable SDK logging.

Docker demonstration

docker compose up --build runs the DevUI, an OpenTelemetry Collector, Jaeger, Prometheus, and Grafana. The DevUI registers only the connector’s Redis.Iris.AgentMemory activity source and meter, then exports both signals to the Collector using OTLP/gRPC.

The Collector routes traces to Jaeger and exposes translated Prometheus series on port 8889; Prometheus scrapes that endpoint and backs the provisioned Grafana dashboard. Application logs are not exported. This intentionally avoids capturing prompt text, memory content, user/session identifiers, or HTTP paths through broad automatic instrumentation.