implemented mermaid js for dynamic diagrams, closes 1938
parent
4b97be7bba
commit
80fecb7d12
|
@ -175,13 +175,6 @@ Insert cloud-specific markdown content here.
|
|||
{{% /cloud %}}
|
||||
```
|
||||
|
||||
#### All content is cloud-specific
|
||||
If all content in an article is cloud-specific, include `cloud` in the `products` frontmatter.
|
||||
|
||||
```yaml
|
||||
products: [cloud]
|
||||
```
|
||||
|
||||
#### InfluxDB Cloud name
|
||||
The name used to refer to InfluxData's cloud offering is subject to change.
|
||||
To facilitate easy updates in the future, use the `cloud-name` short-code when
|
||||
|
@ -206,13 +199,6 @@ InfluxDB Cloud.
|
|||
Find more info [here][{{< cloud-link >}}]
|
||||
```
|
||||
|
||||
### InfluxDB OSS Content
|
||||
If all content in an article is OSS-specific, include `oss` in the `products` frontmatter.
|
||||
|
||||
```yaml
|
||||
products: [oss]
|
||||
```
|
||||
|
||||
### Latest links
|
||||
Each of the InfluxData projects have different "latest" versions.
|
||||
Use the `{{< latest >}}` shortcode to populate link paths with the latest version
|
||||
|
@ -384,6 +370,20 @@ The following parameters are available:
|
|||
{{< keybind mac="⇧⌘P" linux="Ctrl+Shift+P" win="Ctrl+Shift+Alt+P" >}}
|
||||
```
|
||||
|
||||
### Diagrams
|
||||
Use the `{{< diagram >}}` shortcode to dynamically build diagrams.
|
||||
The shortcode uses [mermaid.js](https://github.com/mermaid-js/mermaid) to convert
|
||||
simple text into SVG diagrams.
|
||||
For information about the syntax, see the [mermaid.js documentation](https://mermaid-js.github.io/mermaid/#/).
|
||||
|
||||
```md
|
||||
{{< diagram >}}
|
||||
flowchart TB
|
||||
This --> That
|
||||
That --> There
|
||||
{{< /diagram >}}
|
||||
```
|
||||
|
||||
### Related content
|
||||
Use the `related` frontmatter to include links to specific articles at the bottom of an article.
|
||||
|
||||
|
|
|
@ -102,6 +102,7 @@
|
|||
"article/children",
|
||||
"article/code",
|
||||
"article/cloud",
|
||||
"article/diagrams",
|
||||
"article/enterprise",
|
||||
"article/expand",
|
||||
"article/feedback",
|
||||
|
|
|
@ -0,0 +1,44 @@
|
|||
.mermaid {
|
||||
opacity: 0;
|
||||
color: $article-bg;
|
||||
margin: 3rem 0;
|
||||
transition: opacity .5s;
|
||||
|
||||
|
||||
.arrowheadPath, .arrowMarkerPath { fill: $diagram-arrow !important; }
|
||||
.edgePath .path, .flowchart-link { stroke: $diagram-arrow !important; }
|
||||
.label { color: $article-text !important; }
|
||||
.cluster-label .nodeLabel {
|
||||
color: $article-code !important;
|
||||
}
|
||||
.edgeLabel {
|
||||
color: $article-text !important;
|
||||
background: $article-code-bg !important;
|
||||
font-size: .85em;
|
||||
font-weight: $medium;
|
||||
}
|
||||
|
||||
.node {
|
||||
rect,
|
||||
circle,
|
||||
ellipse,
|
||||
polygon,
|
||||
path {
|
||||
fill: $article-bg !important;
|
||||
stroke: $diagram-arrow !important;
|
||||
stroke-width: 2px !important;
|
||||
}
|
||||
.label { color: $article-text !important; }
|
||||
}
|
||||
|
||||
.cluster {
|
||||
rect,
|
||||
circle,
|
||||
ellipse,
|
||||
polygon,
|
||||
path {
|
||||
fill: $article-code-bg !important;
|
||||
stroke: none !important;
|
||||
}
|
||||
}
|
||||
}
|
|
@ -209,6 +209,9 @@ $svg-geo-s2-cell: $b-dodger;
|
|||
$svg-geo-region: $p-comet;
|
||||
$svg-geo-point: $br-chartreuse;
|
||||
|
||||
// Diagram colors
|
||||
$diagram-arrow: $g6-smoke;
|
||||
|
||||
@import "dark/telegraf",
|
||||
"dark/chronograf",
|
||||
"dark/kapacitor";
|
||||
|
|
|
@ -209,6 +209,9 @@ $svg-geo-s2-cell: $b-hydrogen !default;
|
|||
$svg-geo-region: $br-galaxy !default;
|
||||
$svg-geo-point: $p-potassium !default;
|
||||
|
||||
// Diagram colors
|
||||
$diagram-arrow: $g14-chromium !default;
|
||||
|
||||
@import "light/telegraf",
|
||||
"light/chronograf",
|
||||
"light/kapacitor";
|
||||
|
|
|
@ -15,30 +15,16 @@ This document describes in detail how clustering works in InfluxEnterprise. It s
|
|||
|
||||
An InfluxEnterprise installation consists of three separate software processes: Data nodes, Meta nodes, and the Enterprise Web server. To run an InfluxDB cluster, only the meta and data nodes are required. Communication within a cluster looks like this:
|
||||
|
||||
```text
|
||||
┌───────┐ ┌───────┐
|
||||
│ │ │ │
|
||||
│ Meta1 │◀───▶│ Meta2 │
|
||||
│ │ │ │
|
||||
└───────┘ └───────┘
|
||||
▲ ▲
|
||||
│ │
|
||||
│ ┌───────┐ │
|
||||
│ │ │ │
|
||||
└─▶│ Meta3 │◀─┘
|
||||
│ │
|
||||
└───────┘
|
||||
|
||||
─────────────────────────────────
|
||||
╲│╱ ╲│╱
|
||||
┌────┘ └──────┐
|
||||
│ │
|
||||
┌───────┐ ┌───────┐
|
||||
│ │ │ │
|
||||
│ Data1 │◀────────▶│ Data2 │
|
||||
│ │ │ │
|
||||
└───────┘ └───────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
flowchart TB
|
||||
subgraph meta[Meta Nodes]
|
||||
Meta1 <-- TCP :8089 --> Meta2 <-- TCP :8089 --> Meta3
|
||||
end
|
||||
meta <-- HTTP :8091 --> data
|
||||
subgraph data[Data Nodes]
|
||||
Data1 <-- TCP :8088 --> Data2
|
||||
end
|
||||
{{< /diagram >}}
|
||||
|
||||
The meta nodes communicate with each other via a TCP protocol and the Raft consensus protocol that all use port `8089` by default. This port must be reachable between the meta nodes. The meta nodes also expose an HTTP API bound to port `8091` by default that the `influxd-ctl` command uses.
|
||||
|
||||
|
|
|
@ -15,30 +15,16 @@ This document describes in detail how clustering works in InfluxDB Enterprise. I
|
|||
|
||||
An InfluxDB Enterprise installation consists of three separate software processes: Data nodes, Meta nodes, and the Enterprise Web server. To run an InfluxDB cluster, only the meta and data nodes are required. Communication within a cluster looks like this:
|
||||
|
||||
```text
|
||||
┌───────┐ ┌───────┐
|
||||
│ │ │ │
|
||||
│ Meta1 │◀───▶│ Meta2 │
|
||||
│ │ │ │
|
||||
└───────┘ └───────┘
|
||||
▲ ▲
|
||||
│ │
|
||||
│ ┌───────┐ │
|
||||
│ │ │ │
|
||||
└─▶│ Meta3 │◀─┘
|
||||
│ │
|
||||
└───────┘
|
||||
|
||||
─────────────────────────────────
|
||||
╲│╱ ╲│╱
|
||||
┌────┘ └──────┐
|
||||
│ │
|
||||
┌───────┐ ┌───────┐
|
||||
│ │ │ │
|
||||
│ Data1 │◀────────▶│ Data2 │
|
||||
│ │ │ │
|
||||
└───────┘ └───────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
flowchart TB
|
||||
subgraph meta[Meta Nodes]
|
||||
Meta1 <-- TCP :8089 --> Meta2 <-- TCP :8089 --> Meta3
|
||||
end
|
||||
meta <-- HTTP :8091 --> data
|
||||
subgraph data[Data Nodes]
|
||||
Data1 <-- TCP :8088 --> Data2
|
||||
end
|
||||
{{< /diagram >}}
|
||||
|
||||
The meta nodes communicate with each other via a TCP protocol and the Raft consensus protocol that all use port `8089` by default. This port must be reachable between the meta nodes. The meta nodes also expose an HTTP API bound to port `8091` by default that the `influxd-ctl` command uses.
|
||||
|
||||
|
|
|
@ -15,30 +15,16 @@ This document describes in detail how clustering works in InfluxDB Enterprise. I
|
|||
|
||||
An InfluxDB Enterprise installation consists of three separate software processes: data nodes, meta nodes, and the Enterprise web server. To run an InfluxDB cluster, only the meta and data nodes are required. Communication within a cluster looks like this:
|
||||
|
||||
```text
|
||||
┌───────┐ ┌───────┐
|
||||
│ │ │ │
|
||||
│ Meta1 │◀───▶│ Meta2 │
|
||||
│ │ │ │
|
||||
└───────┘ └───────┘
|
||||
▲ ▲
|
||||
│ │
|
||||
│ ┌───────┐ │
|
||||
│ │ │ │
|
||||
└─▶│ Meta3 │◀─┘
|
||||
│ │
|
||||
└───────┘
|
||||
|
||||
─────────────────────────────────
|
||||
╲│╱ ╲│╱
|
||||
┌────┘ └──────┐
|
||||
│ │
|
||||
┌───────┐ ┌───────┐
|
||||
│ │ │ │
|
||||
│ Data1 │◀────────▶│ Data2 │
|
||||
│ │ │ │
|
||||
└───────┘ └───────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
flowchart TB
|
||||
subgraph meta[Meta Nodes]
|
||||
Meta1 <-- TCP :8089 --> Meta2 <-- TCP :8089 --> Meta3
|
||||
end
|
||||
meta <-- HTTP :8091 --> data
|
||||
subgraph data[Data Nodes]
|
||||
Data1 <-- TCP :8088 --> Data2
|
||||
end
|
||||
{{< /diagram >}}
|
||||
|
||||
The meta nodes communicate with each other via a TCP protocol and the Raft consensus protocol that all use port `8089` by default. This port must be reachable between the meta nodes. The meta nodes also expose an HTTP API bound to port `8091` by default that the `influxd-ctl` command uses.
|
||||
|
||||
|
|
|
@ -17,30 +17,17 @@ This document describes in detail how clustering works in InfluxDB Enterprise. I
|
|||
|
||||
An InfluxDB Enterprise installation consists of three separate software processes: data nodes, meta nodes, and the Enterprise web server. To run an InfluxDB cluster, only the meta and data nodes are required. Communication within a cluster looks like this:
|
||||
|
||||
```text
|
||||
┌───────┐ ┌───────┐
|
||||
│ │ │ │
|
||||
│ Meta1 │◀───▶│ Meta2 │
|
||||
│ │ │ │
|
||||
└───────┘ └───────┘
|
||||
▲ ▲
|
||||
│ │
|
||||
│ ┌───────┐ │
|
||||
│ │ │ │
|
||||
└─▶│ Meta3 │◀─┘
|
||||
│ │
|
||||
└───────┘
|
||||
{{< diagram >}}
|
||||
flowchart TB
|
||||
subgraph meta[Meta Nodes]
|
||||
Meta1 <-- TCP :8089 --> Meta2 <-- TCP :8089 --> Meta3
|
||||
end
|
||||
meta <-- HTTP :8091 --> data
|
||||
subgraph data[Data Nodes]
|
||||
Data1 <-- TCP :8088 --> Data2
|
||||
end
|
||||
{{< /diagram >}}
|
||||
|
||||
─────────────────────────────────
|
||||
╲│╱ ╲│╱
|
||||
┌────┘ └──────┐
|
||||
│ │
|
||||
┌───────┐ ┌───────┐
|
||||
│ │ │ │
|
||||
│ Data1 │◀────────▶│ Data2 │
|
||||
│ │ │ │
|
||||
└───────┘ └───────┘
|
||||
```
|
||||
|
||||
The meta nodes communicate with each other via a TCP protocol and the Raft consensus protocol that all use port `8089` by default. This port must be reachable between the meta nodes. The meta nodes also expose an HTTP API bound to port `8091` by default that the `influxd-ctl` command uses.
|
||||
|
||||
|
|
|
@ -10,37 +10,24 @@ menu:
|
|||
|
||||
Besides the input plugins and output plugins, Telegraf includes aggregator and processor plugins, which are used to aggregate and process metrics as they pass through Telegraf.
|
||||
|
||||
```
|
||||
┌───────────┐
|
||||
│ │
|
||||
│ CPU │───┐
|
||||
│ │ │
|
||||
└───────────┘ │
|
||||
│
|
||||
┌───────────┐ │ ┌───────────┐
|
||||
│ │ │ │ │
|
||||
│ Memory │───┤ ┌──▶│ InfluxDB │
|
||||
│ │ │ │ │ │
|
||||
└───────────┘ │ ┌─────────────┐ ┌─────────────┐ │ └───────────┘
|
||||
│ │ │ │Aggregate │ │
|
||||
┌───────────┐ │ │Process │ │ - mean │ │ ┌───────────┐
|
||||
│ │ │ │ - transform │ │ - quantiles │ │ │ │
|
||||
│ MySQL │───┼──▶ │ - decorate │────▶│ - min/max │───┼──▶│ File │
|
||||
│ │ │ │ - filter │ │ - count │ │ │ │
|
||||
└───────────┘ │ │ │ │ │ │ └───────────┘
|
||||
│ └─────────────┘ └─────────────┘ │
|
||||
┌───────────┐ │ │ ┌───────────┐
|
||||
│ │ │ │ │ │
|
||||
│ SNMP │───┤ └──▶│ Kafka │
|
||||
│ │ │ │ │
|
||||
└───────────┘ │ └───────────┘
|
||||
│
|
||||
┌───────────┐ │
|
||||
│ │ │
|
||||
│ Docker │───┘
|
||||
│ │
|
||||
└───────────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
graph TD
|
||||
Process[Process<br/> - transform<br/> - decorate<br/> - filter]
|
||||
Aggregate[Aggregate<br/> - transform<br/> - decorate<br/> - filter]
|
||||
|
||||
CPU --> Process
|
||||
Memory --> Process
|
||||
MySQL --> Process
|
||||
SNMP --> Process
|
||||
Docker --> Process
|
||||
Process --> Aggregate
|
||||
Aggregate --> InfluxDB
|
||||
Aggregate --> File
|
||||
Aggregate --> Kafka
|
||||
|
||||
style Process text-align:left
|
||||
style Aggregate text-align:left
|
||||
{{< /diagram >}}
|
||||
|
||||
**Processor plugins** process metrics as they pass through and immediately emit
|
||||
results based on the values they process. For example, this could be printing
|
||||
|
|
|
@ -10,37 +10,24 @@ menu:
|
|||
|
||||
Besides the input plugins and output plugins, Telegraf includes aggregator and processor plugins, which are used to aggregate and process metrics as they pass through Telegraf.
|
||||
|
||||
```
|
||||
┌───────────┐
|
||||
│ │
|
||||
│ CPU │───┐
|
||||
│ │ │
|
||||
└───────────┘ │
|
||||
│
|
||||
┌───────────┐ │ ┌───────────┐
|
||||
│ │ │ │ │
|
||||
│ Memory │───┤ ┌──▶│ InfluxDB │
|
||||
│ │ │ │ │ │
|
||||
└───────────┘ │ ┌─────────────┐ ┌─────────────┐ │ └───────────┘
|
||||
│ │ │ │Aggregate │ │
|
||||
┌───────────┐ │ │Process │ │ - mean │ │ ┌───────────┐
|
||||
│ │ │ │ - transform │ │ - quantiles │ │ │ │
|
||||
│ MySQL │───┼──▶ │ - decorate │────▶│ - min/max │───┼──▶│ File │
|
||||
│ │ │ │ - filter │ │ - count │ │ │ │
|
||||
└───────────┘ │ │ │ │ │ │ └───────────┘
|
||||
│ └─────────────┘ └─────────────┘ │
|
||||
┌───────────┐ │ │ ┌───────────┐
|
||||
│ │ │ │ │ │
|
||||
│ SNMP │───┤ └──▶│ Kafka │
|
||||
│ │ │ │ │
|
||||
└───────────┘ │ └───────────┘
|
||||
│
|
||||
┌───────────┐ │
|
||||
│ │ │
|
||||
│ Docker │───┘
|
||||
│ │
|
||||
└───────────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
graph TD
|
||||
Process[Process<br/> - transform<br/> - decorate<br/> - filter]
|
||||
Aggregate[Aggregate<br/> - transform<br/> - decorate<br/> - filter]
|
||||
|
||||
CPU --> Process
|
||||
Memory --> Process
|
||||
MySQL --> Process
|
||||
SNMP --> Process
|
||||
Docker --> Process
|
||||
Process --> Aggregate
|
||||
Aggregate --> InfluxDB
|
||||
Aggregate --> File
|
||||
Aggregate --> Kafka
|
||||
|
||||
style Process text-align:left
|
||||
style Aggregate text-align:left
|
||||
{{< /diagram >}}
|
||||
|
||||
**Processor plugins** process metrics as they pass through and immediately emit
|
||||
results based on the values they process. For example, this could be printing
|
||||
|
|
|
@ -10,37 +10,24 @@ menu:
|
|||
|
||||
Besides the input plugins and output plugins, Telegraf includes aggregator and processor plugins, which are used to aggregate and process metrics as they pass through Telegraf.
|
||||
|
||||
```
|
||||
┌───────────┐
|
||||
│ │
|
||||
│ CPU │───┐
|
||||
│ │ │
|
||||
└───────────┘ │
|
||||
│
|
||||
┌───────────┐ │ ┌───────────┐
|
||||
│ │ │ │ │
|
||||
│ Memory │───┤ ┌──▶│ InfluxDB │
|
||||
│ │ │ │ │ │
|
||||
└───────────┘ │ ┌─────────────┐ ┌─────────────┐ │ └───────────┘
|
||||
│ │ │ │Aggregate │ │
|
||||
┌───────────┐ │ │Process │ │ - mean │ │ ┌───────────┐
|
||||
│ │ │ │ - transform │ │ - quantiles │ │ │ │
|
||||
│ MySQL │───┼──▶ │ - decorate │────▶│ - min/max │───┼──▶│ File │
|
||||
│ │ │ │ - filter │ │ - count │ │ │ │
|
||||
└───────────┘ │ │ │ │ │ │ └───────────┘
|
||||
│ └─────────────┘ └─────────────┘ │
|
||||
┌───────────┐ │ │ ┌───────────┐
|
||||
│ │ │ │ │ │
|
||||
│ SNMP │───┤ └──▶│ Kafka │
|
||||
│ │ │ │ │
|
||||
└───────────┘ │ └───────────┘
|
||||
│
|
||||
┌───────────┐ │
|
||||
│ │ │
|
||||
│ Docker │───┘
|
||||
│ │
|
||||
└───────────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
graph TD
|
||||
Process[Process<br/> - transform<br/> - decorate<br/> - filter]
|
||||
Aggregate[Aggregate<br/> - transform<br/> - decorate<br/> - filter]
|
||||
|
||||
CPU --> Process
|
||||
Memory --> Process
|
||||
MySQL --> Process
|
||||
SNMP --> Process
|
||||
Docker --> Process
|
||||
Process --> Aggregate
|
||||
Aggregate --> InfluxDB
|
||||
Aggregate --> File
|
||||
Aggregate --> Kafka
|
||||
|
||||
style Process text-align:left
|
||||
style Aggregate text-align:left
|
||||
{{< /diagram >}}
|
||||
|
||||
**Processor plugins** process metrics as they pass through and immediately emit
|
||||
results based on the values they process. For example, this could be printing
|
||||
|
|
|
@ -10,37 +10,24 @@ menu:
|
|||
|
||||
Besides the input plugins and output plugins, Telegraf includes aggregator and processor plugins, which are used to aggregate and process metrics as they pass through Telegraf.
|
||||
|
||||
```
|
||||
┌───────────┐
|
||||
│ │
|
||||
│ CPU │───┐
|
||||
│ │ │
|
||||
└───────────┘ │
|
||||
│
|
||||
┌───────────┐ │ ┌───────────┐
|
||||
│ │ │ │ │
|
||||
│ Memory │───┤ ┌──▶│ InfluxDB │
|
||||
│ │ │ │ │ │
|
||||
└───────────┘ │ ┌─────────────┐ ┌─────────────┐ │ └───────────┘
|
||||
│ │ │ │Aggregate │ │
|
||||
┌───────────┐ │ │Process │ │ - mean │ │ ┌───────────┐
|
||||
│ │ │ │ - transform │ │ - quantiles │ │ │ │
|
||||
│ MySQL │───┼──▶ │ - decorate │────▶│ - min/max │───┼──▶│ File │
|
||||
│ │ │ │ - filter │ │ - count │ │ │ │
|
||||
└───────────┘ │ │ │ │ │ │ └───────────┘
|
||||
│ └─────────────┘ └─────────────┘ │
|
||||
┌───────────┐ │ │ ┌───────────┐
|
||||
│ │ │ │ │ │
|
||||
│ SNMP │───┤ └──▶│ Kafka │
|
||||
│ │ │ │ │
|
||||
└───────────┘ │ └───────────┘
|
||||
│
|
||||
┌───────────┐ │
|
||||
│ │ │
|
||||
│ Docker │───┘
|
||||
│ │
|
||||
└───────────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
graph TD
|
||||
Process[Process<br/> - transform<br/> - decorate<br/> - filter]
|
||||
Aggregate[Aggregate<br/> - transform<br/> - decorate<br/> - filter]
|
||||
|
||||
CPU --> Process
|
||||
Memory --> Process
|
||||
MySQL --> Process
|
||||
SNMP --> Process
|
||||
Docker --> Process
|
||||
Process --> Aggregate
|
||||
Aggregate --> InfluxDB
|
||||
Aggregate --> File
|
||||
Aggregate --> Kafka
|
||||
|
||||
style Process text-align:left
|
||||
style Aggregate text-align:left
|
||||
{{< /diagram >}}
|
||||
|
||||
**Processor plugins** process metrics as they pass through and immediately emit
|
||||
results based on the values they process. For example, this could be printing
|
||||
|
|
|
@ -10,37 +10,24 @@ menu:
|
|||
|
||||
Besides the input plugins and output plugins, Telegraf includes aggregator and processor plugins, which are used to aggregate and process metrics as they pass through Telegraf.
|
||||
|
||||
```
|
||||
┌───────────┐
|
||||
│ │
|
||||
│ CPU │───┐
|
||||
│ │ │
|
||||
└───────────┘ │
|
||||
│
|
||||
┌───────────┐ │ ┌───────────┐
|
||||
│ │ │ │ │
|
||||
│ Memory │───┤ ┌──▶│ InfluxDB │
|
||||
│ │ │ │ │ │
|
||||
└───────────┘ │ ┌─────────────┐ ┌─────────────┐ │ └───────────┘
|
||||
│ │ │ │Aggregate │ │
|
||||
┌───────────┐ │ │Process │ │ - mean │ │ ┌───────────┐
|
||||
│ │ │ │ - transform │ │ - quantiles │ │ │ │
|
||||
│ MySQL │───┼──▶ │ - decorate │────▶│ - min/max │───┼──▶│ File │
|
||||
│ │ │ │ - filter │ │ - count │ │ │ │
|
||||
└───────────┘ │ │ │ │ │ │ └───────────┘
|
||||
│ └─────────────┘ └─────────────┘ │
|
||||
┌───────────┐ │ │ ┌───────────┐
|
||||
│ │ │ │ │ │
|
||||
│ SNMP │───┤ └──▶│ Kafka │
|
||||
│ │ │ │ │
|
||||
└───────────┘ │ └───────────┘
|
||||
│
|
||||
┌───────────┐ │
|
||||
│ │ │
|
||||
│ Docker │───┘
|
||||
│ │
|
||||
└───────────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
graph TD
|
||||
Process[Process<br/> - transform<br/> - decorate<br/> - filter]
|
||||
Aggregate[Aggregate<br/> - transform<br/> - decorate<br/> - filter]
|
||||
|
||||
CPU --> Process
|
||||
Memory --> Process
|
||||
MySQL --> Process
|
||||
SNMP --> Process
|
||||
Docker --> Process
|
||||
Process --> Aggregate
|
||||
Aggregate --> InfluxDB
|
||||
Aggregate --> File
|
||||
Aggregate --> Kafka
|
||||
|
||||
style Process text-align:left
|
||||
style Aggregate text-align:left
|
||||
{{< /diagram >}}
|
||||
|
||||
**Processor plugins** process metrics as they pass through and immediately emit
|
||||
results based on the values they process. For example, this could be printing
|
||||
|
|
|
@ -10,37 +10,24 @@ menu:
|
|||
|
||||
Besides the input plugins and output plugins, Telegraf includes aggregator and processor plugins, which are used to aggregate and process metrics as they pass through Telegraf.
|
||||
|
||||
```
|
||||
┌───────────┐
|
||||
│ │
|
||||
│ CPU │───┐
|
||||
│ │ │
|
||||
└───────────┘ │
|
||||
│
|
||||
┌───────────┐ │ ┌───────────┐
|
||||
│ │ │ │ │
|
||||
│ Memory │───┤ ┌──▶│ InfluxDB │
|
||||
│ │ │ │ │ │
|
||||
└───────────┘ │ ┌─────────────┐ ┌─────────────┐ │ └───────────┘
|
||||
│ │ │ │Aggregate │ │
|
||||
┌───────────┐ │ │Process │ │ - mean │ │ ┌───────────┐
|
||||
│ │ │ │ - transform │ │ - quantiles │ │ │ │
|
||||
│ MySQL │───┼──▶ │ - decorate │────▶│ - min/max │───┼──▶│ File │
|
||||
│ │ │ │ - filter │ │ - count │ │ │ │
|
||||
└───────────┘ │ │ │ │ │ │ └───────────┘
|
||||
│ └─────────────┘ └─────────────┘ │
|
||||
┌───────────┐ │ │ ┌───────────┐
|
||||
│ │ │ │ │ │
|
||||
│ SNMP │───┤ └──▶│ Kafka │
|
||||
│ │ │ │ │
|
||||
└───────────┘ │ └───────────┘
|
||||
│
|
||||
┌───────────┐ │
|
||||
│ │ │
|
||||
│ Docker │───┘
|
||||
│ │
|
||||
└───────────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
graph TD
|
||||
Process[Process<br/> - transform<br/> - decorate<br/> - filter]
|
||||
Aggregate[Aggregate<br/> - transform<br/> - decorate<br/> - filter]
|
||||
|
||||
CPU --> Process
|
||||
Memory --> Process
|
||||
MySQL --> Process
|
||||
SNMP --> Process
|
||||
Docker --> Process
|
||||
Process --> Aggregate
|
||||
Aggregate --> InfluxDB
|
||||
Aggregate --> File
|
||||
Aggregate --> Kafka
|
||||
|
||||
style Process text-align:left
|
||||
style Aggregate text-align:left
|
||||
{{< /diagram >}}
|
||||
|
||||
**Processor plugins** process metrics as they pass through and immediately emit
|
||||
results based on the values they process. For example, this could be printing
|
||||
|
|
|
@ -10,37 +10,24 @@ menu:
|
|||
|
||||
Besides the input plugins and output plugins, Telegraf includes aggregator and processor plugins, which are used to aggregate and process metrics as they pass through Telegraf.
|
||||
|
||||
```
|
||||
┌───────────┐
|
||||
│ │
|
||||
│ CPU │───┐
|
||||
│ │ │
|
||||
└───────────┘ │
|
||||
│
|
||||
┌───────────┐ │ ┌───────────┐
|
||||
│ │ │ │ │
|
||||
│ Memory │───┤ ┌──▶│ InfluxDB │
|
||||
│ │ │ │ │ │
|
||||
└───────────┘ │ ┌─────────────┐ ┌─────────────┐ │ └───────────┘
|
||||
│ │ │ │Aggregate │ │
|
||||
┌───────────┐ │ │Process │ │ - mean │ │ ┌───────────┐
|
||||
│ │ │ │ - transform │ │ - quantiles │ │ │ │
|
||||
│ MySQL │───┼──▶ │ - decorate │────▶│ - min/max │───┼──▶│ File │
|
||||
│ │ │ │ - filter │ │ - count │ │ │ │
|
||||
└───────────┘ │ │ │ │ │ │ └───────────┘
|
||||
│ └─────────────┘ └─────────────┘ │
|
||||
┌───────────┐ │ │ ┌───────────┐
|
||||
│ │ │ │ │ │
|
||||
│ SNMP │───┤ └──▶│ Kafka │
|
||||
│ │ │ │ │
|
||||
└───────────┘ │ └───────────┘
|
||||
│
|
||||
┌───────────┐ │
|
||||
│ │ │
|
||||
│ Docker │───┘
|
||||
│ │
|
||||
└───────────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
graph TD
|
||||
Process[Process<br/> - transform<br/> - decorate<br/> - filter]
|
||||
Aggregate[Aggregate<br/> - transform<br/> - decorate<br/> - filter]
|
||||
|
||||
CPU --> Process
|
||||
Memory --> Process
|
||||
MySQL --> Process
|
||||
SNMP --> Process
|
||||
Docker --> Process
|
||||
Process --> Aggregate
|
||||
Aggregate --> InfluxDB
|
||||
Aggregate --> File
|
||||
Aggregate --> Kafka
|
||||
|
||||
style Process text-align:left
|
||||
style Aggregate text-align:left
|
||||
{{< /diagram >}}
|
||||
|
||||
**Processor plugins** process metrics as they pass through and immediately emit
|
||||
results based on the values they process. For example, this could be printing
|
||||
|
|
|
@ -10,37 +10,24 @@ menu:
|
|||
|
||||
Besides the input plugins and output plugins, Telegraf includes aggregator and processor plugins, which are used to aggregate and process metrics as they pass through Telegraf.
|
||||
|
||||
```
|
||||
┌───────────┐
|
||||
│ │
|
||||
│ CPU │───┐
|
||||
│ │ │
|
||||
└───────────┘ │
|
||||
│
|
||||
┌───────────┐ │ ┌───────────┐
|
||||
│ │ │ │ │
|
||||
│ Memory │───┤ ┌──▶│ InfluxDB │
|
||||
│ │ │ │ │ │
|
||||
└───────────┘ │ ┌─────────────┐ ┌─────────────┐ │ └───────────┘
|
||||
│ │ │ │Aggregate │ │
|
||||
┌───────────┐ │ │Process │ │ - mean │ │ ┌───────────┐
|
||||
│ │ │ │ - transform │ │ - quantiles │ │ │ │
|
||||
│ MySQL │───┼──▶ │ - decorate │────▶│ - min/max │───┼──▶│ File │
|
||||
│ │ │ │ - filter │ │ - count │ │ │ │
|
||||
└───────────┘ │ │ │ │ │ │ └───────────┘
|
||||
│ └─────────────┘ └─────────────┘ │
|
||||
┌───────────┐ │ │ ┌───────────┐
|
||||
│ │ │ │ │ │
|
||||
│ SNMP │───┤ └──▶│ Kafka │
|
||||
│ │ │ │ │
|
||||
└───────────┘ │ └───────────┘
|
||||
│
|
||||
┌───────────┐ │
|
||||
│ │ │
|
||||
│ Docker │───┘
|
||||
│ │
|
||||
└───────────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
graph TD
|
||||
Process[Process<br/> - transform<br/> - decorate<br/> - filter]
|
||||
Aggregate[Aggregate<br/> - transform<br/> - decorate<br/> - filter]
|
||||
|
||||
CPU --> Process
|
||||
Memory --> Process
|
||||
MySQL --> Process
|
||||
SNMP --> Process
|
||||
Docker --> Process
|
||||
Process --> Aggregate
|
||||
Aggregate --> InfluxDB
|
||||
Aggregate --> File
|
||||
Aggregate --> Kafka
|
||||
|
||||
style Process text-align:left
|
||||
style Aggregate text-align:left
|
||||
{{< /diagram >}}
|
||||
|
||||
**Processor plugins** process metrics as they pass through and immediately emit
|
||||
results based on the values they process. For example, this could be printing
|
||||
|
|
|
@ -10,37 +10,24 @@ menu:
|
|||
|
||||
Besides the input plugins and output plugins, Telegraf includes aggregator and processor plugins, which are used to aggregate and process metrics as they pass through Telegraf.
|
||||
|
||||
```
|
||||
┌───────────┐
|
||||
│ │
|
||||
│ CPU │───┐
|
||||
│ │ │
|
||||
└───────────┘ │
|
||||
│
|
||||
┌───────────┐ │ ┌───────────┐
|
||||
│ │ │ │ │
|
||||
│ Memory │───┤ ┌──▶│ InfluxDB │
|
||||
│ │ │ │ │ │
|
||||
└───────────┘ │ ┌─────────────┐ ┌─────────────┐ │ └───────────┘
|
||||
│ │ │ │Aggregate │ │
|
||||
┌───────────┐ │ │Process │ │ - mean │ │ ┌───────────┐
|
||||
│ │ │ │ - transform │ │ - quantiles │ │ │ │
|
||||
│ MySQL │───┼──▶│ - decorate │────▶│ - min/max │───┼──▶│ File │
|
||||
│ │ │ │ - filter │ │ - count │ │ │ │
|
||||
└───────────┘ │ │ │ │ │ │ └───────────┘
|
||||
│ └─────────────┘ └─────────────┘ │
|
||||
┌───────────┐ │ │ ┌───────────┐
|
||||
│ │ │ │ │ │
|
||||
│ SNMP │───┤ └──▶│ Kafka │
|
||||
│ │ │ │ │
|
||||
└───────────┘ │ └───────────┘
|
||||
│
|
||||
┌───────────┐ │
|
||||
│ │ │
|
||||
│ Docker │───┘
|
||||
│ │
|
||||
└───────────┘
|
||||
```
|
||||
{{< diagram >}}
|
||||
graph TD
|
||||
Process[Process<br/> - transform<br/> - decorate<br/> - filter]
|
||||
Aggregate[Aggregate<br/> - transform<br/> - decorate<br/> - filter]
|
||||
|
||||
CPU --> Process
|
||||
Memory --> Process
|
||||
MySQL --> Process
|
||||
SNMP --> Process
|
||||
Docker --> Process
|
||||
Process --> Aggregate
|
||||
Aggregate --> InfluxDB
|
||||
Aggregate --> File
|
||||
Aggregate --> Kafka
|
||||
|
||||
style Process text-align:left
|
||||
style Aggregate text-align:left
|
||||
{{< /diagram >}}
|
||||
|
||||
**Processor plugins** process metrics as they pass through and immediately emit
|
||||
results based on the values they process. For example, this could be printing
|
||||
|
|
|
@ -19,3 +19,22 @@
|
|||
|
||||
<!-- Load footer.js -->
|
||||
<script type="text/javascript" src="{{ $footerjs.RelPermalink }}" ></script>
|
||||
|
||||
{{ if .Page.HasShortcode "diagram" }}
|
||||
<!-- Load mermaid.js for diagrams -->
|
||||
<script src="https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js"></script>
|
||||
<script>
|
||||
mermaid.initialize({
|
||||
startOnLoad:true,
|
||||
mermaid: {
|
||||
callback:function(id) {
|
||||
$('.mermaid').css('opacity', 1);
|
||||
}
|
||||
},
|
||||
themeVariables: {
|
||||
fontFamily: "Rubik",
|
||||
fontSize: '18px',
|
||||
}
|
||||
})
|
||||
</script>
|
||||
{{ end }}
|
|
@ -0,0 +1,3 @@
|
|||
<div class="mermaid">
|
||||
{{.Inner}}
|
||||
</div>
|
Loading…
Reference in New Issue