X-Ray
Status: Unavailable for supported deployment: backend capability only, with no dedicated Operator CRD or supported dashboard catalog entry.
:::caution No supported deployment contract
This capability is documented for catalog completeness, but the selected release does not publish a supported end-to-end deployment contract.
:::
Always confirm availability in the release bundle selected for deployment.
At a glance
| Property | Value |
|---|---|
| Pipeline phase | Request + response |
| Category | Observability |
| Canonical minimum tier | Free |
| Canonical entitlement | Yes |
| Supported deployment contract | No |
| Release status | Unavailable for supported deployment: backend capability only, with no dedicated Operator CRD or supported dashboard catalog entry. |
Release accuracy
- Current documentation: Unavailable for supported deployment: backend capability only, with no dedicated Operator CRD or supported dashboard catalog entry.
Where any detail below conflicts with the release status above, the release status is authoritative. Field names and examples describe the current dashboard and CRD surface; always confirm behavior against the selected release bundle before relying on it operationally.
Release-aware feature flow. The diagram is explanatory; the release status on this page is authoritative.
Diagram resources: Open the SVG full screen · Download the editable Excalidraw source
Performance impact
No performance data is published for this component.
Overview
Passively sample traffic to identify repeated queries, slow operations, burst clients, read/write mix, possible PII, and optimization opportunities. This backend-only capability samples and fingerprints traffic for workload analysis. It has no corresponding built-in dashboard catalog entry.
When to use
- Explore workload composition
- Find repeated or slow query fingerprints
- Identify burst patterns and possible sensitive fields
How it works
- Does not modify requests or responses
- Samples and fingerprints traffic
- Aggregates observations into periodic insights
Configuration
“Not specified” means required semantics were not declared for that field.
| Field | Type | Default | Required | Description |
|---|---|---|---|---|
sample_rate | unspecified | — | No | Sample rate |
analysis_window | unspecified | — | No | Analysis window |
slow_query_threshold | unspecified | — | No | Slow-query threshold |
burst_threshold | unspecified | — | No | Burst threshold |
fingerprint_limit | unspecified | — | No | Fingerprint limit |
custom_pii_patterns | unspecified | — | No | Custom PII patterns |
Settings reference
No additional settings reference is documented for this component.
Examples
No example is documented for this component.
Best practices
- Do not attempt to deploy it through a borrowed CRD mapping
- Treat detected field names and query fingerprints as sensitive telemetry
- Wait for a bundle with a dedicated deployment contract
Limitations
- No dedicated Operator CRD or supported deployment contract is published.
Security and operational guidance
- Do not attempt to deploy it through a borrowed CRD mapping
- Treat detected field names and query fingerprints as sensitive telemetry
- Wait for a bundle with a dedicated deployment contract
Related steps
Release availability
- Current documentation: Unavailable for supported deployment: backend capability only, with no dedicated Operator CRD or supported dashboard catalog entry.
See the component catalog for the complete comparison matrix.