There will be planned maintenance for Splunk Synthetic Monitoring as specified below: Realm Splunk Synthetic Monitoring Planned Maintenance Window app.jp0.signalfx.com February 15, 2024 from 9.00 am PST to 11.00 am PST (GMT-7) [link to status page] app.au0.signalfx.com February 20, 2024 from 8.00 am to 10.00 am PT (GMT-7) [link to status page] app.eu0.signalfx.com February 21, 2024 from Noon to 2.00 pm PT (GMT-7) [link to status page] app.us0.signalfx.com February 22, 2024 from 7.00 am to 9.00 am PT (GMT-7) [link to status page] app.us1.signalfx.com February 23, 2024 from 7.00 am to 9.00 am PT (GMT-7) [link to status page] app.us2.signalfx.com Not Applicable / No impact During this maintenance window, the user interface of Splunk Synthetic Monitoring will not be available, and some tests may be paused momentarily. You can find which realm / region you’re using by following the steps below: In the Observability Cloud main menu, select Settings. Select your user name at the top of the Settings menu. On the Organizations tab, you can view or copy your realm, organizations and organization IDs. Please note that the planned maintenance activity only applies to Splunk Synthetic Monitoring. Other products or features of Splunk Observability Cloud, Rigor Synthetic Monitoring and Web Optimization will not be impacted by this maintenance window. For any questions, please reach out on the Splunk Support Portal to create a Support case (select Get Started > Create a Case > Support > Splunk Synthetic Monitoring). ... View more

On July 23rd, 2023, we experienced an internal issue that affected timing metrics of Browser and API checks for a limited number of customers in the Splunk Synthetic Monitoring platform. This issue is now fully resolved and Splunk has taken additional steps to prevent any future occurrences.  Timing metrics such as synthetics.run.duration.time.ms, synthetics.dns.time.ms, synthetics.dom_complete.time.ms populated by Browser and API tests may show a lower than expected value. Charts, reports and detectors associated with these metrics may have also been impacted. We understand the inconvenience this may have caused and would like to extend our most sincere apologies. To help mitigate this disruption, we are able to provide you with a detailed list of the tests impacted to assess any problems and our customer support team is prepared to help you with any questions.  For Browser Tests, all metrics ending with *time.ms were impacted (approximately 25 metrics).  For API Tests, all metrics with the extension *time.ms were impacted (approximately 7 metrics).  Note: This did not impact the Splunk Rigor platform and therefore did not impact checks configured there.  For any questions, please reach out on the Splunk Support Portal to create a Support case (select Get Started. > Create a Case > Select Support > Select Splunk Synthetics). ... View more