Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
d37d01fc
Commit
d37d01fc
authored
Aug 13, 2021
by
Suzanne Selhorn
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Updated nav steps to match standards
Related to:
https://gitlab.com/gitlab-org/technical-writing/-/issues/454
parent
c85edcc1
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
25 additions
and
18 deletions
+25
-18
doc/operations/incident_management/paging.md
doc/operations/incident_management/paging.md
+5
-4
doc/operations/incident_management/status_page.md
doc/operations/incident_management/status_page.md
+20
-14
No files found.
doc/operations/incident_management/paging.md
View file @
d37d01fc
...
...
@@ -27,10 +27,11 @@ Email notifications are available in projects for triggered alerts. Project
members with the
**Owner**
or
**Maintainer**
roles have the option to receive
a single email notification for new alerts.
1.
Navigate to
**Settings > Monitor**
.
1.
Expand the
**Alerts**
section.
1.
In the
**Integration settings**
tab, select the checkbox
**Send a single email notification to Owners and Maintainers for new alerts**
.
1.
On the top bar, select
**Menu > Projects**
and find your project.
1.
On the left sidebar, select
**Settings > Monitor**
.
1.
Expand
**Alerts**
.
1.
On the
**Alert settings**
tab, select the
**Send a single email notification to Owners and Maintainers for new alerts**
checkbox.
1.
Select
**Save changes**
.
## Paging **(PREMIUM)**
...
...
doc/operations/incident_management/status_page.md
View file @
d37d01fc
...
...
@@ -39,19 +39,23 @@ To configure a GitLab Status Page you must:
Only AWS S3 is supported as a deploy target.
Prerequisite:
-
You must have at least the Maintainer
[
role
](
../../user/permissions.md
)
.
To provide GitLab with the AWS account information needed to push content to your Status Page:
1.
Sign into GitLab as a user with Maintainer or greater
[
permissions
](
../../user/permissions.md
)
.
1.
Navigate to
**{settings}**
**Settings > Monitor**
. Next to
**Status Page**
,
click
**Expand
**
.
1.
Click
**Active**
to enable the Status Page feature
.
1.
In
**Status Page URL**
, provide the URL to
your external status page.
1.
Provide the
**S3 Bucket name**
. For more information, see
1.
On the top bar, select
**Menu > Projects**
and find your project
.
1.
On the left sidebar, select
**Settings > Monitor**
.
1.
Expand
**Status Page
**
.
1.
Select the
**Active**
checkbox
.
1.
In
the
**Status Page URL**
box, provide the URL for
your external status page.
1.
In the
**S3 Bucket name**
box, type the name of your S3 bucket
. For more information, see
[
Bucket configuration documentation
](
https://docs.aws.amazon.com/AmazonS3/latest/dev/HostingWebsiteOnS3Setup.html
)
.
1.
Provide the
**AWS region**
for your bucket. For more information, see the
1.
In the
**AWS region**
box, type the region
for your bucket. For more information, see the
[
AWS documentation
](
https://github.com/aws/aws-sdk-ruby#configuration
)
.
1.
Provide
your
**AWS access key ID**
and
**AWS Secret access key**
.
1.
Click
**Save changes**
.
1.
Enter
your
**AWS access key ID**
and
**AWS Secret access key**
.
1.
Select
**Save changes**
.
### Configure your AWS account
...
...
@@ -69,8 +73,8 @@ the necessary CI/CD variables to deploy the Status Page to AWS S3:
1.
Fork the
[
Status Page
](
https://gitlab.com/gitlab-org/status-page
)
project.
You can do this through
[
Repository Mirroring
](
https://gitlab.com/gitlab-org/status-page#repository-mirroring
)
,
which ensures you get the up-to-date Status Page features.
1.
Navigate to
**{settings}**
**Settings > CI/CD**
.
1.
Scroll to
**Variables**
, and click
**Expand
**
.
1.
On the left sidebar, select
**Settings > CI/CD**
.
1.
Expand
**Variables
**
.
1.
Add the following variables from your Amazon Console:
-
`S3_BUCKET_NAME`
- The name of the Amazon S3 bucket.
If no bucket with the provided name exists, the first pipeline run creates
...
...
@@ -80,8 +84,8 @@ the necessary CI/CD variables to deploy the Status Page to AWS S3:
-
`AWS_DEFAULT_REGION`
- The AWS region.
-
`AWS_ACCESS_KEY_ID`
- The AWS access key ID.
-
`AWS_SECRET_ACCESS_KEY`
- The AWS secret.
1.
Navigate to
**CI/CD > Pipelines > Run Pipeline**
, and run the pipeline to
deploy the Status Page to S3
.
1.
On the left sidebar, select
**CI/CD > Pipelines**
.
1.
To deploy the Status Page to S3, select
**Run pipeline**
.
WARNING:
Consider limiting who can access issues in this project, as any user who can view
...
...
@@ -92,7 +96,9 @@ the issue can potentially [publish comments to your GitLab Status Page](#publish
After creating the CI/CD variables, configure the Project you want to use for
Incident issues:
1.
To view the Status Page settings, navigate to
**{settings}**
**Settings > Monitor > Status Page**
.
1.
On the top bar, select
**Menu > Projects**
and find your project.
1.
On the left sidebar, select
**Settings > Monitor**
.
1.
Expand
**Status page**
.
1.
Fill in your cloud provider's credentials and make sure to select the
**Active**
checkbox.
1.
Select
**Save changes**
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment