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
3b91c9ec
Commit
3b91c9ec
authored
Sep 12, 2020
by
Shinya Maeda
Committed by
Marcel Amirault
Sep 12, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Documentation for Show Alert in Environment Index page feature
This commit adds the documentation and e2e tests.
parent
9e439fbe
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
32 additions
and
0 deletions
+32
-0
doc/ci/environments/img/alert_for_environment.png
doc/ci/environments/img/alert_for_environment.png
+0
-0
doc/ci/environments/index.md
doc/ci/environments/index.md
+32
-0
No files found.
doc/ci/environments/img/alert_for_environment.png
0 → 100644
View file @
3b91c9ec
16.4 KB
doc/ci/environments/index.md
View file @
3b91c9ec
...
@@ -864,6 +864,38 @@ exist, you should see something like:
...
@@ -864,6 +864,38 @@ exist, you should see something like:
![
Environment groups
](
../img/environments_dynamic_groups.png
)
![
Environment groups
](
../img/environments_dynamic_groups.png
)
### Environment incident management
You have successfuly setup a Continous Delivery/Deployment workflow in your project.
Production environments can go down unexpectedly, including for reasons outside
of your own control. For example, issues with external dependencies, infrastructure,
or human error can cause major issues with an environment. This could include:
-
A dependent cloud service goes down.
-
A 3rd party library is updated and it's not compatible with your application.
-
Someone performs a DDoS attack to a vulnerable endpoint in your server.
-
An operator misconfigures infrastructure.
-
A bug is introduced into the production application code.
You can use
[
incident management
](
../../operations/incident_management/index.md
)
to get alerts when there are critical issues that need immediate attention.
#### View the latest alerts for environments **(ULTIMATE)**
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/214634) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 13.4.
If you
[
set up alerts for Prometheus metrics
](
../../operations/metrics/alerts.md
)
,
alerts for environments are shown on the environments page. The alert with the highest
severity is shown, so you can identify which environments need immediate attention.
![
Environment alert
](
img/alert_for_environment.png
)
When the issue that triggered the alert is resolved, it is removed and is no
longer visible on the environment page.
If the alert requires a
[
rollback
](
#retrying-and-rolling-back
)
, you can select the
deployment tab from the environment page and select which deployment to roll back to.
### Monitoring environments
### Monitoring environments
If you have enabled
[
Prometheus for monitoring system and response metrics
](
../../user/project/integrations/prometheus.md
)
,
If you have enabled
[
Prometheus for monitoring system and response metrics
](
../../user/project/integrations/prometheus.md
)
,
...
...
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