FinOps documentation.

Connect your Dynatrace tenant

Getting started · ~5 minutes

1. Generate a read-only API token
In your Dynatrace environment, create a new API token scoped to read-only access. FinOps never requests write scopes — if a setup screen asks for anything beyond read access, that's not FinOps.

2. Enter your tenant URL and token
From your DynaLens account, add a new tenant connection and paste in your Dynatrace environment URL and the token generated in step 1.

3. Wait for the first sync
FinOps pulls DPS consumption history for your tenant. Initial sync typically completes within a few minutes, depending on estate size.

Managing multiple tenants — as a platform team or a partner? Repeat the same steps for each tenant; every tenant you connect appears in the same account, with its own isolated attribution and forecasting.

First login

What you'll see

Once your tenant syncs, the FinOps dashboard opens on the cost overview: current DPS consumption, forecast against your annual commitment, and savings already identified. From there, the Attribution tab breaks spend down by capability and environment, and Recommendations lists one-click Fix actions ranked by savings impact.

Cost attribution

Core concept

FinOps attributes DPS consumption continuously, by capability, account, and environment, so every line item has an owner. Attribution covers every metered DPS capability — Full-Stack, Infrastructure, Kubernetes, RUM, Synthetic, Log Management, Application Security, Business Events, and Davis AI — not a subset.

Attribution updates as consumption happens; there's no batch delay waiting for the next invoice cycle to see where spend is heading.

Forecasting & budget alerts

Core concept

FinOps uses Monte Carlo forecasting to project spend against your annual commitment, with confidence bands rather than a single point estimate — so you see a realistic range, not false precision.

Budget alerts fire automatically the moment a forecast crosses 25%, 50%, 75%, or 90% of budget, and FinOps surfaces a predicted exhaustion date whenever you're on track to run out of commitment early. A weekly digest summarizes position across every tenant you operate.

One-click Fix

Core concept

Recommendations aren't just advisory — each one includes a Fix action that applies the change directly back into your live Dynatrace tenant (for example, adjusting a retention setting), so resolving a cost recommendation doesn't require leaving FinOps to go make the change by hand.

Every Fix action is logged, and because FinOps only ever holds read-only tenant access for monitoring, Fix actions operate through the same scoped, auditable path — nothing happens in your environment without a specific, visible action on your part.

DPS capability coverage

Reference

One-click Fix availability depends on the capability having a directly configurable retention/sampling setting; coverage expands as new Fix actions ship.

Deployment & security

Reference

• Read-only, always — FinOps never writes to your Dynatrace environment outside of an explicit, logged Fix action you initiate.
• Tenant isolation — One Keycloak realm per customer; schema-level data separation in PostgreSQL.
• SaaS or on-premises — Fully managed SaaS, or air-gapped on-premises deployment with full feature parity.
• Classic or DPS licensing — Works across Dynatrace SaaS and Managed, Classic and DPS consumption models.

For a walkthrough of the architecture for your environment, get in touch.

FAQ

Does FinOps require a specific Dynatrace licensing model?
FinOps works with both Classic and DPS consumption licensing, and with SaaS or Managed deployments.

Can I connect more than one Dynatrace tenant?
Yes — FinOps is built for both single-estate platform teams and partners managing many customer tenants from one account.

What happens if I revoke the API token?
FinOps immediately loses access to that tenant. Historical attribution and forecasting data already synced remains available in your account; consumption stops updating until a new token is provided.

Does a Fix action require approval, or does it apply automatically?
Fix actions are applied only when you explicitly trigger them — recommendations are advisory until you choose to act on one.

Changelog

Changelog will populate here as FinOps releases ship. Check back after the next release.