Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions docs/cloud/features/incident_reporting.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# Incident Reporting

## Overview

Tobiko Cloud has 24/7 monitoring and alerting in place to ensure the platform is running smoothly.
However, if you encounter any issues, you can report incidents directly through the platform.
This will immediately notify our support team, who will investigate and resolve the issue as quickly as possible.

### Reporting an incident using SSO

To report an incident using your Single Sign-On (SSO) account, follow these steps:

* Visit [Tobiko Cloud Incident Reporting Page](https://incidents.tobikodata.com/).
* You will see your organization's name in the top right corner, indicating that you are logged in with your SSO account.
* Select a severity level for your incident
* Put in the project name that the incident is related to
* The project name is the name after your organization name in the Cloud UI.
* Write a detailed description of the incident
* Include any relevant information that can help our support team understand and resolve the issue.
* Click the "Submit" button to send your incident report.
* You will receive a confirmation message indicating that your incident has been reported successfully.
* You should hear from our support team shortly after submitting the incident report.

### Getting URL that doesn't require SSO

Although in most cases SSO is the preferred way to report incidents, it is possible that SSO could be down or not working for some reason.
To prepare for this situation, you can get a URL that doesn't require SSO by following these steps:

* Visit [Tobiko Cloud Incident Reporting Page](https://incidents.tobikodata.com/).
* Click the "Copy Standalone URL" button below the report incident part of the page.
* Save this URL within your organization so that anyone can use it in case SSO is not working.

### If you don't have SSO enabled for your organization

Contact your solution architect and ask them to provide you with a URL that doesn't require SSO.
1 change: 1 addition & 0 deletions mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -125,6 +125,7 @@ nav:
- cloud/features/scheduler/dagster.md
- Security:
- "Security Overview": cloud/features/security/security.md
- "Incident Reporting": cloud/features/incident_reporting.md
# - Observability:
# - cloud/features/observability/overview.md
# - cloud/features/observability/model_freshness.md
Expand Down