Phase 2: prepare Splunk Observability Cloud

Prerequisites

Before you begin Phase 2, confirm that:

• [ ] Phase 1 is complete, and the scope, application inventory, and migration wave are approved.
• [ ] The Splunk Observability Cloud entitlement is active and the destination organization is provisioned.
• [ ] Data-residency and telemetry-retention requirements are documented.
• [ ] Splunk Observability Cloud administrators, network and security contacts, and token owners are assigned.
• [ ] The applications, Collectors, proxies, gateways, and network zones included in the migration wave are identified.
• [ ] The owner and process for requesting firewall or proxy changes are identified.
• [ ] An approved secret manager is available for storing access-token values.

Complete the phase 2 tasks

Complete the following tasks in order:

• Set up the Splunk Observability Cloud Organization: Verify the destination organization, realm, administrators, teams, environment segmentation, and data-retention requirements.
• Validate network connectivity: Confirm that every required network zone can reach its approved realm-specific endpoints through the applicable firewall, proxy, and gateway paths.
• Create access token: Create and securely store the Ingest tokens required for telemetry and any API token required for Migration Tool operations.
• Send and verify a test metric: Send a test metric from each required telemetry path and verify that it appears in the intended destination organization.

Sending a test metric validates the network path, ingest endpoint, and Ingest token. It does not validate an API token. If the migration wave requires a Migration Tool destination connection, use the destination connection test on the Configure Connections page to validate the API token and its permissions.

Confirm readiness

Confirm that:

• [ ] The destination organization and realm are verified and recorded.
• [ ] Administrator access, team ownership, environment segmentation, and data-retention requirements are reviewed.
• [ ] Every required network path has passed DNS, TLS, firewall, proxy, and endpoint-connectivity checks.
• [ ] Required firewall or proxy changes are approved and implemented.
• [ ] Each access token has the correct scope, an assigned owner, an expiration and rotation plan, and approved storage.
• [ ] Any required API token passes Migration Tool destination connection test.
• [ ] Each required Ingest token returns HTTP status 200 when sending the test metric.
• [ ] The test metric appears in the intended organization with the expected value and dimensions.
• [ ] Test results and unresolved findings are recorded without exposing token values.
• [ ] No blocking organization, network, access-token, or ingestion issue remains.

After completing these checks, continue to Phase 3.