false

Splunk On-Call Maintenance Policy

Updated: March 2024

GENERAL

In order to operate in an efficient and secure manner and also deliver the latest features to our customers and users, Splunk On-Call has the following classes of maintenance-related activities:

  • Continuous Releases
  • Planned Maintenance
  • Emergency Maintenance

Splunk On-Call will take no more than two maintenance windows for Planned Maintenance per calendar month.

If you have any questions or concerns about upcoming or ongoing maintenance, please contact Splunk Support by opening a case on the Splunk Customer Portal.

CONTINUOUS RELEASES

Splunk On-Call performs frequent, regular service updates with no service interruptions There will be no impact on incident ingestion, login, or access to incident data during continuous releases.

PLANNED MAINTENANCE

Splunk On-Call will announce Planned Maintenance activities 14 days prior to the maintenance window. Our communications will specify any required customer actions, such as updates to data ingestion mechanisms or applications.

During Planned Maintenance, incident ingestion, login, and access to incident data may be degraded or unavailable for a short period of time within the maintenance window. Our communications will provide specifics on whether any service will be degraded or unavailable.

EMERGENCY MAINTENANCE

Emergency Maintenance is performed in circumstances that require immediate attention. We expect these Emergency Maintenance windows to be rare and by their very nature not scheduled. Splunk will announce any emergency maintenance and make commercially reasonable efforts to notify customers. Our communications will specify any required customer actions, such as updates to data ingestion mechanisms or applications.

During Emergency Maintenance, incident ingestion, login, and access to incident data may be degraded or unavailable for a short period of time within the window. Our communications will provide specifics on whether any service will be degraded or unavailable.