Skip to content

Commit 953f2a6

Browse files
committed
feat: add docs for reporting incidents in cloud
1 parent 2c1ed26 commit 953f2a6

2 files changed

Lines changed: 36 additions & 0 deletions

File tree

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
# Incident Reporting
2+
3+
## Overview
4+
5+
Tobiko Cloud has 24/7 monitoring and alerting in place to ensure the platform is running smoothly.
6+
However, if you encounter any issues, you can report incidents directly through the platform.
7+
This will immediately notify our support team, who will investigate and resolve the issue as quickly as possible.
8+
9+
### Reporting an incident using SSO
10+
11+
To report an incident using your Single Sign-On (SSO) account, follow these steps:
12+
13+
* Visit [Tobiko Cloud Incident Reporting Page](https://incidents.tobikodata.com/).
14+
* You will see your organization's name in the top right corner, indicating that you are logged in with your SSO account.
15+
* Select a severity level for your incident
16+
* Put in the project name that the incident is related to
17+
* The project name is the name after your organization name in the Cloud UI.
18+
* Write a detailed description of the incident
19+
* Include any relevant information that can help our support team understand and resolve the issue.
20+
* Click the "Submit" button to send your incident report.
21+
* You will receive a confirmation message indicating that your incident has been reported successfully.
22+
* You should hear from our support team shortly after submitting the incident report.
23+
24+
### Getting URL that doesn't require SSO
25+
26+
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.
27+
To prepare for this situation, you can get a URL that doesn't require SSO by following these steps:
28+
29+
* Visit [Tobiko Cloud Incident Reporting Page](https://incidents.tobikodata.com/).
30+
* Click the "Copy Standalone URL" button below the report incident part of the page.
31+
* Save this URL within your organization so that anyone can use it in case SSO is not working.
32+
33+
### If you don't have SSO enabled for your organization
34+
35+
Contact your solution architect and ask them to provide you with a URL that doesn't require SSO.

mkdocs.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,7 @@ nav:
125125
- cloud/features/scheduler/dagster.md
126126
- Security:
127127
- "Security Overview": cloud/features/security/security.md
128+
- "Incident Reporting": cloud/features/incident_reporting.md
128129
# - Observability:
129130
# - cloud/features/observability/overview.md
130131
# - cloud/features/observability/model_freshness.md

0 commit comments

Comments
 (0)