Migrate from legacy signalfx.com to observability.splunkcloud.com

Available Languages

Updated:October 1, 2026
Document ID:SPLK053860

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Infrastructure Monitoring Splunk Application Monitoring Splunk Synthetics Monitoring Splunk Real User Monitoring

Description

Following the integration of SignalFx into Splunk Observability Cloud, the platform has undergone domain consolidation and rebranding. The new observability.splunkcloud.com domain is now the primary endpoint for Splunk Observability Cloud services. However, existing implementations using the legacy signalfx.com domain continue to function.

Organizations may encounter the following scenarios:

  • Uncertainty about mandatory migration timelines
  • Questions regarding endpoint compatibility and coexistence
  • Need to plan integration updates for systems currently using signalfx.com endpoints
  • Concerns about service disruption during migration

This article provides clarity on the current state of both domains and outlines the migration options available.


Investigation

To determine if an implementation is affected by the domain transition, perform the following steps:

  1. Identify all domains currently in use by reviewing configuration files and integration scripts.

  2. Search for references to signalfx.com in the following locations:

    • Application configuration files
    • Integration setup scripts
    • Monitoring dashboards and alerts
    • API authentication endpoints
    • Data ingestion pipelines

  3. Verify the current domain in use by examining API requests. Check logs or network traffic for endpoint URLs containing either:

    • signalfx.com (legacy domain)
    • observability.splunkcloud.com (new domain)

  4. Document the scope of systems and integrations currently pointing to the legacy signalfx.com domain to assess migration effort.


Resolution

The following information clarifies the current state and migration options:

Current Status:

  • Both signalfx.com and observability.splunkcloud.com domains are currently active and operational
  • Existing implementations using signalfx.com endpoints will continue to function without disruption
  • No mandatory immediate migration is required

Next Steps:

There are no immediate actions required

Future updates will be communicated through email notifications and updates on this documentation page. If specific actions become necessary, they will be announced in advance.

For more information and official documentation: Splunk Observability Cloud domain change

 

 


Splunk Observability Cloud domain change

Revision History

Revision Publish Date Comments
1.0
01-Oct-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products

Related Articles