Set up the Splunk Observability Cloud organization

Reference information for preparing the destination Splunk Observability Cloud organization for migration.

Set up the organization

Prepare the destination Splunk Observability Cloud organization for the applications in the migration wave. Prepare the organization and realm before you validate network connectivity or create access tokens.

Complete the following tasks with your Splunk representative and Splunk Observability Cloud administrator.

Task Action

Verify the destination organization

Confirm your sign-in to the approved Splunk Observability Cloud organization. Verify its name and realm against the Phase 1 migration plan before making configuration changes.

Confirm the realm

Follow View your realm, API endpoints, and organization to find your organization’s realm and realm-specific endpoints. Verify that the realm matches the approved data-residency requirements, and record the realm and endpoints in the migration plan. See Splunk Observability Cloud service description for realm-to-region mapping.

Review data retention

Review Data retention in Splunk Observability Cloud. Confirm that the retention periods for the APM data types in scope meet your operational and compliance requirements. Record any unmet requirement and assign an owner to resolve it before migration.

Assign administrators

Ensure that at least one designated administrator can access the organization and perform the required Phase 2 configuration.

Define the team structure

Create or identify teams that align with application ownership and the approved environment-segmentation model. Assign the appropriate users to each team.

Record the organization details

Record the following information in the migration plan:

  • Organization name
  • Realm
  • Organization administrators
  • Teams and application owners
  • Environment-segmentation approach
  • Data-retention requirements and any identified gaps
  • Unresolved user-access issues and their assigned owners
Note:

Do not include access-token values in the migration plan, tickets, reports, or screenshots.

Confirm readiness

Confirm that:

  • [ ] You provisioned and can access the destination organization.
  • [ ] The organization and realm meet the approved data-residency requirements.
  • [ ] You recorded the organization name and realm in the migration plan.
  • [ ] The required administrators can access the organization.
  • [ ] You defined the team and application-ownership structure.
  • [ ] You reviewed applicable telemetry-retention entitlements.
  • [ ] You assigned an owner and a resolution plan to any unresolved issues.

After completing these checks, continue to Validate Network Connectivity.