Skip to content

Commit a8568ee

Browse files
authored
Remove references to pre-Bento UI (#4091)
* Remove references to pre-bento UI * Remove references to pre-Bento UI * Update docs/send-data/collection/processing-rules/create-processing-rule.md * Update docs/send-data/collection/processing-rules/create-processing-rule.md
1 parent 2dd1b45 commit a8568ee

File tree

4 files changed

+16
-83
lines changed

4 files changed

+16
-83
lines changed

docs/contributing/word-list.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ This word list provides an alphabetized list of commonly used terms at Sumo Logi
2727

2828
**Check box**. Check box is two words. Don't use checkbox.
2929

30-
**Classic UI**. Use this term to distinguish the old UI.
30+
**Classic UI**. Use this term to clarify that you're talking about the legacy UI.
3131

3232
**Click**. You click a UI element. Do not use "click on".
3333

docs/metrics/metrics-operators/outlier.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,9 @@ outlier [window=<time_unit_or_number>, threshold=<number>, direction=[ +- | + |
2020

2121
Where:
2222

23-
* `window` is the range over which to calculate the moving average and standard deviation of the time series. `window` can be specified with time units (s, m, h), or it can be specified without time units. Default: 5m.
24-
:::note
25-
If you use `outlier` in the Classic Metrics UI, if you specify the `window` parameter without supplying a unit of time, the window duration applied will be in the units used in the [quantization](docs/metrics/introduction/metric-quantization.md) of the query.
23+
* `window` is the range over which to calculate the moving average and standard deviation of the time series. `window` can be specified with time units (s, m, h), or it can be specified without time units. Default: 5m.
2624
* `threshold` is the number of standard deviations from the moving average that defines the threshold band. Default: 3
27-
* `direction` specifies what deviation direction should trigger violations: positive deviations (+), negative deviations (-), or both (+-). Default: +-
25+
* `direction` specifies what deviation direction should trigger violations: positive deviations (`+`), negative deviations (`-`), or both (`+-`). Default: `+-`.
2826

2927
![outlier-operator.png](/img/metrics/outlier-operator.png)
3028

docs/search/get-started-with-search/search-basics/comments-search-queries.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,8 @@ The following is a multi-line comment.
3333

3434
![multi line comment.png](/img/search/get-started-search/search-basics/comments-search-queries/multi-line-comment.png)
3535

36-
## Pro Tip: Sumo Logic App Queries as Examples
36+
## Pro Tip: Leverage pre-built Sumo Logic app queries
3737

38-
Sumo Logic Apps are a great resource of example search queries. You can review and even [run searches from Sumo Logic Apps](/docs/get-started/apps-integrations#run-searches-from-sumo-logic-apps) without installing them. To view available Sumo Logic Apps, click the **Library** icon <img src={useBaseUrl('img/reuse/library-icon.png')} alt="Library icon" style={{border: '1px solid gray'}} width="30" /> at the top of the UI (**Library > Apps** in the classic UI). You can also [copy content from the Library](/docs/get-started/library), and use it as a starting point to create your own queries. When you do that, you can comment out the aggregation lines of the query and replace them with your own. You can also delete them of course, but commenting them out instead would make them available for reference later.
38+
Sumo Logic apps are a great resource for example search queries. You can preview and even [run a Log Search a from Sumo Logic app](/docs/get-started/apps-integrations#run-searches-from-sumo-logic-apps) without installing it.
39+
40+
To view available Sumo Logic apps, click the **Library** icon <img src={useBaseUrl('img/reuse/library-icon.png')} alt="Library icon" style={{border: '1px solid gray'}} width="30" /> at the top of the UI (**Library > Apps** in the Classic UI). You can also [copy content from the Library](/docs/get-started/library), and use it as a starting point to create your own queries. When you do that, you can comment out the aggregation lines of the query and replace them with your own. You can also delete them of course, but commenting them out instead would make them available for reference later.
Lines changed: 9 additions & 76 deletions
Original file line numberDiff line numberDiff line change
@@ -1,35 +1,17 @@
11
---
22
id: create-processing-rule
33
title: Create a Processing Rule
4-
description: Processing rules filter and can forward data sent to Sumo Logic from a Source.
4+
description: Use processing rules to filter and forward data sent from a source to Sumo Logic.
55
---
66

7-
There are two user interfaces (UI) to create a Processing Rule, classic and new. The new interface is only available on certain Sources and is being released incrementally. Each UI is documented in a separate tab below.
7+
This document describes how to create a processing rule.
88

9-
<Tabs
10-
className="unique-tabs"
11-
defaultValue="new-ui"
12-
values={[
13-
{label: 'New UI', value: 'new-ui'},
14-
{label: 'Classic UI', value: 'classic-ui'},
15-
]}>
16-
17-
<TabItem value="new-ui">
18-
19-
## New interface for Hosted Collector Sources
20-
21-
You can add a processing rule to an existing Source or create a processing rule when you configure a new Source.
22-
23-
1. To create a processing rule for an existing Source, go to **Manage Data** > **Collection** > **Collection** and click **Edit** next to a Source. When configuring your new or existing Source, click the **\+ Add Filter** or **\+ Add** **Action** text in the **Processing Rules** section. 
24-
25-
* A filter is either an allowlist or denylist rule.
26-
* An action is either a hash or mask rule.
27-
28-
![processing rules](/img/collector/processing-rules/create-a-processing-rule/processing-rules.png)
29-
1. Once clicked, the configuration options are displayed.
30-
31-
![generic processing rules UI with added options.png](/img/collector/processing-rules/create-a-processing-rule/generic_processing_rules_UI_with_added_options.png)
9+
You can add a processing rule to an existing Source or create one when you configure a new Source.
3210

11+
1. To create a processing rule for an existing Source, go to **Manage Data** > **Collection** > **Collection** and click **Edit** next to a Source. When configuring your new or existing Source, click the **\+ Add Filter** or **\+ Add** **Action** text in the **Processing Rules** section.
12+
* A filter is either an allowlist or denylist rule.
13+
* An action is either a hash or mask rule.<br/>![processing rules](/img/collector/processing-rules/create-a-processing-rule/processing-rules.png)
14+
1. Once clicked, the configuration options are displayed.<br/> ![generic processing rules UI with added options.png](/img/collector/processing-rules/create-a-processing-rule/generic_processing_rules_UI_with_added_options.png)
3315
1. Give a meaningful **Name** to your rule. Names can be up to 32 characters long.
3416
1. Choose the **Type** of processing rule you'd like to create:
3517
* Filters have the option to:
@@ -39,58 +21,9 @@ You can add a processing rule to an existing Source or create a processing rule
3921
* [Hash messages that match](hash-rules.md). Replace a message with a unique, randomly-generated code to protect sensitive or proprietary information. You may want to hash unique identifiers, such as credit card numbers or user names. By hashing this type of data, you can still track it, even though it is fully hidden.
4022
* [Mask messages that match](mask-rules.md). Replace an expression with a mask string that you can customize—another option to protect data, such as passwords, that you'dn't normally track.
4123
1. For **Filter**, type a regular expression that defines the messages you want to filter. The rule must match the whole message.
42-
4324
For multi-line log messages, to get the lines before and after the line containing your text, wrap the segment with **(?s).\*** such as: **(?s).\*matching text(?s).\***
44-
4525
:::note
46-
Your regex must be [RE2 compliant.](https://github.com/google/re2/wiki/Syntax)
26+
Your regex must be [RE2 compliant](https://github.com/google/re2/wiki/Syntax).
4727
:::
48-
49-
1. To remove a filter or action click the trash can icon.
50-
51-
![processing rule trach can icon.png](/img/collector/processing-rules/create-a-processing-rule/trashcan-icon.png)
52-
28+
1. To remove a filter or action, click the trash can icon.<br/> ![processing rule trash can icon.png](/img/collector/processing-rules/create-a-processing-rule/trashcan-icon.png)
5329
1. When you are finished adding all the rules you need, click **Submit**.
54-
55-
</TabItem>
56-
<TabItem value="classic-ui">
57-
58-
59-
## Original interface
60-
61-
1. To create a processing rule for an existing Source, go to **Manage Data** > **Collection** > **Collection** and click **Edit** next to a Source. When configuring your new or existing Source, expand the **Processing Rules for Logs** section and then click **Add Rule**.
62-
63-
![Add processing rule](/img/collector/processing-rules/create-a-processing-rule/no-rules.png)
64-
65-
1. The **Processing Rule for Logs** dialog is displayed. 
66-
67-
![Add Processing Rule](/img/collector/processing-rules/create-a-processing-rule/redact-rules.png)
68-
 
69-
1. Give a meaningful **Name** to your rule. Names can be up to 32 characters long.
70-
1. For **Filter**, type a regular expression that defines the messages you want to filter. The rule must match the whole message.
71-
72-
* For multi-line log messages, to get the lines before and after the line containing your text, wrap the segment with `(?s).` such as:`(?s).*matching text(?s).`
73-
74-
:::note
75-
Your regex must be [RE2 compliant](https://github.com/google/re2/wiki/Syntax).
76-
:::
77-
78-
1. Choose the **Type** of processing rule you'd like to create:
79-
80-
* [Exclude messages that match](include-and-exclude-rules.md). Remove messages that you do not want to send to Sumo Logic at all, think of it as a "denylist" filter. These messages are skipped after reaching the Source and are not uploaded to Sumo Logic.
81-
* [Include messages that match](include-and-exclude-rules.md). Send only the data you'd like in your Sumo Logic account, think of it as an "allowlist" filter. This type of filter can be very useful when the list of log data you want to send to Sumo Logic is easier to filter than setting up exclude filters for all of the types of messages you'd like to exclude, for example, if you only want to include only messages coming from a firewall.
82-
* [Hash messages that match](hash-rules.md). Replace a message with a unique, randomly-generated code to protect sensitive or proprietary information. You may want to hash unique identifiers, such as credit card numbers or user names. By hashing this type of data, you can still track it, even though it is fully hidden.
83-
* [Mask messages that match](mask-rules.md). Replace an expression with a mask string that you can customize—another option to protect data, such as passwords, that you'dn't normally track.
84-
* Forward messages that match. Send data from an Installed Collector Source to a selected non-Sumo location. This option is only available if you have configured a data forwarding destination. For more information, see [Forward Data from an Installed Collector](/docs/manage/data-forwarding/installed-collectors).
85-
86-
1. Click **Apply** to add the rule. Continue to add rules as needed.
87-
88-
1. When you are finished adding all the rules you need, click **Submit**.
89-
90-
![rule-action.png](/img/collector/processing-rules/create-a-processing-rule/save-rule.png)
91-
92-
</TabItem>
93-
</Tabs>
94-
95-
import Tabs from '@theme/Tabs';
96-
import TabItem from '@theme/TabItem';

0 commit comments

Comments
 (0)