Skip to content

Commit 7a6bd2e

Browse files
Removes comments
1 parent e4e6b17 commit 7a6bd2e

File tree

1 file changed

+4
-31
lines changed

1 file changed

+4
-31
lines changed

solutions/security/get-started/configure-advanced-settings.md

Lines changed: 4 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -4,34 +4,7 @@ mapped_urls:
44
- https://www.elastic.co/guide/en/serverless/current/security-advanced-settings.html
55
---
66

7-
# Configure advanced settings
8-
9-
% What needs to be done: Align serverless/stateful
10-
11-
% Use migrated content from existing pages that map to this page:
12-
13-
% - [x] ./raw-migrated-files/security-docs/security/advanced-settings.md
14-
% - [ ] ./raw-migrated-files/docs-content/serverless/security-advanced-settings.md
15-
16-
% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
17-
18-
$$$update-sec-indices$$$
19-
20-
$$$exclude-cold-frozen-data-rule-executions$$$
21-
22-
$$$exclude-cold-frozen-tiers$$$
23-
24-
$$$ip-reputation-links$$$
25-
26-
$$$manage-alert-tags$$$
27-
28-
$$$max-notes-alerts-events$$$
29-
30-
$$$show-related-integrations$$$
31-
32-
$$$update-threat-intel-indices$$$
33-
34-
$$$visualizations-in-flyout$$$
7+
# Configure advanced settings [security-advanced-settings]
358

369
The advanced settings determine:
3710

@@ -59,8 +32,6 @@ Modifying advanced settings can affect Kibana performance and cause problems tha
5932

6033
## Access advanced settings [security-advanced-settings-access-advanced-settings]
6134

62-
% The advanced settings are located in a different place in Serverless. See line 27 in the raw migrated Serverless file for more info. Also remember to annotate the Serverless and ESS content appropriately.
63-
6435
To access advanced settings, go to **Stack Management****Advanced Settings**, then scroll down to **Security Solution** settings.
6536

6637
:::{image} ../../../images/security-solution-advanced-settings.png
@@ -71,6 +42,8 @@ To access advanced settings, go to **Stack Management** → **Advanced Settings*
7142

7243
## Update default Elastic Security indices [update-sec-indices]
7344

45+
The `securitySolution:defaultIndex` field defines which {{es}} indices the {{security-app}} uses to collect data. By default, index patterns are used to match sets of {{es}} indices.
46+
7447
The `securitySolution:defaultIndex` field defines which {{es}} indices the {{security-app}} uses to collect data. By default, index patterns are used to match sets of {{es}} indices:
7548

7649
* `apm-*-transaction*`
@@ -105,7 +78,7 @@ If you leave the `-*elastic-cloud-logs-*` index pattern selected, all Elastic cl
10578

10679
The `securitySolution:defaultThreatIndex` advanced setting specifies threat intelligence indices that {{elastic-sec}} features query for ingested threat indicators. This setting affects features that query threat intelligence indices, such as the Threat Intelligence view on the Overview page, indicator match rules, and the alert enrichment query.
10780

108-
% The max limit of threat intel indices is different in the Serverless docs -- not sure why. See line 80 in the raw migrated Serverless file for more info. If add the Serverless content, remember to annotate the Serverless and ESS content appropriately.
81+
10982

11083
You can specify one or more threat intelligence indices; multiple indices must be separated by commas. By default, only the `logs-ti*` index pattern is specified. Do not remove or overwrite this index pattern, as it is used by {{agent}} integrations.
11184

0 commit comments

Comments
 (0)