c0c002133 · cryptotaxi247/netdata-1

@@ -1,172 +0,0 @@

1 -<!--startmeta

2 -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/exporting/graphite/integrations/influxdb.md"

3 -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/exporting/graphite/metadata.yaml"

4 -sidebar_label: "InfluxDB"

5 -learn_status: "Published"

6 -learn_rel_path: "Exporting Metrics"

7 -message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE EXPORTER'S metadata.yaml FILE"

8 -endmeta-->

9 -

10 -# InfluxDB

11 -

12 -

13 -<img src="https://netdata.cloud/img/influxdb.svg" width="150"/>

14 -

15 -

16 -Use the Graphite connector for the exporting engine to archive your Netdata metrics to Graphite providers for long-term storage,

17 -further analysis, or correlation with data from other sources.

18 -

19 -

20 -

21 -<img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" />

22 -

23 -## Setup

24 -

25 -### Prerequisites

26 -

27 -####

28 -

29 -- You have already installed Netdata and Graphite.

30 -

31 -

32 -

33 -### Configuration

34 -

35 -#### File

36 -

37 -The configuration file name for this integration is `exporting.conf`.

38 -

39 -

40 -You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the

41 -Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).

42 -

43 -```bash

44 -cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata

45 -sudo ./edit-config exporting.conf

46 -```

47 -#### Options

48 -

49 -The following options can be defined for this exporter.

50 -

51 -<details open><summary>Config options</summary>

52 -

54 -|:----|:-----------|:-------|:--------:|

55 -| enabled | Enables or disables an exporting connector instance (yes/no). | no | yes |

56 -| destination | Accepts a space separated list of hostnames, IPs (IPv4 and IPv6) and ports to connect to. Netdata will use the first available to send the metrics. | no | yes |

59 -| data source | Selects the kind of data that will be sent to the external database. (as collected/average/sum) | | no |

62 -| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |

63 -| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |

64 -| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |

65 -| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |

66 -| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |

67 -| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |

68 -| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |

69 -| send automatic labels | Controls if automatically created labels, like `_os_name` or `_architecture` should be sent to the external database (yes/no). | | no |

70 -

71 -##### destination

72 -

73 -The format of each item in this list, is: [PROTOCOL:]IP[:PORT].

74 -- PROTOCOL can be udp or tcp. tcp is the default and only supported by the current exporting engine.

75 -- IP can be XX.XX.XX.XX (IPv4), or [XX:XX...XX:XX] (IPv6). For IPv6 you can to enclose the IP in [] to separate it from the port.

76 -- PORT can be a number of a service name. If omitted, the default port for the exporting connector will be used.

77 -

78 -Example IPv4:

79 - ```yaml

80 - destination = 10.11.14.2:2003 10.11.14.3:4242 10.11.14.4:2003

81 - ```

82 -Example IPv6 and IPv4 together:

83 -```yaml

84 -destination = [ffff:...:0001]:2003 10.11.12.1:2003

85 -```

86 -When multiple servers are defined, Netdata will try the next one when the previous one fails.

87 -

88 -

89 -##### update every

90 -

91 -Netdata will add some randomness to this number, to prevent stressing the external server when many Netdata servers

92 -send data to the same database. This randomness does not affect the quality of the data, only the time they are sent.

93 -

94 -

95 -##### buffer on failures

96 -

97 -If the server fails to receive the data after that many failures, data loss on the connector instance is expected (Netdata will also log it).

98 -

99 -

100 -##### send hosts matching

101 -

102 -Includes one or more space separated patterns, using * as wildcard (any number of times within each pattern).

103 -The patterns are checked against the hostname (the localhost is always checked as localhost), allowing us to

104 -filter which hosts will be sent to the external database when this Netdata is a central Netdata aggregating multiple hosts.

105 -

106 -A pattern starting with `!` gives a negative match. So to match all hosts named `*db*` except hosts containing `*child*`,

107 -use `!*child* *db*` (so, the order is important: the first pattern matching the hostname will be used - positive or negative).

108 -

109 -

110 -##### send charts matching

111 -

112 -A pattern starting with ! gives a negative match. So to match all charts named apps.* except charts ending in *reads,

113 -use !*reads apps.* (so, the order is important: the first pattern matching the chart id or the chart name will be used,

114 -positive or negative). There is also a URL parameter filter that can be used while querying allmetrics. The URL parameter

115 -has a higher priority than the configuration option.

116 -

117 -

118 -##### send names instead of ids

119 -

120 -Netdata supports names and IDs for charts and dimensions. Usually IDs are unique identifiers as read by the system and names

121 -are human friendly labels (also unique). Most charts and metrics have the same ID and name, but in several cases they are

122 -different : disks with device-mapper, interrupts, QoS classes, statsd synthetic charts, etc.

123 -

124 -

125 -</details>

126 -

127 -#### Examples

128 -

129 -##### Example configuration

130 -

131 -Basic configuration

132 -

133 -```yaml

134 -[graphite:netdata]

135 - enabled = yes

136 - destination = localhost:2003

137 -

138 -```

139 -##### Configuration with HTTPS and HTTP authentication

140 -

141 -Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.

142 -

143 -```yaml

144 -[graphite:netdata]

145 - enabled = yes

146 - destination = localhost:2003

147 - username = my_username

148 - password = my_password

149 -

150 -```

151 -##### Detailed Configuration for a remote, secure host

152 -

153 -Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.

154 -

155 -```yaml

156 -[graphite:https:netdata]

157 - enabled = yes

158 - username = my_username

159 - password = my_password

160 - destination = 10.10.1.114:2003

161 - # data source = average

162 - # prefix = netdata

163 - # hostname = my_hostname

164 - # update every = 10

165 - # buffer on failures = 10

166 - # timeout ms = 20000

167 - # send names instead of ids = yes

168 - # send charts matching = *

169 - # send hosts matching = localhost *

170 -

171 -```

172 -

Regenerate integrations docs (#19634)