Configure Data Nodes
Data 节点配置设置
- 全局设置
- Meta 设置
[meta] - Data 设置
[data] -
Coordinator 设置
[coordinator](包括 InfluxQL 查询控制) - Hinted Handoff 设置
[hinted-handoff] - Anti-Entropy 设置
[anti-entropy] - Retention 设置
[retention] - Shard precreation 设置
[shard-precreation] - Monitor 设置
[monitor] - HTTP 设置
[http]) - Logging 设置
[logging]) - Subscriber 设置
[subscriber]) - Graphite 设置
[graphite]) - Collectd 设置
[collectd]) - OpenTSDB 设置
[opentsdb]) - UDP 设置
[udp]) - Continuous queries 设置
[continuous-queries]) - TLS 设置
[tls]
每 24 小时将数据报告打印输出到日志中。每个报告包括一个随机生成的标识符、操作系统、架构、InfluxDB Cluster 版本以及 database、measurement 和唯一 series 的数量。将此选项更改为 true 以禁用报告。
环境变量: INFLUXDB_REPORTING_DISABLED
RPC 服务用于节点间通信、备份和恢复的 TCP 绑定地址。
环境变量: INFLUXDB_BIND_ADDRESS
Data 节点的主机名。这必须可被集群的所有其它成员解析和访问。
环境变量: INFLUXDB_HOSTNAME
将此节点的内部状态更新至集群的频率。
环境变量: INFLUXDB_GOSSIP_FREQUENCY
Settings related to how the data nodes interact with the meta nodes.
The directory where the cluster metadata is stored.
Note: Data nodes do require a local meta directory.
环境变量: INFLUXDB_META_DIR
Whether to use TLS when connecting to meta nodes. Set to true to if https-enabled is set to true.
环境变量: INFLUXDB_META_META_TLS_ENABLED
Allows insecure TLS connections to meta nodes. This is useful when testing with self-signed certificates.
Set to true to allow the data node to accept self-signed certificates if https-enabled is set to true.
环境变量: INFLUXDB_META_META_INSECURE_TLS
Set to true if auth-enabled is set to true in the meta node configuration files. For JWT authentication, also see the meta-internal-shared-secret configuration option.
环境变量: INFLUXDB_META_META_AUTH_ENABLED
The shared secret used by the internal API for JWT authentication between InfluxDB nodes. This value must be the same as the internal-shared-secret specified in the meta node configuration file.
环境变量: INFLUXDB_META_META_INTERNAL_SHARED_SECRET
Automatically creates a default retention policy (RP) when the system creates a database. The default RP (autogen) has an infinite duration, a shard group duration of seven days, and a replication factor set to the number of data nodes in the cluster. The system targets the autogen RP when a write or query does not specify an RP. Set this option to false to prevent the system from creating the autogen RP when the system creates a database.
注意: 此设置已无实际作用，它将在未来的版本中删除。要禁用保留策略自动创建，请在 Meta 节点配置文件中设置
retention-autocreate为false。
环境变量: INFLUXDB_META_RETENTION_AUTOCREATE
Whether log messages are printed for the meta service.
环境变量: INFLUXDB_META_LOGGING_ENABLED
Controls where the actual shard data for InfluxDB lives and how it is compacted from the WAL. “dir” may need to be changed to a suitable place for your system. The defaults should work for most systems.
For InfluxDB OSS, see the OSS documentation.
The directory where the TSM storage engine stores TSM (read-optimized) files.
环境变量: INFLUXDB_DATA_DIR
The directory where the TSM storage engine stores WAL (write-optimized) files.
环境变量: INFLUXDB_DATA_WAL_DIR
Trace logging provides more verbose output around the TSM engine. Turning this on can provide more useful output for debugging TSM engine issues.
环境变量: INFLUXDB_DATA_TRACE_LOGGING_ENABLED
Whether queries should be logged before execution. Very useful for troubleshooting, but will log any sensitive data contained within a query.
环境变量: INFLUXDB_DATA_QUERY_LOG_ENABLED
The amount of time that a write waits before fsyncing. Use a duration greater than 0 to batch up multiple fsync calls. This is useful for slower disks or when experiencing WAL write contention. A value of 0s fsyncs every write to the WAL. InfluxData recommends values ranging from 0ms to 100ms for non-SSD disks.
环境变量: INFLUXDB_DATA_WAL_FSYNC_DELAY
The maximum size a shard cache can reach before it starts rejecting writes.
环境变量: INFLUXDB_DATA_CACHE_MAX_MEMORY_SIZE
The size at which the TSM engine will snapshot the cache and write it to a TSM file, freeing up memory.
环境变量: INFLUXDB_DATA_CACHE_SNAPSHOT_MEMORY_SIZE
The length of time at which the TSM engine will snapshot the cache and write it to a new TSM file if the shard hasn’t received writes or deletes.
环境变量: INFLUXDB_DATA_CACHE_SNAPSHOT_WRITE_COLD_DURATION
The maximum number of concurrent full and level compactions that can run at one time.
A value of 0 (unlimited compactions) results in 50% of runtime.GOMAXPROCS(0) used at runtime, so when 50% of the CPUs aren’t available, compactions are limited. Any number greater than 0 limits compactions to that value.
This setting does not apply to cache snapshotting.
环境变量: INFLUXDB_DATA_CACHE_MAX_CONCURRENT_COMPACTIONS
The maximum number of simultaneous DELETE calls on a shard.
The default is 1, and should be left unchanged for most users.
环境变量: INFLUXDB_MAX_CONCURRENT_DELETES
The maximum number of bytes per seconds TSM compactions write to disk. Default is "48m" (48 million). Note that short bursts are allowed to happen at a possibly larger value, set by compact-throughput-burst.
环境变量: INFLUXDB_DATA_COMPACT_THROUGHPUT
The maximum number of bytes per seconds TSM compactions write to disk during brief bursts. Default is "48m" (48 million).
环境变量: INFLUXDB_DATA_COMPACT_THROUGHPUT_BURST
The duration at which the TSM engine will compact all TSM files in a shard if it hasn’t received a write or delete.
环境变量: INFLUXDB_DATA_COMPACT_FULL_WRITE_COLD_DURATION
The type of shard index to use for new shards. The default (inmem) is to use an in-memory index that is recreated at startup. A value of tsi1 will use a disk-based index that supports higher cardinality datasets. Value should be enclosed in double quotes.
环境变量: INFLUXDB_DATA_INDEX_VERSION
The maximum number of series allowed per database before writes are dropped. The default setting is 1000000 (one million). Change the setting to 0 to allow an unlimited number of series per database.
If a point causes the number of series in a database to exceed max-series-per-database, InfluxDB will not write the point, and it returns a 500 with the following error:
{"error":"max series per database exceeded: <series>"}Note: Any existing databases with a series count that exceeds
max-series-per-databasewill continue to accept writes to existing series, but writes that create a new series will fail.
环境变量: INFLUXDB_DATA_MAX_SERIES_PER_DATABASE
The maximum number of tag values allowed per tag key. The default value is 100000 (one hundred thousand). Change the setting to 0 to allow an unlimited number of tag values per tag key. If a tag value causes the number of tag values of a tag key to exceed max-values-per-tag, then InfluxDB will not write the point, and it returns a partial write error.
Any existing tag keys with tag values that exceed max-values-per-tag will continue to accept writes, but writes that create a new tag value will fail.
环境变量: INFLUXDB_DATA_MAX_VALUES_PER_TAG
The threshold, in bytes, when an index write-ahead log (WAL) file will compact into an index file. Lower sizes will cause log files to be compacted more quickly and result in lower heap usage at the expense of write throughput. Higher sizes will be compacted less frequently, store more series in-memory, and provide higher write throughput. Valid size suffixes are k, m, or g (case-insensitive, 1024 = 1k). Values without a size suffix are in bytes.
环境变量: INFLUXDB_DATA_MAX_INDEX_LOG_FILE_SIZE
The size of the internal cache used in the TSI index to store previously calculated series results. Cached results will be returned quickly from the cache rather than needing to be recalculated when a subsequent query with a matching tag key-value predicate is executed. Setting this value to 0 will disable the cache, which may lead to query performance issues. This value should only be increased if it is known that the set of regularly used tag key-value predicates across all measurements for a database is larger than 100. An increase in cache size may lead to an increase in heap usage.
环境变量: INFLUXDB_DATA_SERIES_ID_SET_CACHE_SIZE
Settings related to how data nodes interact with each other, how data is shared across shards, and how InfluxQL queries are managed.
An InfluxDB Enterprise cluster uses remote procedure calls (RPCs) for inter-node communication. An RPC connection pool manages the stream connections and efficiently uses system resources. InfluxDB data nodes multiplex RPC streams over a single TCP connection to avoid the overhead of frequently establishing and destroying TCP connections and exhausting ephemeral ports. Typically, a data node establishes a single, persistent TCP connection to each of the other data nodes to perform most RPC requests. In special circumstances, for example, when copying shards, a single-use TCP connection may be used.
For information on InfluxDB _internal measurement statistics related to clusters, RPCs, and shards, see Measurements for monitoring InfluxDB OSS and InfluxDB Enterprise (_inernal).
The duration for which the meta node waits for a connection to a remote data node before the meta node attempts to connect to a different remote data node. This setting applies to queries only.
环境变量: INFLUXDB_COORDINATOR_DIAL_TIMEOUT
The maximum time that a TCP connection to another data node remains idle in the connection pool. When the connection is idle longer than the specified duration, the inactive connection is reaped — retired or recycled — so that the connection pool is not filled with inactive connections. Reaping idle connections minimizes inactive connections, decreases system load, and prevents system failure.
环境变量: INFLUXDB_COORDINATOR_POOL_MAX_IDLE_TIME
The maximum number of idle RPC stream connections to retain in an idle pool between two nodes. When a new RPC request is issued, a connection is temporarily pulled from the idle pool, used, and then returned. If an idle pool is full and a stream connection is no longer required, the system closes the stream connection and resources become available. The number of active streams can exceed the maximum number of idle pool connections, but are not returned to the idle pool when released. Creating streams are relatively inexpensive operations to perform, so it is unlikely that changing this value will measurably improve performance between two nodes.
环境变量: INFLUXDB_COORDINATOR_POOL_MAX_IDLE_STREAMS
By default, this option is set to false and writes are processed in the order that they are received. This means if any points are in the hinted handoff (HH) queue for a shard, all incoming points must go into the HH queue.
If true, writes may process in a different order than they were received. This can reduce the time required to drain the HH queue and increase throughput during recovery.
Do not enable if your use case involves updating points, which may cause points to be overwritten. To overwrite an existing point, the measurement name, tag keys and values (if the point includes tags), field keys, and timestamp all have to be the same as a previous write.
For example, if you have two points with the same measurement (cpu), field key (v), and timestamp (1234), the following could happen:
Point 1 (cpu v=1.0 1234) arrives at node1, attempts to replicate on node2, and finds node2 is down, so point 1 goes to the local HH queue. Now, node2 comes back online and point 2 cpu v=20. 1234 arrives at node1, overwrites point 1, and is written to node2 (bypassing the HH queue). Because the point 2 arrives at node2 before point 1, point 2 is stored before point 1.
环境变量: INFLUXDB_COORDINATOR_ALLOW_OUT_OF_ORDER
The default timeout set on shard readers. The time in which a query connection must return its response after which the system returns an error.
环境变量: INFLUXDB_COORDINATOR_SHARD_READER_TIMEOUT
Determines whether data nodes use HTTPS to communicate with each other.
The SSL certificate to use when HTTPS is enabled.
The certificate should be a PEM-encoded bundle of the certificate and key.
If it is just the certificate, a key must be specified in https-private-key.
Use a separate private key location.
Whether data nodes will skip certificate validation communicating with each other over HTTPS. This is useful when testing with self-signed certificates.
Enables cluster trace logging. Set to true to enable logging of cluster communications. Enable this setting to verify connectivity issues between data nodes.
环境变量: INFLUXDB_COORDINATOR_CLUSTER_TRACING
The duration a write request waits until a “timeout” error is returned to the caller. The default value is 10 seconds.
环境变量: INFLUXDB_COORDINATOR_WRITE_TIMEOUT
The maximum number of concurrent queries allowed to be executing at one time.
If a query is executed and exceeds this limit, an error is returned to the caller.
This limit can be disabled by setting it to 0.
环境变量: INFLUXDB_COORDINATOR_MAX_CONCURRENT_QUERIES
The maximum time a query is allowed to execute before being killed by the system. This limit can help prevent run away queries. Setting the value to 0 disables the limit.
环境变量: INFLUXDB_COORDINATOR_QUERY_TIMEOUT
The time threshold when a query will be logged as a slow query.
This limit can be set to help discover slow or resource intensive queries.
Setting the value to 0 disables the slow query logging.
环境变量: INFLUXDB_COORDINATOR_LOG_QUERIES_AFTER
Set to true to log queries that are killed due to exceeding the query-timeout. The default setting (false) will not log timedout queries.
环境变量: INFLUXDB_COORDINATOR_LOG_TIMEDOUT_QUERIES
The maximum number of points a SELECT statement can process.
A value of 0 will make the maximum point count unlimited.
环境变量: INFLUXDB_COORDINATOR_MAX_SELECT_POINT
The maximum number of series a SELECT can run. A value of 0 will make the maximum series count unlimited.
环境变量: INFLUXDB_COORDINATOR_MAX_SELECT_SERIES
The maximum number of group by time buckets a SELECT can create.
A value of 0 will make the maximum number of buckets unlimited.
环境变量: INFLUXDB_COORDINATOR_MAX_SELECT_BUCKETS
Set to true to print all running queries to the log when a data node process receives a SIGTERM (for example, a k8s process exceeds the container memory limit or the process is terminated).
环境变量: INFLUXDB_COORDINATOR_TERMINATION_QUERY_LOG
Controls the hinted handoff (HH) queue, which allows data nodes to temporarily cache writes destined for another data node when that data node is unreachable.
注意：尚不支持
The maximum number of bytes to write to a shard in a single request.
环境变量: INFLUXDB_HINTED_HANDOFF_BATCH_SIZE
The maximum number of incoming pending writes allowed in the hinted handoff queue.
环境变量: INFLUXDB_HINTED_HANDOFF_MAX_WRITES_PENDING
The hinted handoff directory where the durable queue will be stored on disk.
环境变量: INFLUXDB_HINTED_HANDOFF_DIR
Set to false to disable hinted handoff. Disabling hinted handoff is not recommended and can lead to data loss if another data node is unreachable for any length of time.
环境变量: INFLUXDB_HINTED_HANDOFF_ENABLED
The maximum size of the hinted handoff queue in bytes. Each queue is for one and only one other data node in the cluster. If there are N data nodes in the cluster, each data node may have up to N-1 hinted handoff queues.
环境变量: INFLUXDB_HINTED_HANDOFF_MAX_SIZE
The time interval that writes sit in the queue before they are purged. The time is determined by how long the batch has been in the queue, not by the timestamps in the data. If another data node is unreachable for more than the max-age it can lead to data loss.
环境变量: INFLUXDB_HINTED_HANDOFF_MAX_AGE
注意：尚不支持
The maximum number of hinted handoff blocks that the source data node attempts to write to each destination data node. Hinted handoff blocks are sets of data that belong to the same shard and have the same destination data node.
If retry-concurrency is 20 and the source data node’s hinted handoff has 25 blocks for destination data node A, then the source data node attempts to concurrently write 20 blocks to node A. If retry-concurrency is 20 and the source data node’s hinted handoff has 25 blocks for destination data node A and 30 blocks for destination data node B, then the source data node attempts to concurrently write 20 blocks to node A and 20 blocks to node B. If the source data node successfully writes 20 blocks to a destination data node, it continues to write the remaining hinted handoff data to that destination node in sets of 20 blocks.
If the source data node successfully writes data to destination data nodes, a higher retry-concurrency setting can accelerate the rate at which the source data node empties its hinted handoff queue.
Note that increasing retry-concurrency also increases network traffic.
环境变量: INFLUXDB_HINTED_HANDOFF_RETRY_CONCURRENCY
The rate limit (in bytes per second) that hinted handoff retries hints. A value of 0 disables the rate limit.
环境变量: INFLUXDB_HINTED_HANDOFF_RETRY_RATE_LIMIT
The time period after which the hinted handoff retries a write after the write fails.
环境变量: INFLUXDB_HINTED_HANDOFF_RETRY_INTERVAL
The maximum interval after which the hinted handoff retries a write after the write fails. The retry-max-interval option is no longer in use and will be removed from the configuration file in a future release. Changing the retry-max-interval setting has no effect on your cluster.
环境变量: INFLUXDB_HINTED_HANDOFF_RETRY_MAX_INTERVAL
The interval at which InfluxDB checks to purge data that are above max-age.
环境变量: INFLUXDB_HINTED_HANDOFF_PURGE_INTERVAL
For information about the Anti-Entropy service, see [Anti-entropy service in InfluxDB Enterprise
Controls the copying and repairing of shards to ensure that data nodes contain the shard data they are supposed to.
Enables the anti-entropy service. Default value is false.
环境变量: INFLUXDB_ANTI_ENTROPY_ENABLED
The interval of time when anti-entropy checks run on each data node.
环境变量: INFLUXDB_ANTI_ENTROPY_CHECK_INTERVAL
注意：尚不支持
The maximum number of shards that a single data node will copy or repair in parallel.
Having max-fetch=10 with higher numbers of shards (100+) can add significant overhead to running nodes. The more shards you have, the lower this should be set. If AE is enabled while lowering your max-fetch, initially, you’ll see higher CPU load as new shard digest files are created. The added load drops off after shard digests are completed for existing shards.
环境变量: INFLUXDB_ANTI_ENTROPY_MAX_FETCH
注意：尚不支持
The maximum number of concurrent sync operations that should be performed. Modify this setting only when requested by InfluxData support.
环境变量: INFLUXDB_ANTI_ENTROPY_MAX_SYNC
注意：尚不支持
Enables missing shards to automatically be repaired.
环境变量: INFLUXDB_ANTI_ENTROPY_AUTO_REPAIR_MISSING
Controls the enforcement of retention policies for evicting old data.
Enables retention policy enforcement. Default value is true.
环境变量: INFLUXDB_RETENTION_ENABLED
The interval of time when retention policy enforcement checks run.
环境变量: INFLUXDB_RETENTION_CHECK_INTERVAL
Controls the precreation of shards, so they are available before data arrives. Only shards that, after creation, will have both a start- and end-time in the future, will ever be created. Shards are never precreated that would be wholly or partially in the past.
Enables the shard precreation service.
环境变量: INFLUXDB_SHARD_PRECREATION_ENABLED
The interval of time when the check to precreate new shards runs.
环境变量: INFLUXDB_SHARD_PRECREATION_CHECK_INTERVAL
The default period ahead of the end time of a shard group that its successor group is created.
环境变量: INFLUXDB_SHARD_PRECREATION_ADVANCE_PERIOD
By default, InfluxDB writes system monitoring data to the _internal database. If that database does not exist, InfluxDB creates it automatically. The DEFAULT retention policy on the internal database is seven days. To change the default seven-day retention policy, you must create it.
For InfluxDB Enterprise production systems, InfluxData recommends including a dedicated InfluxDB (OSS) monitoring instance for monitoring InfluxDB Enterprise cluster nodes.
- On the dedicated InfluxDB monitoring instance, set
store-enabled = falseto avoid potential performance and storage issues. - On each InfluxDB cluster node, install a Telegraf input plugin and Telegraf output plugin configured to report data to the dedicated InfluxDB monitoring instance.
Enables the internal storage of statistics.
环境变量: INFLUXDB_MONITOR_STORE_ENABLED
The destination database for recorded statistics.
环境变量: INFLUXDB_MONITOR_STORE_DATABASE
The interval at which to record statistics.
环境变量: INFLUXDB_MONITOR_STORE_INTERVAL
注意：尚不支持
The time interval to poll other data nodes' stats when aggregating cluster stats.
环境变量: INFLUXDB_MONITOR_REMOTE_COLLECT_INTERVAL
Controls how the HTTP endpoints are configured. These are the primary mechanism for getting data into and out of InfluxDB.
For InfluxDB OSS, see the OSS documentation.
Enables HTTP endpoints.
环境变量: INFLUXDB_HTTP_ENABLED
Determines whether the Flux query endpoint is enabled. To enable the use of Flux queries, set the value to true.
环境变量: INFLUXDB_HTTP_FLUX_ENABLED
The bind address used by the HTTP service.
环境变量: INFLUXDB_HTTP_BIND_ADDRESS
Enables HTTP authentication.
环境变量: INFLUXDB_HTTP_AUTH_ENABLED
The default realm sent back when issuing a basic authorization challenge.
环境变量: INFLUXDB_HTTP_REALM
Enables HTTP request logging.
环境变量: INFLUXDB_HTTP_LOG_ENABLED
Determines whether the HTTP write request logs should be suppressed when the log is enabled.
The path to the access log, which determines whether detailed write logging is enabled using log-enabled = true. Specifies whether HTTP request logging is written to the specified path when enabled. If influxd is unable to access the specified path, it will log an error and fall back to stderr. When HTTP request logging is enabled, this option specifies the path where log entries should be written. If unspecified, the default is to write to stderr, which intermingles HTTP logs with internal InfluxDB logging. If influxd is unable to access the specified path, it will log an error and fall back to writing the request log to stderr.
环境变量: INFLUXDB_HTTP_ACCESS_LOG_PATH
Filters which requests should be logged. Each filter is of the pattern nnn, nnx, or nxx where n is a number and x is the wildcard for any number. To filter all 5xx responses, use the string 5xx. If multiple filters are used, then only one has to match. The default value is no filters, with every request being printed.
环境变量: INFLUXDB_HTTP_ACCESS_LOG_STATUS_FILTERS_x
access-log-status-filter = ["4xx", "5xx"]
"4xx"` is in array position `0` `"5xx"` is in array position `1
The input values for the access-log-status-filters is an array. When using environment variables, the values can be supplied as follows.
INFLUXDB_HTTP_ACCESS_LOG_STATUS_FILTERS_0=4xx
INFLUXDB_HTTP_ACCESS_LOG_STATUS_FILTERS_1=5xx
The _n at the end of the environment variable represents the array position of the entry.
Enables detailed write logging.
环境变量: INFLUXDB_HTTP_WRITE_TRACING
Determines whether the /pprof endpoint is enabled.
This endpoint is used for troubleshooting and monitoring.
环境变量: INFLUXDB_HTTP_PPROF_ENABLED
Enables authentication on prometheus remote read api. This setting has no
effect if auth-enabled is set to false.
环境变量: INFLUXDB_PROM_READ_AUTH_ENABLED
Enables HTTPS.
环境变量: INFLUXDB_HTTP_HTTPS_ENABLED
The SSL certificate to use when HTTPS is enabled.
The certificate should be a PEM-encoded bundle of the certificate and key.
If it is just the certificate, a key must be specified in https-private-key.
环境变量: INFLUXDB_HTTP_HTTPS_CERTIFICATE
The location of the separate private key.
环境变量: INFLUXDB_HTTP_HTTPS_PRIVATE_KEY
The JWT authorization shared secret used to validate requests using JSON web tokens (JWTs).
环境变量: INFLUXDB_HTTP_SHARED_SECRET
The maximum size, in bytes, of a client request body. When a HTTP client sends data that exceeds the configured maximum size, a 413 Request Entity Too Large HTTP response is returned. To disable the limit, set the value to 0.
环境变量: INFLUXDB_HTTP_MAX_BODY_SIZE
The default chunk size for result sets that should be chunked. The maximum number of rows that can be returned in a non-chunked query. The default setting of 0 allows for an unlimited number of rows. InfluxDB includes a "partial":true tag in the response body if query results exceed the max-row-limit setting.
环境变量: INFLUXDB_HTTP_MAX_ROW_LIMIT
The maximum number of HTTP connections that may be open at once.
New connections that would exceed this limit are dropped.
The default value of 0 disables the limit.
环境变量: INFLUXDB_HTTP_MAX_CONNECTION_LIMIT
Enables the HTTP service over the UNIX domain socket.
环境变量: INFLUXDB_HTTP_UNIX_SOCKET_ENABLED
The path of the UNIX domain socket.
环境变量: INFLUXDB_HTTP_BIND_SOCKET
The maximum number of writes processed concurrently. The default value of 0 disables the limit.
环境变量: INFLUXDB_HTTP_MAX_CONCURRENT_WRITE_LIMIT
The maximum number of writes queued for processing. The default value of 0 disables the limit.
环境变量: INFLUXDB_HTTP_MAX_ENQUEUED_WRITE_LIMIT
The maximum duration for a write to wait in the queue to be processed. Setting this to 0 or setting max-concurrent-write-limit to 0 disables the limit.
Determines which log encoder to use for logs. Valid options are auto, logfmt, and json. A setting of auto will use a more a more user-friendly output format if the output terminal is a TTY, but the format is not as easily machine-readable. When the output is a non-TTY, auto will use logfmt.
环境变量: INFLUXDB_LOGGING_FORMAT
Determines which level of logs will be emitted.
环境变量: INFLUXDB_LOGGING_LEVEL
Suppresses the logo output that is printed when the program is started.
环境变量: INFLUXDB_LOGGING_SUPPRESS_LOGO
Controls the subscriptions, which can be used to fork a copy of all data received by the InfluxDB host.
Determines whether the subscriber service is enabled.
环境变量: INFLUXDB_SUBSCRIBER_ENABLED
The default timeout for HTTP writes to subscribers.
环境变量: INFLUXDB_SUBSCRIBER_HTTP_TIMEOUT
Allows insecure HTTPS connections to subscribers. This option is useful when testing with self-signed certificates.
环境变量: INFLUXDB_SUBSCRIBER_INSECURE_SKIP_VERIFY
The path to the PEM-encoded CA certs file. If the set to the empty string (""), the default system certs will used.
环境变量: INFLUXDB_SUBSCRIBER_CA_CERTS
The number of writer Goroutines processing the write channel.
环境变量: INFLUXDB_SUBSCRIBER_WRITE_CONCURRENCY
The number of in-flight writes buffered in the write channel.
环境变量: INFLUXDB_SUBSCRIBER_WRITE_BUFFER_SIZE
This section controls one or many listeners for Graphite data. For more information, see Graphite protocol support in InfluxDB.
Determines whether the graphite endpoint is enabled.
These next lines control how batching works. You should have this enabled otherwise you could get dropped metrics or poor performance. Batching will buffer points in memory if you have many coming in.
# database = "graphite"
# retention-policy = ""
# bind-address = ":2003"
# protocol = "tcp"
# consistency-level = "one"Flush if this many points get buffered.
The number of batches that may be pending in memory.
Flush at least this often even if we haven’t hit buffer limit.
UDP Read buffer size, 0 means OS default. UDP listener will fail if set above OS max.
This string joins multiple matching ‘measurement’ values providing more control over the final measurement name.
Default tags that will be added to all metrics. These can be overridden at the template level or by tags extracted from metric.
# templates = [
# "*.app env.service.resource.measurement",
# # Default template
# "server.*",
# ]Each template line requires a template pattern. It can have an optional filter before the template and separated by spaces. It can also have optional extra tags following the template. Multiple tags should be separated by commas and no spaces similar to the line protocol format. There can be only one default template.
The [[collectd]] settings control the listener for collectd data. For more information, see CollectD protocol support in InfluxDB.
# enabled = false
# bind-address = ":25826"
# database = "collectd"
# retention-policy = ""
# typesdb = "/usr/share/collectd/types.db"The collectd security level can be "" (or “none”), “sign”, or “encrypt”.
The path to the collectd authorization file. Must be set if security level is sign or encrypt.
These next lines control how batching works. You should have this enabled otherwise you could get dropped metrics or poor performance. Batching will buffer points in memory if you have many coming in.
Flush if this many points get buffered.
The number of batches that may be pending in memory.
Flush at least this often even if we haven’t hit buffer limit.
UDP Read buffer size, 0 means OS default. UDP listener will fail if set above OS max.
Controls the listener for OpenTSDB data. For more information, see OpenTSDB protocol support in InfluxDB.
# enabled = false
# bind-address = ":4242"
# database = "opentsdb"
# retention-policy = ""
# consistency-level = "one"
# tls-enabled = false
# certificate= "/etc/ssl/influxdb.pem"Log an error for every malformed point.
These next lines control how batching works. You should have this enabled otherwise you could get dropped metrics or poor performance. Only points metrics received over the telnet protocol undergo batching.
Flush if this many points get buffered.
The number of batches that may be pending in memory.
Flush at least this often even if we haven’t hit buffer limit.
The [[udp]] settings control the listeners for InfluxDB line protocol data using UDP. For more information, see UDP protocol support in InfluxDB.
# enabled = false
# bind-address = ":8089"
# database = "udp"
# retention-policy = ""InfluxDB precision for timestamps on received points ("" or “n”, “u”, “ms”, “s”, “m”, “h”)
These next lines control how batching works. You should have this enabled otherwise you could get dropped metrics or poor performance. Batching will buffer points in memory if you have many coming in.
Flush if this many points get buffered.
The number of batches that may be pending in memory.
Will flush at least this often even if we haven’t hit buffer limit.
UDP Read buffer size, 0 means OS default. UDP listener will fail if set above OS max.
Controls how continuous queries are run within InfluxDB.
Determines whether the continuous query service is enabled.
环境变量: INFLUXDB_CONTINUOUS_QUERIES_ENABLED
Controls whether queries are logged when executed by the CQ service.
环境变量: INFLUXDB_CONTINUOUS_QUERIES_LOG_ENABLED
Write continuous query execution statistics to the default monitor store.
环境变量: INFLUXDB_CONTINUOUS_QUERIES_QUERY_STATS_ENABLED
The interval for how often continuous queries will be checked whether they need to run.
环境变量: INFLUXDB_CONTINUOUS_QUERIES_RUN_INTERVAL
Global configuration settings for Transport Layer Security (TLS) in InfluxDB.
If the TLS configuration settings is not specified, InfluxDB supports all of the cipher suite IDs listed and all TLS versions implemented in the Constants section of the Go crypto/tls package documentation, depending on the version of Go used to build InfluxDB. Use the SHOW DIAGNOSTICS command to see the version of Go used to build InfluxDB.
InfluxData recommends configuring your InfluxDB server’s TLS settings for “modern compatibility” that provides a higher level of security and assumes that backward compatibility is not required. Our recommended TLS configuration settings for ciphers, min-version, and max-version are based on Mozilla’s “modern compatibility” TLS server configuration described in Security/Server Side TLS.
InfluxData’s recommended TLS settings for “modern compatibility” are specified in the following configuration settings example.
ciphers = [ "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
"TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
"TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256",
"TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
"TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384",
"TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384"
]
min-version = "tls1.3"
max-version = "tls1.3"Minimum version of the TLS protocol that will be negotiated. Valid values include: tls1.0, tls1.1, tls1.2 and tls1.3. If not specified, min-version is the minimum TLS version specified in the Go crypto/tls package. In this example, tls1.3 specifies the minimum version as TLS 1.3.
环境变量: INFLUXDB_TLS_MIN_VERSION
The maximum version of the TLS protocol that will be negotiated. Valid values include: tls1.0, tls1.1, tls1.2 and tls1.3. If not specified, max-version is the maximum TLS version specified in the Go crypto/tls package. In this example, tls1.3 specifies the maximum version as TLS 1.3.
环境变量: INFLUXDB_TLS_MAX_VERSION