Service level agreements
Listed terms cover requests sent through this service adapter. They do not cover direct connections to the target service or replace the cloud provider’s own SLA. Each origin-to-target pair has its own terms or an explicit pending status. See the SLA tables, measurement rules, and scaling conditions.Secret Manager to Secrets Manager
Deployment availability. These targets describe this adapter design. Confirm that your deployment supports the listed operations; a numerical target does not establish runtime availability.
What Tensor9 covers. These service levels cover the adapter between the origin API and target API. They do not replace the target provider’s SLA.
How latency is counted. Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded.
Which terms apply. Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.
What this adapter does
Foraws::1.0.0::secretsmanager, secret identity, version creation/access and destruction are translated to the target’s lifecycle. Deletion semantics differ: disabling or scheduling deletion of a native version is not necessarily immediate physical erasure. The latency target covers correct request handling, not a promise to accelerate the provider’s deletion or replication schedule. These targets describe this adapter design; confirm that your deployment supports the listed operations. A numerical target does not establish runtime availability.
How the latency targets were chosen
Bounded secret-version access: 1 ms monthly p99.secretmanager.projects.secrets.versions.access. Resolve the version identity, map native access and encode the bounded response. Adapter-owned metadata or authorization work is not excluded.
Secret and version changes: 20 ms monthly p99. secretmanager.projects.secrets.addVersion, secretmanager.projects.secrets.create, secretmanager.projects.secrets.delete, secretmanager.projects.secrets.versions.destroy. Bounded configuration validation, durable adapter metadata and response encoding; native provisioning completion and propagation are separate.
Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.
What counts toward latency
For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter’s own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it. For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request’s adapter duration first, then the monthly p99. Do not subtract one service’s p99 from another’s. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.Availability and failures
The 99.9% request target measures correct adapter handling, not the percentage of application calls that return success. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures count even when the target is healthy. With 1,000,000 eligible calls in a month, a 99.9% target permits at most 1,000 adapter-attributable failures. Endpoint probes have their own denominator. Correctness defects remain actionable even when the monthly availability percentage is met.Scaling and target-service capacity
Track payload bytes, version access, cache misses and version creation separately. Rotation bursts can increase target calls and adapter metadata work. Tensor9 scales the adapter inside agreed payload, concurrency and churn limits; the customer supplies target permissions, quotas and rotation policy. A cache must not violate the selected version’s correctness to satisfy latency. Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service’s capacity with Tensor9’s help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.Data and behavior guarantees
Return the intended version’s bytes without silently substituting a newer or older secret. Preserve supported access denial and deletion state, and report native lifecycle limitations. Never include secret values in Explain evidence or support tickets. Provider storage durability and multi-region replication remain separate from the adapter request guarantee.Example and diagnosis
Read version7 of database-password, then add version 8 as part of rotation. Access and lifecycle use different rows. If clients still explicitly request version7, returning8 to make rotation appear complete is an adapter correctness defect even if both responses meet the latency target.
Use tensor9 explain and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider’s latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.
Secret Manager to Key Vault
Deployment availability. These targets describe this adapter design. Confirm that your deployment supports the listed operations; a numerical target does not establish runtime availability.
What Tensor9 covers. These service levels cover the adapter between the origin API and target API. They do not replace the target provider’s SLA.
How latency is counted. Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded.
Which terms apply. Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.
What this adapter does
Forazure::1.0.0::keyvault, secret identity, version creation/access and destruction are translated to the target’s lifecycle. Deletion semantics differ: disabling or scheduling deletion of a native version is not necessarily immediate physical erasure. The latency target covers correct request handling, not a promise to accelerate the provider’s deletion or replication schedule. These targets describe this adapter design; confirm that your deployment supports the listed operations. A numerical target does not establish runtime availability.
How the latency targets were chosen
Bounded secret-version access: 1 ms monthly p99.secretmanager.projects.secrets.versions.access. Resolve the version identity, map native access and encode the bounded response. Adapter-owned metadata or authorization work is not excluded.
Secret and version changes: 20 ms monthly p99. secretmanager.projects.secrets.addVersion, secretmanager.projects.secrets.create, secretmanager.projects.secrets.delete, secretmanager.projects.secrets.versions.destroy. Bounded configuration validation, durable adapter metadata and response encoding; native provisioning completion and propagation are separate.
Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.
What counts toward latency
For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter’s own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it. For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request’s adapter duration first, then the monthly p99. Do not subtract one service’s p99 from another’s. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.Availability and failures
The 99.9% request target measures correct adapter handling, not the percentage of application calls that return success. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures count even when the target is healthy. With 1,000,000 eligible calls in a month, a 99.9% target permits at most 1,000 adapter-attributable failures. Endpoint probes have their own denominator. Correctness defects remain actionable even when the monthly availability percentage is met.Scaling and target-service capacity
Track payload bytes, version access, cache misses and version creation separately. Rotation bursts can increase target calls and adapter metadata work. Tensor9 scales the adapter inside agreed payload, concurrency and churn limits; the customer supplies target permissions, quotas and rotation policy. A cache must not violate the selected version’s correctness to satisfy latency. Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service’s capacity with Tensor9’s help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.Data and behavior guarantees
Return the intended version’s bytes without silently substituting a newer or older secret. Preserve supported access denial and deletion state, and report native lifecycle limitations. Never include secret values in Explain evidence or support tickets. Provider storage durability and multi-region replication remain separate from the adapter request guarantee.Example and diagnosis
Read version7 of database-password, then add version 8 as part of rotation. Access and lifecycle use different rows. If clients still explicitly request version7, returning8 to make rotation appear complete is an adapter correctness defect even if both responses meet the latency target.
Use tensor9 explain and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider’s latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.