Certificate/Cipher Suite
diff --git a/docs/wafd/umn/waf_01_0021.html b/docs/wafd/umn/waf_01_0021.html
index 30dcd48c7..271306d33 100644
--- a/docs/wafd/umn/waf_01_0021.html
+++ b/docs/wafd/umn/waf_01_0021.html
@@ -1,8 +1,8 @@
Viewing the Dashboard
-This topic describes how to view protection event logs, including attack and request statistics, event distribution, top 10 attacked domain names, top 10 attack source IP addresses, and top 10 attacked URLs in a specified time range, such as yesterday, today, past 3 days, past 7 days, or past 30 days.
- Prerequisites
+ If you have connected websites to WAF, you can have a glance at their security on the Dashboard page. You will learn of WAF updates, protection overview, product details, as well as the security statistics of protected websites and instances you have for up to 30 days. You can also check event source statistics and bot protection statistics.
+
Specification LimitationsYou can view the protection data of a maximum of 30 days.
@@ -50,12 +50,12 @@
 Queries Per Second (QPS) indicates the number of requests per second. For example, an HTTP GET request is also called a query. The number of requests is the total number of requests in a specific time range.
- Viewing the Dashboard- Log in to the management console.
- Click
 in the upper left corner of the management console and select a region or project. - Click
 in the upper left corner and choose Web Application Firewall (Dedicated) under Security. - In the upper part of the page, select a project from the Enterprise Project drop-down list. Then, specify the website, instance, and time range for your query.
- By default, the information about all websites you add to WAF in all enterprise projects are displayed.
- Domain Names: shows information about websites added to the WAF instance in the selected enterprise project. Click View to go to the Website Settings page and view details about domain names of protected websites.
- Query time: You can select Yesterday, Today, Past 3 days, Past 7 days, or Past 30 days.
+Checking the Overview Information- Log in to the management console.
- Click
 in the upper left corner of the management console and select a region or project. - Click
 in the upper left corner and choose Web Application Firewall (Dedicated) under Security. - In the upper part of the page, select a project from the Enterprise Project drop-down list. Then, specify the website, instance, and time range for your query.
- By default, the information about all websites you add to WAF in all enterprise projects are displayed.
- Domain Names: shows information about websites added to the WAF instance in the selected enterprise project. Click View to go to the Website Settings page and view details about domain names of protected websites.
- Query time: You can select Yesterday, Today, Past 3 days, Past 7 days, or Past 30 days.
Figure 1 Setting search criteria
- - View how many requests, attacks, and attacked pages by attack type over the specified time range.
- Requests: shows the page views of the website, making it easy for you to view the total number of pages accessed by visitors in a certain period of time.
- Attacks: shows how many times the website are attacked.
- You can view how many pages are attacked by a certain type of attack within a certain period of time.
- You can click Show Details to view the details of the 10 domain names with the most requests, attacks, and basic web protection, precise protection, CC attack protection, and anti-crawler protection actions.
+ - View how many requests, attacks, and attacked pages by attack type over the specified time range.
- Requests: shows the page views of the website, making it easy for you to view the total number of pages accessed by visitors in a certain period of time.
- Attacks: shows how many times the website are attacked.
- You can view how many pages are attacked by a certain type of attack within a certain period of time.
- You can click Show Details to view the details of the 10 domain names with the most requests, attacks, and basic web protection, precise protection, CC attack protection, and anti-crawler protection actions.
Figure 2 Protection action statistics
- - Query security data in the Security Event Statistics area.
By day: You can select this option to view the data gathered by the day. If you leave this option unselected, you have the following options:
-- Yesterday and Today: Security event data is gathered every minute.
- Past 3 days: Security event data is gathered every 5 minutes.
- Past 7 days: Security event data is gathered every 10 minutes.
- Past 30 days: Security event data is gathered every hour.
+ - Query security data in the Security Event Statistics area.
By day: You can select this option to view the data gathered by the day. If you leave this option unselected, you have the following options:
+- Yesterday and Today: Security event data is gathered every minute.
- Past 3 days: Security event data is gathered every 5 minutes.
- Past 7 days: Security event data is gathered every 10 minutes.
- Past 30 days: Security data is gathered every hour.
Figure 3 Security Event Statistics
Table 2 Parameters in Security Event StatisticsParameter
@@ -66,25 +66,25 @@
|
|---|
Requests
|
-You can view how many requests for your website as well as total attacks and attacks of each attack type.
+ | You can view how many requests to your website as well as total attacks and attacks of each attack type.
|
QPS
|
-Average number of requests per second for the domain name. For details about the values of QPS, see How to Calculate QPS.
+ | Average number of requests per second for the domain name. For details about QPS, see How to Calculate QPS.
Queries Per Second (QPS) indicates the number of requests per second. For example, an HTTP GET request is also called a query.
|
Bytes Sent/Received
|
-Bandwidth usage
+ | Bandwidth usage.
The value of sent and received bytes is calculated by adding the values of request_length and upstream_bytes_received by time, so the value is different from the network bandwidth monitored on the EIP. This value is also affected by web page compression, connection reuse, and TCP retransmission.
|
Event Distribution
|
-Types of attack events
-Click an area in the Event Distribution area to view the type, number, and proportion of an attack.
+ | Types of attack events.
+Click an area in the Event Distribution area to view the type, number, and proportion of an attack.
|
Top 10 Attacked Domain Names
diff --git a/docs/wafd/umn/waf_01_0024.html b/docs/wafd/umn/waf_01_0024.html
index 24b8c4d59..0bfc5bb82 100644
--- a/docs/wafd/umn/waf_01_0024.html
+++ b/docs/wafd/umn/waf_01_0024.html
@@ -5,94 +5,94 @@
WAF detects attacks by using built-in basic web protection rules, built-in features in anti-crawler protection, and custom rules you configured (such as CC attack protection, precise access protection, blacklist, whitelist, and geolocation access control rules). WAF will respond to detected attacks based on the protective actions (such as Block and Log only) defined in the rules and display attack events on the Events page.
PrerequisitesThere is at least one false alarm event in the event list.
Constraints- Only attack events blocked or recorded by built-in basic web protection rules and features in anti-crawler protection can be handled as false alarms.
- For events generated based on custom rules (such as a CC attack protection rule, precise protection rule, blacklist rule, whitelist rule, or geolocation access control rule), they cannot be handled as false alarms. To ignore such an event, delete or disable the custom rule hit by the event.
- An attack event can only be handled as a false alarm once.
- After an attack event is handled as a false alarm, the attack event will not be displayed on the Events page.
- Dedicated WAF instances earlier than June 2022 do not support All protection for Ignore WAF Protection. Only Basic web protection can be selected.
+ Constraints- Only attack events blocked or recorded by built-in basic web protection rules and features in anti-crawler protection can be handled as false alarms.
- For events generated based on custom rules (such as a CC attack protection rule, precise protection rule, blacklist rule, whitelist rule, or geolocation access control rule), they cannot be handled as false alarms. To ignore such an event, delete or disable the custom rule hit by the event.
- An attack event can only be handled as a false alarm once.
- After an attack event is handled as a false alarm, the attack event will not be displayed on the Events page.
- Dedicated WAF instances earlier than June 2022 do not support All protection for Ignore WAF Protection. Only Basic web protection can be selected.
- Application ScenariosSometimes normal service requests may be blocked by WAF. For example, suppose you deploy a web application on an ECS and then add the public domain name associated with that application to WAF. If you enable basic web protection for that application, WAF may block the access requests that match the basic web protection rules. As a result, the website cannot be accessed through its domain name. However, the website can still be accessed through the IP address. In this case, you can handle the false alarms to allow normal access requests to the application.
+ Application ScenariosSometimes normal service requests may be blocked by WAF. For example, suppose you deploy a web application on ECSs and then add the public domain name associated with that application to WAF. If you enable basic web protection for that application, WAF may block the access requests that match the basic web protection rules. If the website is inaccessible over its domain name but accessible over its IP address, you can handle the false alarms to allow normal access requests to the application.
- Handling False Alarms- Log in to the management console.
- Click
 in the upper left corner and choose Web Application Firewall (Dedicated) under Security. - In the navigation pane on the left, choose Events.
- Click the Search tab. In the website or instance drop-down list, select a website to view corresponding event logs. The query time can be Yesterday, Today, Past 3 days, Past 7 days, Past 30 days, or a time range you configure.
- In the event list, handle events.
- If you confirm that an event is a false alarm, locate the row containing the event. In the Operation column, click and handle the hit rule.
Figure 1 Handling a false alarm
+Handling False Alarms- Log in to the management console.
- In the navigation pane on the left, choose Events.
- Click the Search tab. In the website or instance drop-down list, select a website to view corresponding event logs. The query time can be Yesterday, Today, Past 3 days, Past 7 days, Past 30 days, or a time range you configure.
- In the event list, handle events.
- If you confirm that an event is a false alarm, locate the row containing the event. In the Operation column, click and handle the hit rule.
Figure 1 Handling a false alarm
-Table 1 ParametersParameter
+Table 1 ParametersParameter
|
-Description
+ | Description
|
-Example Value
+ | Example Value
|
|---|
-Scope
+ | Scope
|
-- All domain names: By default, this rule will be used to all domain names that are protected by the current policy.
- Specified domain names: Specify a domain name range this rule applies to.
+ | - All domain names: By default, this rule will be applied to all domain names that are protected by the current policy.
- Specified domain names: Specify a domain name range this rule applies to.
|
-Specified domain names
+ | Specified domain names
|
-Domain Name
+ | Domain Name
|
-This parameter is mandatory when you select Specified domain names for Scope.
+ | This parameter is mandatory when you select Specified domain names for Scope.
Enter a single domain name that matches the wildcard domain name being protected by the current policy.
|
-www.example.com
+ | www.example.com
|
-Condition List
+ | Condition List
|
-Click Add to add conditions. At least one condition needs to be added. You can add up to 30 conditions to a protection rule. If more than one condition is added, all of the conditions must be met for the rule to be applied. A condition includes the following parameters:
-Parameters for configuring a condition are described as follows: - Field
- Subfield: Configure this field only when Params, Cookie, or Header is selected for Field.
NOTICE: The length of a subfield cannot exceed 2,048 bytes. Only digits, letters, underscores (_), and hyphens (-) are allowed.
+ Click Add to add conditions. At least one condition needs to be added. You can add up to 30 conditions to a protection rule. If more than one condition is added, all of the conditions must be met for the rule to be applied. A condition includes the following parameters:
+Parameters for configuring a condition are described as follows: - Field
- Subfield: Configure this field only when Params, Cookie, or Header is selected for Field.
NOTICE: The length of a subfield cannot exceed 2,048 characters. Only digits, letters, underscores (_), and hyphens (-) are allowed.
- - Logic: Select a logical relationship from the drop-down list.
- Content: Enter or select the content that matches the condition.
+ - Logic: Select a logical relationship from the drop-down list.
- Content: Enter or select the content that matches the condition.
|
- Path, Include, /product
+ | Path, Include, /product
|
|
-Ignore WAF Protection
+ | Ignore WAF Protection
|
-- All protection: All WAF rules do not take effect, and WAF allows all request traffic to the domain names in the rule.
- Basic web protection: You can ignore basic web protection by rule ID, attack type, or all built-in rules. For example, if XSS check is not required for a URL, you can whitelist XSS rule.
+ | - All protection: All WAF rules do not take effect, and WAF allows all request traffic to the domain names in the rule.
- Basic web protection: You can ignore basic web protection by rule ID, attack type, or all built-in rules. For example, if XSS check is not required for a URL, you can whitelist XSS rule.
|
-Basic web protection
+ | Basic web protection
|
-Ignored Protection Type
+ | Ignored Protection Type
|
-If you select Basic web protection for Ignored Protection Type, specify the following parameters:
+ | If you select Basic web protection for Ignored WAF Protection, select one of the following for Ignored Protection Type:
- ID: Configure the rule by event ID.
- Attack type: Configure the rule by attack type, such as XSS and SQL injection. One type contains one or more rule IDs.
- All built-in rules: all checks enabled in Basic Web Protection.
|
-Attack type
+ | Attack type
|
-Rule ID
+ | Rule ID
|
-This parameter is mandatory when you select ID for Ignored Protection Type.
+ | This parameter is mandatory when you select ID for Ignored Protection Type.
Rule ID of a misreported event in Events whose type is not Custom. You are advised to handle false alarms on the Events page.
|
-041046
+ | 041046
|
-Rule Type
+ | Rule Type
|
-This parameter is mandatory when you select Attack type for Ignored Protection Type.
+ | This parameter is mandatory when you select Attack type for Ignored Protection Type.
Select an attack type from the drop-down list box.
WAF can defend against XSS attacks, web shells, SQL injection attacks, malicious crawlers, remote file inclusions, local file inclusions, command injection attacks, and other attacks.
|
-SQL injection
+ | SQL injection
|
-Rule Description
+ | Rule Description
|
-A brief description of the rule. This parameter is optional.
+ | A brief description of the rule. This parameter is optional.
|
-SQL injection attacks are not intercepted.
+ | SQL injection attacks are not intercepted.
|
-Ignore Field
+ | Ignore Field
|
-To ignore attacks of a specific field, specify the field in the Advanced Settings area. After you add the rule, WAF will stop blocking attack events of the specified field.
+ | To ignore attacks of a specific field, specify the field in the Advanced Settings area. After you add the rule, WAF will stop blocking attacks matching the specified field.
Select a target field from the first drop-down list box on the left. The following fields are supported: Params, Cookie, Header, Body, and Multipart. - If you select Params, Cookie, or Header, you can select All or Field to configure a subfield.
- If you select Body or Multipart, you can select All.
- If you select Cookie, the Domain Name box for the rule can be empty.
NOTE: If All is selected, WAF will not block all attack events of the selected field.
|
-Params
+ | Params
All
|
@@ -103,47 +103,47 @@
Figure 2 Add to Address Group
- Add the source IP address to a blacklist or whitelist rule of the corresponding protected domain name. Locate the row containing the desired event. In the Operation column, click . Then, the source IP address will be blocked or allowed based on the protective action configured in the blacklist or whitelist rule.
Figure 3 Add to Blacklist/Whitelist
-Table 2 Parameter descriptionsParameter
+Table 2 Parameter descriptionsParameter
|
-Description
+ | Description
|
|---|
-Add to
+ | Add to
|
-
+ |
|
-Rule Name
+ | Rule Name
|
-- If you select Existing rule for Add to, select a rule name from the drop-down list.
- If you select New rule for Add to, customize a blacklist or whitelist rule.
+ | - If you select Existing rule for Add to, select a rule name from the drop-down list.
- If you select New rule for Add to, customize a blacklist or whitelist rule.
|
-IP Address/Range/Group
+ | IP Address/Range/Group
|
-This parameter is mandatory when you select New rule for Add to.
+ | This parameter is mandatory when you select New rule for Add to.
You can select IP address/Range or Address Group to add IP addresses a blacklist or whitelist rule.
|
-Group Name
+ | Group Name
|
-This parameter is mandatory when you select Address group for IP Address/Range/Group.
+ | This parameter is mandatory when you select Address group for IP Address/Range/Group.
Select an address group from the drop-down list.
|
-Protective Action
+ | Protective Action
|
-- Block: Select Block if you want to blacklist an IP address or IP address range.
- Allow: Select Allow if you want to whitelist an IP address or IP address range.
- Log only: Select Log only if you want to observe an IP address or IP address range.
+ | - Block: Select Block if you want to blacklist an IP address or IP address range.
- Allow: Select Allow if you want to whitelist an IP address or IP address range.
- Log only: Select Log only if you want to observe an IP address or IP address range.
|
-Known Attack Source
+ | Known Attack Source
|
-If you select Block for Protective Action, you can select a blocking type of a known attack source rule. WAF will block requests matching the configured IP address, Cookie, or Params for a length of time configured as part of the rule.
+ | If you select Block for Protective Action, you can select a blocking type of a known attack source rule. WAF will block requests matching the configured IP address, Cookie, or Params for a length of time configured as part of the rule.
|
-Rule Description
+ | Rule Description
|
-A brief description of the rule. This parameter is optional.
+ | A brief description of the rule. This parameter is optional.
|
diff --git a/docs/wafd/umn/waf_01_0027.html b/docs/wafd/umn/waf_01_0027.html
index 3903bb393..66a1df368 100644
--- a/docs/wafd/umn/waf_01_0027.html
+++ b/docs/wafd/umn/waf_01_0027.html
@@ -3,9 +3,7 @@
Which Web Service Framework Protocols Does WAF Support?
WAF is deployed on the cloud.
Web Application Firewall (WAF) keeps web services stable and secure. It examines all HTTP and HTTPS requests to detect and block the following attacks: Structured Query Language (SQL) injection, cross-site scripting (XSS), web shells, command and code injections, file inclusion, sensitive file access, third-party vulnerability exploits, Challenge Collapsar (CC) attacks, malicious crawlers, and cross-site request forgery (CSRF).
- WAF can examine the following requests:
- - WebSocket and WebSockets (enabled by default)
- WebSocket request inspection is enabled by default if Client Protocol is set to HTTP.
- WebSockets request inspection is enabled by default if Client Protocol is set to HTTPS.
- - HTTP/HTTPS
+ WAF checks HTTP and HTTPS requests.
diff --git a/docs/wafd/umn/waf_01_0035.html b/docs/wafd/umn/waf_01_0035.html
index 4aa633722..01b815f21 100644
--- a/docs/wafd/umn/waf_01_0035.html
+++ b/docs/wafd/umn/waf_01_0035.html
@@ -4,7 +4,7 @@
- In the row containing the attack event, click Handle as False Alarm in the Operation column. For details, see Handling False Alarms.
+ | In the row containing the attack event, click Handle as False Alarm in the Operation column. For details, see Handling False Alarms.
|
Custom protection rules
@@ -36,7 +36,7 @@
|
-Allow the blocked requests by referring to Configuring Custom Precise Protection Rules. The Handle as False Alarm button is grayed out for events that are generated against a precise protection rule.
+ | The Handle as False Alarm button is grayed out for events that are generated against a precise protection rule. To allow the blocked requests, see Configuring Custom Precise Protection Rules.
|
diff --git a/docs/wafd/umn/waf_01_0045.html b/docs/wafd/umn/waf_01_0045.html
index 063732af9..ba2ddecf2 100644
--- a/docs/wafd/umn/waf_01_0045.html
+++ b/docs/wafd/umn/waf_01_0045.html
@@ -8,7 +8,7 @@
The process of forwarding traffic from WAF to origin servers is called back-to-source. WAF uses back-to-source IP addresses to send client requests to the origin server. When a website is connected to WAF, the destination IP addresses to the client are the IP addresses of WAF, so that the origin server IP address is invisible to the client.
Figure 2 Back-to-source IP address
- How WAF Works (ELB Access Mode)If you connect a website to WAF in ELB access mode, WAF works as follows:
+ How WAF Works (ELB Access Mode)If you connect a website to WAFELB access mode, WAF works as follows:
- In this mode, WAF is integrated into the gateway of an ELB load balancer through an SDK module. WAF extracts traffic through the SDK module embedded in the gateway for inspection.
- WAF synchronizes the inspection result to the load balancer, and the load balancer determines whether to forward client requests to the origin server based on the inspection result.
- In this method, WAF does not forward traffic. This reduces compatibility and stability problems.
Figure 3 How WAF in ELB load balancer access mode works
diff --git a/docs/wafd/umn/waf_01_0054.html b/docs/wafd/umn/waf_01_0054.html
index 5f535acd8..cea114498 100644
--- a/docs/wafd/umn/waf_01_0054.html
+++ b/docs/wafd/umn/waf_01_0054.html
@@ -3,65 +3,63 @@
Configuring Information Leakage Prevention Rules to Protect Sensitive Information from Leakage
You can add two types of information leakage prevention rules.
- Sensitive information filtering: prevents disclosure of sensitive information, such as ID numbers, phone numbers, and email addresses.
- Response code interception: blocks the specified HTTP status codes.
- If you have enabled enterprise projects, ensure that you have all operation permissions for the project where your WAF instance locates. Then, you can select the project from the Enterprise Project drop-down list and configure protection policies for the domain names in the project.
-
- PrerequisitesYou have added your website to a policy.
+
Constraints- It takes several minutes for a new rule to take effect. After the rule takes effect, protection events triggered by the rule will be displayed on the Events page.
- Configuring an Information Leakage Prevention Rule- Log in to the management console.
- Click
 in the upper left corner of the management console and select a region or project. - Click
 in the upper left corner and choose Web Application Firewall (Dedicated) under Security. - In the navigation pane on the left, choose Policies.
- Click the name of the target policy to go to the protection configuration page.
- Click the Information Leakage Prevention configuration area and toggle it on or off if needed.
 : enabled. : disabled.
- - In the upper left corner above the Information Leakage Prevention rule list, click Add Rule.
- In the dialog box displayed, add an information leakage prevention rule by referring to Table 1.
Information leakage prevention rules prevent sensitive information (such as ID numbers, phone numbers, and email addresses) from being disclosed. This type of rule can also block specified HTTP status codes.
-Sensitive information filtering: Configure rules to mask sensitive information, such as phone numbers and ID numbers, from web pages. For example, you can set the following protection rules to mask sensitive information, such as ID numbers, phone numbers, and email addresses: Figure 1 Sensitive information leakage
+ Configuring an Information Leakage Prevention Rule- Log in to the management console.
- Click in the upper left corner of the management console and select a region or project.
- Click in the upper left corner and choose Web Application Firewall (Dedicated) under Security.
- In the navigation pane on the left, click Policies.
- Click the name of the target policy to go to the protection configuration page.
- Click the Information Leakage Prevention configuration area and toggle it on or off if needed.
- : enabled.
- : disabled.
+ - In the upper left corner above the Information Leakage Prevention rule list, click Add Rule.
- In the dialog box displayed, add an information leakage prevention rule by referring to Table 1. Figure 1 and Figure 2 show the examples.
Information leakage prevention rules prevent sensitive information (such as ID numbers, phone numbers, and email addresses) from being disclosed. This type of rule can also block specified HTTP status codes.
+Sensitive information filtering: Configure rules to mask sensitive information, such as phone numbers and ID numbers, from web pages. For example, you can set the following protection rules to mask sensitive information, such as ID numbers, phone numbers, and email addresses: Figure 1 Sensitive information leakage
-Response code interception: An error page of a specific HTTP response code may contain sensitive information. You can configure rules to block such error pages to prevent such information from being leaked out. For example, you can set the following rule to block error pages of specified HTTP response codes 404, 502, and 503. Figure 2 Blocking response codes
+ Response code interception: An error page of a specific HTTP response code may contain sensitive information. You can configure rules to block such error pages to prevent such information from being leaked out. For example, you can set the following rule to block error pages of specified HTTP response codes 404, 502, and 503. Figure 2 Blocking response codes
- Table 1 Rule parametersParameter
+Table 1 Rule parametersParameter
|
-Description
+ | Description
|
-Example Value
+ | Example Value
|
|---|
-Path
+ | Path
|
-A part of the URL that does not include the domain name. The URL can contain sensitive information (such as ID numbers, phone numbers, and email addresses) or a blocked error code.
+ | A part of the URL that does not include the domain name. The URL can contain sensitive information (such as ID numbers, phone numbers, and email addresses) or a blocked error code.
- Prefix match: Only the prefix of the path to be entered must match that of the path to be protected.
If the path to be protected is /admin, set Path to /admin*.
- Exact match: The path to be entered must match the path to be protected.
If the path to be protected is /admin, set Path to /admin.
NOTE: - The path supports prefix and exact matches only. Regular expressions are not supported.
- The path cannot contain two or more consecutive slashes. For example, ///admin. If you enter ///admin, the WAF engine converts /// to /.
|
-/admin*
+ | /admin*
|
-Type
+ | Type
|
-- Sensitive information filtering
- Response code interception: Enable WAF to block the specified HTTP response code page.
+ | - Sensitive information filtering
- Response code interception: Enable WAF to block the specified HTTP response code page.
|
-Sensitive information filtering
+ | Sensitive information filtering
|
-Content
+ | Content
|
-Information to be protected. Options are Identification card, Phone number, and Email.
+ | Information to be protected. Options are Identification card, Phone number, and Email.
|
-Identification card
+ | Identification card
|
-Protective Action
+ | Protective Action
|
-Action the rule takes. You can select Filter or Log only.
+ | Action the rule takes. You can select Filter or Log only.
|
-Filter
+ | Filter
|
-Rule Description
+ | Rule Description
|
-A brief description of the rule. This parameter is optional.
+ | A brief description of the rule. This parameter is optional.
|
-None
+ | None
|
diff --git a/docs/wafd/umn/waf_01_0060.html b/docs/wafd/umn/waf_01_0060.html
index 44cdc5182..f9b7fd550 100644
--- a/docs/wafd/umn/waf_01_0060.html
+++ b/docs/wafd/umn/waf_01_0060.html
@@ -2,10 +2,8 @@
Viewing CTS Traces in the Trace List
ScenariosAfter you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. Cloud Trace Service (CTS) stores operation records (traces) generated in the last seven days.
- These operation records are retained for seven days on the CTS console and are automatically deleted upon expiration. Manual deletion is not supported.
-
- Viewing Real-Time Traces- Log in to the management console.
- Click
 in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed. - Choose Trace List in the navigation pane on the left.
- Set filters to search for your desired traces, as shown in Figure 1. The following filters are available.
Figure 1 Filters
+Viewing Real-Time Traces in the Trace List- Log in to the management console.
- Click in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
- Choose Trace List in the navigation pane on the left.
- Set filters to search for your desired traces, as shown in Figure 1. The following filters are available.
Figure 1 Filters
- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
|
|---|
|
|---|
|
|---|
|
|
in the upper left corner of the management console and select a region or project.
in the upper left corner and choose Web Application Firewall (Dedicated) under Security.
