Skip to content
Snippets Groups Projects
Commit 4c974bd4 authored by Mark Florian's avatar Mark Florian
Browse files

Enable Threat Monitoring page by default

This enables the Threat Monitoring feature by default (and can be
disabled by explicitly disabling the `threat_monitoring` feature flag).

This also adds some basic documentation for Threat Monitoring.

Part of [WAF statistics reporting][1].

[1]: #14707
parent 20d0479c
No related branches found
No related tags found
No related merge requests found
Pipeline #108992285 failed
......@@ -280,6 +280,20 @@ from processing any requests for the given application or environment.
To permanently disable it, you must [uninstall](#uninstalling-applications) and
reinstall your Ingress application for the changes to take effect.
##### Viewing Web Application Firewall traffic
> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/14707) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 12.8.
You can view Web Application Firewall traffic by navigating to your project's
**Security & Compliance > Threat Monitoring** page.
From there, you can see tracked over time:
* the total amount of traffic to your application
* the proportion of traffic that is considered anomalous by the Web Application
Firewall
![Threat Monitoring](img/threat_monitoring_v12_8.png)
### JupyterHub
> - Introduced in GitLab 11.0 for project-level clusters.
......
doc/user/clusters/img/threat_monitoring_v12_8.png

52 KiB

......@@ -82,7 +82,7 @@ module ProjectPolicy
with_scope :subject
condition(:threat_monitoring_enabled) do
@subject.beta_feature_available?(:threat_monitoring)
@subject.feature_available?(:threat_monitoring)
end
with_scope :subject
......
---
title: Add Threat Monitoring page
merge_request: 22911
author:
type: added
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment