Skip to main content
Lantern Home

 

Splunk Lantern

Rigor to Splunk Synthetics Migration - Customer FAQ

  1. Last updated
  2. Save as PDF

Splunk sunset the legacy Rigor platform as of February 28, 2025, and replaced it with Splunk Synthetic Monitoring which offers a similar synthetic testing experience within Splunk Observability Cloud. Splunk Synthetic Monitoring offers a higher level of product experience with a platform that complies with General Data Protection Regulation (GDPR) and Service Organization Control Type 2 (SOC 2), centralizes all data and reports in one place, and provides higher service level agreements (SLAs).

General information

  1. What happened to Rigor and Splunk Synthetic Monitoring?
    The Rigor platform (Rigor and Web Optimization) became End-of-Life (EOL) on February 28, 2025. It ceased to exist on that date. As a result, Splunk migrated Rigor customers to Splunk Synthetic Monitoring within Splunk Observability Cloud, so users can keep enjoying the same digital monitoring functionality and experience.
     
  2. Why did Splunk do this?
    Rigor was created to offer a synthetic testing experience for ITOps, engineers, and front-end developers to test the uptime and performance of their websites and endpoints. Splunk consolidated efforts to offer the same functionality in Splunk Observability Cloud as Splunk Synthetic Monitoring. This lets Splunk provide its customers with a single integrated and superior digital experience monitoring product alongside powerful capabilities from Splunk Application Performance Monitoring, Splunk Real User Monitoring, Splunk Infrastructure Monitoring, and Splunk Log Observer Connect.
     
  3. What does End-of-Life mean?
    End of Life means that the Rigor platform ended its product life cycle and is no longer available. Support on Rigor was available until its official EOL on February 28, 2025.
     
  4. What happened if I continued to stay on the Rigor platform?
    Rigor was in maintenance mode until February 28, 2025. After that date, if you did not to migrate to Splunk Synthetic Monitoring at the time of your license renewal, you lost all access to Rigor monitoring services.
     
  5. What are the advantages of migrating to Splunk Synthetic Monitoring?
    Splunk Synthetic Monitoring lets IT and engineering teams proactively detect issues that affect web and API performance and end-user experience. It also lets them troubleshoot and remedy issues in the web browser, the server, or a third-party dependency — all within a single user interface.

    With Splunk Synthetic Monitoring, you can centralize all your data and reports in the Splunk Observability Cloud platform for easier dashboarding and monitoring. You also get access to a platform compliant with GDPR and SOC 2 so you have better data protection, risk mitigation, and customer trust, and which provides higher SLAs. Finally, Splunk Synthetic Monitoring offers a highly similar product offering to Rigor, including close feature parity. See details later in this FAQ. Find out more about Splunk Synthetic Monitoring here.
     
  6. Can I still get customer support for Rigor?
    You can no longer receive customer support.

Product/Technical

  1. Are there any key differences between Splunk Synthetic Monitoring and Rigor?
    Splunk worked hard to ensure full feature parity between Rigor and Splunk Synthetic Monitoring. See the following table:
    Rigor Features Available on Splunk Synthetic Monitoring
    Notifications Yes
    Connection speeds Yes
    Private locations Yes
    Wait for full metrics Yes
    CRUD API endpoints for all UI functionalities Yes
    Rigor metrics Yes
    Custom wait times Yes
    Response time monitor Yes, can be created via Splunk detectors
    Threshold monitors Yes, can be created via Splunk detectors
    Fill in text fields with password obfuscation Yes
    Browser tests Yes
    API tests Yes
    Uptime tests Yes
    Try Now - including screenshots Yes
    Global variables Yes
    Tags Available as custom properties
    Auto-retry Yes

    Some Rigor features are not part of Splunk Synthetic Monitoring, namely:

    • SMS notifications
    • Reports
    • Benchmark tests
    • Content checks
    • Status pages
    • Web optimization
       
  2. Is Splunk Synthetic Monitoring available across every cloud service provider region?
    Today, Splunk Synthetic Monitoring is available in the following regions:
    • AWS - US West Oregon
    • AWS - US East Virginia
    • AWS - AP Sydney
    • AWS - EU Dublin
    • AWS - AP Tokyo
    • GCP US Oregon (us-west-1)

  3. Are the data retention policies the same between Rigor and Splunk Observability Cloud?
    Splunk Synthetic Monitoring provides 13 months data retention for metric data.

  4. Does Splunk Synthetic Monitoring have an official documentation page?
    Yes, you can find all the product and configuration details here.
     
  5. What is Splunk Observability Cloud?
    Splunk Observability Cloud is our full-stack, analytics-powered, and OpenTelemetry-native observability solution that lets you monitor the performance of your systems and troubleshoot across your technology stack. The platform includes Splunk Application Performance Monitoring, Splunk Infrastructure Monitoring, and Splunk Real User Monitoring. Learn more about Splunk observability solutions here.

Splunk did not move any historical data from Rigor platform to Splunk Synthetic Monitoring. You were required to create a copy of your data using the Rigor APIs prior to the EOL. The Rigor platform was available in read-only mode for 90 days after your migration to Splunk Synthetic Monitoring, which provides access to historic data before the account is deactivated.

Support

  1. I would like to suggest some product and feature improvements for Splunk Synthetic Monitoring to the product team. Where can I do that?
    We love to get your feedback and hear your thoughts on our products. You can submit your ideas on Splunk Ideas.
      
  2. I have a question that wasn’t answered in this FAQ. Who should I contact?
    Contact your account manager/sales executive or Splunk Support if you do not have a Splunk representative assigned to your account. More details can be found on working with Splunk Support here.