Introduce a flexible activation delay or scheduled start time for Synthetic Tests,fully supported via UI, API, and the Terraform provider,to prevent premature alerting during long-term system onboarding and manual configuration phases.

Why is it useful?

When onboarding new systems or environments via Infrastructure as Code (IaC), Synthetic Tests are typically provisioned at the very beginning of the lifecycle. However, a system is rarely "live" the exact moment its infrastructure is created.

Depending on the project, the gap between infrastructure creation and going live can range from a few minutes (for automated container deployments) to several days or weeks (where development teams must first perform manual configurations, data migration, or compliance checks).

Without a built-in activation offset, these tests immediately fail and trigger false alarms, causing severe alert fatigue in incident management platforms like PagerDuty. Currently, teams must either build complex, brittle CI/CD workflows to deploy tests at a later date, or manually disable/enable tests in the UI, which defeats the purpose of GitOps and IaC.

Who would benefit from it?

Platform & DevOps Engineers: They can write a single, clean Terraform configuration that provisions both the infrastructure and its monitoring upfront, without needing external orchestrators to delay test creation.

Development & Implementation Teams: They gain a "grace period" to manually configure and test the application without worrying about triggering global alerts.

SREs & On-Call Shiftheads: They eliminate deployment-related noise and false pages entirely.

How should it work?

When creating a Synthetic Test, users should be able to define a flexible delay or a future activation date.

Flexible Input: The system should accept either a duration string (e.g., 15m, 2h, 7d) or a specific timestamp (ISO 8601).

State Management: Upon creation, the test enters a "Pending Activation" state. During this window, the test does not execute, and no alerts are evaluated.

Automatic Transition: Once the specified time or duration has elapsed, Instana automatically transitions the test to the Active state.