Skip to content

Commit a800602

Browse files
committed
Remove links to visualization tool
The visualization tool is no longer available. Left the visualizations since they are still helpful in explaining the concepts. Signed-off-by: Erik Bledsoe <[email protected]>
1 parent 93a8ab7 commit a800602

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

quickstart/life-of-a-fluentd-event.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -118,9 +118,7 @@ A **Filter** behaves like a rule to pass or reject an event. The following confi
118118
</match>
119119
```
120120

121-
Fluentd configuration visualization link: [https://link.calyptia.com/gjl](https://link.calyptia.com/gjl) \(sign-up required\)
122-
123-
![Visualization from Calyptia](../.gitbook/assets/screen-shot-2021-03-16-at-12.50.12-pm.png)
121+
![Visualization](../.gitbook/assets/screen-shot-2021-03-16-at-12.50.12-pm.png)
124122

125123
As you can see, the new **Filter** definition will be a mandatory step to pass before the control goes to the **Match** section. The **Filter** basically will accept or reject the **Event** based on its `type` and rule. For our example we want to discard any user **logout** action. We only care about the **logins**. The way to accomplish this, is doing a `grep` inside the **Filter** to exclude any message on which `action` key have the **logout** string.
126124

@@ -210,9 +208,7 @@ This new implementation called **Labels**, aims to solve the configuration file
210208
</label>
211209
```
212210

213-
Fluentd configuration visualization: [https://link.calyptia.com/guh](https://link.calyptia.com/guh) \(sign-up required\)
214-
215-
![Visualization from Calyptia](../.gitbook/assets/screen-shot-2021-03-16-at-12.51.26-pm.png)
211+
![Visualization](../.gitbook/assets/screen-shot-2021-03-16-at-12.51.26-pm.png)
216212

217213
The new configuration contains a `@label` parameter under `source` indicating that the further steps will take place on the `@STAGING` label section. The expectation is that every event reported on the **Source**, the **Routing Engine** will continue processing on `@STAGING`. Hence, it will skip the old filter definition.
218214

0 commit comments

Comments
 (0)