Splunk 可观察性 AI 助手
Outage严重事件
受影响的组件
AI Assistant
- investigating
我们正在调查斯普伦克观测助理的一次重大故障.
- identified
这个问题已被确定为Azure OpenAI停用,我们正在绕道开展工作.
- monitoring
一项措施已经执行,我们正在监测结果.
- resolved
监测阶段完成。 这个问题已经得到解决.
自动翻译自官方事件更新。
61 Signalfx Us1 incidents · 2025年5月 — official updates, affected components, duration and resolution details.
我们正在调查斯普伦克观测助理的一次重大故障.
这个问题已被确定为Azure OpenAI停用,我们正在绕道开展工作.
一项措施已经执行,我们正在监测结果.
监测阶段完成。 这个问题已经得到解决.
自动翻译自官方事件更新。
从08/25/2026起,11:38AM PDT,斯普伦克APM微量处理管的性能退化,正导致"问题解决"(Reasonshuting MetricSets)延迟了5分多. 因此,APM解决问题的经验,服务地图和Tag Spotlight无法访问最新数据. 商业工作流量的计量标准也取决于这一管道的处理同样被拖延。 跟踪数据摄入量目前没有受到影响;服务级和端点级监测计量仪及其制造的探测器也没有受到影响.
我们正在继续调查这一问题.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
我们的小组继续监测局势,以确保充分补救.
这一事件已经得到解决.
自动翻译自官方事件更新。
处理警报的问题导致通知延迟。 我们目前正在调查这一问题.
我们目前正在调查上升的通知延迟。 客户在接到警报通知时可能会遇到延误。 我们正在积极努力解决这一问题,并将在我们取得进展时提供最新情况。 我们感谢你的耐心.
我们已经确定并正在积极解决造成延迟警报的问题。 该固定办法已经实施,而且通知交付时间已经显著改善。 虽然有些通知在定案前排队,但随着系统赶上来,仍然可能遇到一些小的延误,但新的通知通常都在发出。 我们赞赏你的耐心,并将继续密切监测局势.
我们正在积极努力解决这一问题。 客户在通知交付方面可能继续出现延误。 这包括新生成的通知,这些通知正在排队中较早的事件后面处理。 小组正在积极调查根源,并努力清理积压的排队通知。 作为暂时的缓解措施,我们在通知中取消了图像预览,以提高处理速度. 通知目前仅限文本。 我们赞赏你的耐心,并将随着进展提供进一步的最新情况.
我们已经执行了一项解决通知延误问题的措施。 我们的监测显示,通知交付时间大有改善,我们正在密切跟踪执行情况,以确保这一问题得到全面解决。 感谢你们耐心地努力恢复全面服务.
通知交付的拖延已完全得到解决。 所有已排队的通知均已处理完毕,该系统现已正常运行.
自动翻译自官方事件更新。
Sprunk APM 度量衡处理管道的性能下降导致Monitory MetricSets延迟了5分钟以上. 跟踪数据摄入量没有受到影响,但服务、端点和工作流程仪表板以及Monitor MetricSets所建的其他图表和探测器受到影响.
我们正在继续调查这个问题。
我们正在继续调查这一问题.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
新的或重新启动的公制时间序列的数据点摄入量在2:28 PM PST到2:47 PM PST之间受到影响. 在此期间,新的计量时间序列出现了部分数据损失。 这种状况现已得到恢复.
自动翻译自官方事件更新。
10:37 AM PST到10:39 AM PST之间,新公制时间序列的数据摄入点受到影响. 在此期间,新的计量时间序列出现了部分数据损失。 这种状况现已得到恢复.
自动翻译自官方事件更新。
从4a PT开始,我们正在调查斯普伦克可观察性云网络应用的重大故障. 数据摄入量目前没有受到影响。 我们将尽快提供最新情况.
我们正在继续调查这个问题。
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决。 请注意,斯普伦克可观测云API也在这一事件中受到影响.
自动翻译自官方事件更新。
1a PDT至2:50a PDT之间,任何具有"全部(动态)上市项目"设置的GCP集成,都有部分来自GCP的云监测数据被放弃. 这个问题已经得到解决。 客户可能会看到使用受影响全球氯化石蜡云监测测量仪的图表和探测器存在漏洞。 AWS Cloud Watch和Azure Monitor的度量衡没有受到影响.
自动翻译自官方事件更新。
客户在看到新创建的计量时间序列时可能遇到延误。 对于现有的时间序列,数据点摄入不受影响. 我们正在调查,不久将提供最新情况.
造成新设定的衡量时间序列延误的问题已经解决。 Metric时间序列创建正常运行. 现有时间序列的数据点摄入量没有受到影响.
自动翻译自官方事件更新。
我们确认,影响Tag Spotlight的问题已经得到解决。 从6月30日4:30 PM PT开始,客户在Tag Spotlight内部的功能可能有限. 全功能于7月1日7:20AM PT恢复.
自动翻译自官方事件更新。
由于最近一期的回放,用户从APM TraceView页面上的日志相关内容浏览到Log Observation,转回APM TraceView. 这影响了除美国3号和政府外所有领域的客户的日志关联经验。 这一变化已经恢复,以恢复预期的导航经验。 APM和Log Observer的产品可得性没有受到影响;这个问题仅限于TraceView的Logs相关工作流程。 事发时间:05:09 PDT,2026年6月25日 事件结束时间:22:15 PDT,2026年6月25日
自动翻译自官方事件更新。
Rum API Endpoints were not available for one of our IPs, resulting in degraded service or a partial outage at first, and possibly a complete outage towards the end. This issue occurred from 4:22pm PST to 4:57pm PST
Datapoint ingest is affected , some datapoints could be dropped. Team is investigating and will provide an update shortly.
Our engineering team is currently implementing an impact mitigation configuration change. The internal investigation is still ongoing. We will share an additional update as soon as possible.
Our engineering team has completed impact mitigating configuration changes and confirmed services are recovered as of 4:55 PDT. We will continue monitoring and share an update as soon as possible.
Our engineering team has confirmed that all the services recovered as of 4:55 PM PDT and remained stable during monitoring. This incident is now resolved.
We are investigating delays in processing Splunk Observability Synthetic Monitoring test results for a small subset of customers. Tests are still running, but metrics may be delayed until the issue is resolved.
We have identified and remediated an issue affecting synthetic test result ingestion for a subset of customers. We apologize for any inconvenience this may have caused and thank you for your patience. Time range of impact: June 1 20:00 UTC - June 2 15:30 UTC
Charts for customers may not be loading. App and UI availability is also impacted. We are investigating and will provide an update shortly.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the status.
This Incident has been resolved.
A degradation of the Splunk O11y Cloud ingest path is causing ~20% of AWS CloudWatch metrics to be dropped. We are investigating the issue and will provide an update as soon as possible.
This incident has been resolved. We have since confirmed that only AWS CloudWatch metrics were impacted during this incident. Azure and GCP metrics were not impacted.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Charts for all customers may not be loading. Datapoint ingest is not affected. We are investigating and will provide an update shortly.
Our teams continue working to identify the cause and implement a fix.
Our investigation remains ongoing, and there is no change in status at this time. We are continuing to prioritize this issue and will provide the next update in thirty minutes.
Our teams are continuing their efforts to identify the root cause of this issue. There is no change in status to report at this time, but we are dedicating all necessary resources to reach a resolution. We will provide another update shortly.
Update (8:50 AM PST): We have observed that charts are now loading successfully. While service is recovering, our teams remain on-site to investigate the root cause and ensure full system stability. We will continue to monitor performance closely.
We are continuing to monitor the environment. There is no change in status at this time; our teams remain focused on resolving the remaining isolated issues.
Our teams are continuing to monitor the environment and are actively working to fully resolve the issue.
Update 10:30 PST: We are also investigating reports of login issues. Users may experience difficulty authenticating or accessing their accounts at this time.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor the environment to ensure full remediation.
This incident has been resolved.
We are investigating an issue affecting Real User Monitoring (RUM) metrics across all realms. Customers may experience custom metric MTS quota limits being exceeded, resulting in metric data being dropped. RUM metric dimensions that were previously available may be missing.
The issue affecting Real User Monitoring (RUM) metrics has been identified. The fix is currently being implemented. We are actively working to restore full service and will provide further updates as progress continues.
We are continuing to work on the fix. We expect to have further updates within the next hour. We appreciate your patience as we work diligently to resolve this issue and restore full service.
We are currently continuing to test the fix for the Real User Monitoring (RUM) metrics issue. We are thoroughly validating the mitigation to ensure it resolves the issue effectively and maintains system stability. We appreciate your ongoing patience and will provide further updates as testing progresses.
We are currently continuing to test the fix for the Real User Monitoring (RUM) metrics issue. We will share an update once we have further information.
The outage impacting RUM MMS Data Drop has been resolved after internal engineering teams deployed a fix. All systems are operational and stable. Thank you for your patience and understanding.
We are currently investigating an issue where RUM (Real User Monitoring) MMS data is being dropped, which may result in missing or incomplete data in charts and dashboards related to real user monitoring. We are actively investigating and will provide updates as the situation develops.
We have identified the cause of the issue resulting in missing or incomplete data in Real User Monitoring charts and dashboards. We are implementing a fix and will provide an update within 15 minutes.
A solution to address the issue causing missing or incomplete data in Real User Monitoring (RUM) charts and dashboards is currently being implemented. Our teams are actively working on deploying the fix and will continue to provide updates as progress is made
We have identified an issue causing missing or incomplete data in Real User Monitoring (RUM) custom charts and dashboards across multiple realms. A fix is currently being rolled out and validated
A fix for the issue affecting Real User Monitoring (RUM) charts and dashboards has been deployed and is being actively monitored across all realms; customers may now see data restored in charts and dashboards
The issue affecting Real User Monitoring (RUM) custom charts and dashboards across multiple realms has been resolved. The fix has been deployed, and data is now flowing normally.