influxdb基础（六）——influxdb.conf配置详解（官方文档翻译）

文章目录

• 前言
• influxdb.conf原件
• 总结

前言

influxdb

默认配置路径为

/etc/influxdb/influxdb.conf

。其内包含了数据文件存储路径、大小、缓存刷入

TSM

文件阈值、压缩shard阈值、是否打印log、并发数、端口等各种配置。非常有必要了解其有哪些配置和策略，对理解

influxdb

的运作原理上有一定帮助。配置虽多只需要知道其中一些主要的，大部分都可以保持默认配置，等真的需要时再深入研究其配置。

influxdb.conf原件

### Welcome to the InfluxDB configuration file.

# The values in this file override the default values used by the system if
# a config option is not specified. The commented out lines are the configuration
# field and the default value used. Uncommenting a line and changing the value
# will change the value used at runtime when the process is restarted.

# Once every 24 hours InfluxDB will report usage data to usage.influxdata.com
# The data includes a random ID, os, arch, version, the number of series and other
# usage data. No data from user databases is ever transmitted.
# Change this option to true to disable reporting.
# 该选项用于上报influxdb的使用信息给InfluxData公司，默认值为false
# reporting-disabled = false

# Bind address to use for the RPC service for backup and restore.
# 用于为备份和恢复绑定rpc服务地址，
# bind-address = "127.0.0.1:8088"

###
### [meta]
###
### Controls the parameters for the Raft consensus group that stores metadata
### about the InfluxDB cluster.
###

[meta]
  # Where the metadata/raft database is stored
  # 元目录，meta目录中的文件包括meta.db。
  # 主要存储包含系统状态的内部信息、用户信息、数据库/分片元数据、CQs、RPs和订阅等
  dir = "/var/lib/influxdb/meta"

  # Automatically create a default retention policy when creating a database.
  # 当创建db时，自动创建默认的rp autogen
  # 因为默认rp是永久保存数据，在生产环境中都应该主动设置rp，所以可以设置为false。
  # retention-autocreate = true

  # If log messages are printed for the meta service
  # 记录打印 meta服务的日志消息
  # logging-enabled = true

###
### [data]
###
### Controls where the actual shard data for InfluxDB lives and how it is
### flushed from the WAL. "dir" may need to be changed to a suitable place
### for your system, but the WAL settings are an advanced configuration. The
### defaults should work for most systems.
###

[data]
  # The directory where the TSM storage engine stores TSM files.
  # TSM 文件存储的目录（真正存储db数据的目录），可设置其他目录
  dir = "/var/lib/influxdb/data"

  # The directory where the TSM storage engine stores WAL files.
  # wal 预写日志文件存储目录
  wal-dir = "/var/lib/influxdb/wal"

  # The amount of time that a write will wait before fsyncing.  A duration
  # greater than 0 can be used to batch up multiple fsync calls.  This is useful for slower
  # disks or when WAL write contention is seen.  A value of 0s fsyncs every write to the WAL.
  # Values in the range of 0-100ms are recommended for non-SSD disks.
  # wal同步写入之前等待的时间。
  # 使用大于0的持续时间对多个fsync调用进行批处理，这对于速度较慢的磁盘或遇到WAL写入争用时非常有用。
  # 0值会同步对WAL的每次写操作。对于非ssd磁盘，我们建议其范围为0ms-100ms。
  # wal-fsync-delay = "0s"


  # The type of shard index to use for new shards.  The default is an in-memory index that is
  # recreated at startup.  A value of "tsi1" will use a disk based index that supports higher
  # cardinality datasets.
  # 用于新shard的索引类型。默认情况下在启动时重新创建的内存索引。值tsi1将使用基于磁盘的索引，该索引支持较高的基数数据集。
  # index-version = "inmem"

  # Trace logging provides more verbose output around the tsm engine. Turning
  # this on can provide more useful output for debugging tsm engine issues.
  # 切换TSM引擎和WAL中附加调试信息的日志记录。默认不开启
  # trace-logging-enabled = false

  # Whether queries should be logged before execution. Very useful for troubleshooting, but will
  # log any sensitive data contained within a query.
  # 查询时记录日志
  # 对于故障诊断非常有用，但将记录查询中包含的任何敏感数据。
  # 开发环境可以开启true，生产环境false
  # query-log-enabled = true

  # Validates incoming writes to ensure keys only have valid unicode characters.
  # This setting will incur a small overhead because every key must be checked.
  # 验证传入的写操作，以确保键只有有效的unicode字符。
  # 这个设置会产生一个小的开销，因为必须检查每个键，所以默认不开启。
  # validate-keys = false

  # Settings for the TSM engine

  # CacheMaxMemorySize is the maximum size a shard's cache can
  # reach before it starts rejecting writes.
  # Valid size suffixes are k, m, or g (case insensitive, 1024 = 1k).
  # Values without a size suffix are in bytes.
  # shard缓存最大内存大小，达到最大值后拒绝写操作。
  # cache-max-memory-size = "1g"

  # CacheSnapshotMemorySize is the size at which the engine will
  # snapshot the cache and write it to a TSM file, freeing up memory
  # Valid size suffixes are k, m, or g (case insensitive, 1024 = 1k).
  # Values without a size suffix are in bytes.
  # shard的cache模块刷新数据到tsm文件的阈值，
  # 到达这个值将保存快照，将数据刷入tsm，并释放cache。
  # cache-snapshot-memory-size = "25m"

  # CacheSnapshotWriteColdDuration is the length of time at
  # which the engine will snapshot the cache and write it to
  # a new TSM file if the shard hasn't received writes or deletes
  # shard是有时间范围的，超过了这个时间范围就不会往这个shard里写数据了，
  # 所以超过这个时间没有收到写或者删除操作时，此时cache可能没有达到阈值，此时依然会对cache进行快照并写入新的tsm文件
  # cache-snapshot-write-cold-duration = "10m"

  # CompactFullWriteColdDuration is the duration at which the engine
  # will compact all TSM files in a shard if it hasn't received a
  # write or delete
  # shard是有时间范围的，超过了这个时间范围就不会往这个shard里写数据了，
  # 所以超过这个时间没有收到写或者删除操作时，会压缩所有的tsm文件为一个文件。
  # compact-full-write-cold-duration = "4h"

  # The maximum number of concurrent full and level compactions that can run at one time.  A
  # value of 0 results in 50% of runtime.GOMAXPROCS(0) used at runtime.  Any number greater
  # than 0 limits compactions to that value.  This setting does not apply
  # to cache snapshotting.
  # 同时可以运行的并发满压缩和级别压缩的最大数量。
  # 值为0将导致运行时使用runtime. gomaxprocs(0)——这意味着使用所有处理器。
  # 此设置不适用于缓存快照。 默认0就完事了。
  # max-concurrent-compactions = 0

  # CompactThroughput is the rate limit in bytes per second that we
  # will allow TSM compactions to write to disk. Note that short bursts are allowed
  # to happen at a possibly larger value, set by CompactThroughputBurst
  # 每秒压缩tsm写入磁盘时的速率，48m/s
  # compact-throughput = "48m"

  # CompactThroughputBurst is the rate limit in bytes per second that we
  # will allow TSM compactions to write to disk.
  # 允许短时间爆发的更大速率，每秒压缩tsm写入磁盘时的速率，48m/s
  # compact-throughput-burst = "48m"

  # If true, then the mmap advise value MADV_WILLNEED will be provided to the kernel with respect to
  # TSM files. This setting has been found to be problematic on some kernels, and defaults to off.
  # It might help users who have slow disks in some cases.
  # 默认false即可
  # tsm-use-madv-willneed = false

  # Settings for the inmem index

  # The maximum series allowed per database before writes are dropped.  This limit can prevent
  # high cardinality issues at the database level.  This limit can be disabled by setting it to
  # 0.
  # 每个数据库允许的最大series数，默认设置是一百万。series 指 tag、measurement、policy 相同的数据集合
  # 将该设置更改为0，以允许每个数据库的序列数量不受限制。
  # 若超过则会返回500错误，并提示{"error":"max series per database exceeded: <series>"}
  # max-series-per-database = 1000000

  # The maximum number of tag values per tag that are allowed before writes are dropped.  This limit
  # can prevent high cardinality tag values from being written to a measurement.  This limit can be
  # disabled by setting it to 0.
  # 设置每一个tag允许的value最大数量，默认10W,设置0可以取消限制。
  # 若超过该数值，则会返回错误。
  # max-values-per-tag = 100000

  # Settings for the tsi1 index

  # The threshold, in bytes, when an index write-ahead log 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.
  # 索引提前写日志文件压缩到索引文件中时的阈值(以字节为单位)。较小的大小将导致日志文件被压缩得更多
  # 这会导致以写吞吐量为代价的较低堆使用率。更大的尺寸压缩频率更低，在内存中存储更多系列，并提供更高的写吞吐量。
  # 有效的大小后缀是k、m或g(大小写不敏感，1024 = 1k)。没有大小后缀的#值以字节为单位。
  # max-index-log-file-size = "1m"

  # 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.
  # 以前TSI索引中用于存储的内部缓存的大小计算的级数结果。
  # 缓存的结果将更快地从缓存中返回，当后续查询带有匹配的标签键/值时，不需要重新计算
  # 将此值设置为0将禁用缓存，这可能会导致缓存失效导致查询性能问题。
  # 增大此值会增加堆的使用，默认100。没太理解后续用到再说
  series-id-set-cache-size = 100

###
### [coordinator]
###
### Controls the clustering service configuration.
###

[coordinator]
  # The default time a write request will wait until a "timeout" error is returned to the caller.
  # 写超时时间
  # write-timeout = "10s"

  # 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.
  # 同一时间查询请求最大并发数，超过这个阈值，将返回异常给调用者。如果设置为0，将禁用该设置，并发数无限制。
  # max-concurrent-queries = 0

  # The maximum time a query will 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.
  # 查询请求超时时间，0无限制
  # query-timeout = "0s"

  # 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.
  # 查询慢日志记录阈值，即为查询多久被记录为慢日志。0为无限制。
  # log-queries-after = "0s"

  # The maximum number of points a SELECT can process.  A value of 0 will make
  # the maximum point count unlimited.  This will only be checked every second so queries will not
  # be aborted immediately when hitting the limit.
  # 一次查询返回的最大point数，即数据的条数。0无限制
  # 这只是每秒钟检查，所以某一秒到达point最大值，不会影响后面的查询
  # max-select-point = 0

  # The maximum number of series a SELECT can run.  A value of 0 will make the maximum series
  # count unlimited.
  # 一次查询返回的series的最大值，0无限制
  # max-select-series = 0

  # The maximum number of group by time bucket a SELECT can create.  A value of zero will max the maximum
  # number of buckets unlimited.
  # 一次查询按时间排序最大组数，0无限制。
  # max-select-buckets = 0

###
### [retention]
###
### Controls the enforcement of retention policies for evicting old data.
### 控制删除旧数据的保留策略的执行设置。
###

[retention]
  # Determines whether retention policy enforcement enabled.
  # 是否开启保留策略，默认开启
  # enabled = true

  # The interval of time when retention policy enforcement checks run.
  # 保留策略强制检查运行的时间间隔，默认30分钟检查一下shard group，并以shard group为单位清除数据
  # check-interval = "30m"

###
### [shard-precreation]
### shard预创建配置
###
### 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.

[shard-precreation]
  # Determines whether shard pre-creation service is enabled.
  # 是否开启shard预创建服务，默认开启，为了数据写入时shard已经准备好可用。
  # enabled = true

  # The interval of time when the check to pre-create new shards runs.
  # 预创建新shard的检查运行时间间隔
  # check-interval = "10m"

  # The default period ahead of the endtime of a shard group that its successor
  # group is created.
  # 一个shard group在结束写之前多久，后继group被创建。也是下一个group的预创建时间
  # 默认30分钟前
  # advance-period = "30m"

###
### Controls the system self-monitoring, statistics and diagnostics.
### 控制系统的自我监视、统计和诊断。
###
### The internal database for monitoring data is created automatically if
### if it does not already exist. The target retention within this database
### is called 'monitor' and is also created with a retention period of 7 days
### and a replication factor of 1, if it does not exist. In all cases the
### this retention policy is configured as the default for the database.
### 用于监控数据的内部数据库如果它不存在将自动创建。此数据库中的目标保留策略名为“monitor”，如果不存在，则创建的保留期为7天，复制因子为1的保留策略。
### 在所有情况下这个保留策略被配置为该数据库的默认策略。


[monitor]
  # Whether to record statistics internally.
  # 是否在内部记录统计数据，默认记录。
  # store-enabled = true

  # The destination database for recorded statistics
  # 用于记录统计数据的目标数据库，_internal
  # store-database = "_internal"

  # The interval at which to record statistics
  # 多久记录一次统计数据，默认10秒。
  # store-interval = "10s"

###
### [http]
###
### Controls how the HTTP endpoints are configured. These are the primary
### mechanism for getting data into and out of InfluxDB.
### 控制如何配置HTTP端点。这些是用于输入和输出数据的主要原理。
###

[http]
  # Determines whether HTTP endpoint is enabled.
  # 是否开启http端点，默认开启，为了通过http操作数据库
  # enabled = true

  # Determines whether the Flux query endpoint is enabled.
  # 确认是否启用Flux query
  # flux-enabled = false

  # Determines whether the Flux query logging is enabled.
  # 确认是否开启Flux query日志
  # flux-log-enabled = false

  # The bind address used by the HTTP service.
  # http服务绑定的地址端口 ，默认8086，如果冲突可更换
  # bind-address = ":8086"

  # Determines whether user authentication is enabled over HTTP/HTTPS.
  # 确定是否通过HTTP/HTTPS启用用户身份验证。
 auth-enabled = true

  # The default realm sent back when issuing a basic auth challenge.
  # 发出基本认证质询时返回的默认域。
  # realm = "InfluxDB"

  # Determines whether HTTP request logging is enabled.
  # 确认是否启动http请求日志
  # log-enabled = true

  # Determines whether the HTTP write request logs should be suppressed when the log is enabled.
  # 确定在启用日志时是否应该抑制HTTP写请求日志。，默认false，即会记录写日志
  # suppress-write-log = false

  # 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.
  # 当启用HTTP请求日志记录时，此选项指定路径应该写入日志条目。
  # 如果未指定，默认是写入stderr，它混合HTTP日志和内部的影响db日志。
  #
  # If influxd is unable to access the specified path, it will log an error and fall back to writing
  # the request log to stderr.
  # 如果没有指定日志路径，将记录一个异常并转而写入stderr（标准错误输出）
  # 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 a 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 is to have no filters which
  # will cause every request to be printed.
  # 过滤器配置 有3种模式NNN,NNX or NXX.N 代表一个数字，x是任何数字的统配符。如果想过滤所有5xx返回，可使用5xx
  # 如果使用多个过滤器，只有其中一个被匹配到。默认没有配置过滤器，即将输出每一个的请求返回日志
  # access-log-status-filters = []

  # Determines whether detailed write logging is enabled.
  # 确认是否启用详细写日志
  # write-tracing = false

  # Determines whether the pprof endpoint is enabled.  This endpoint is used for
  # troubleshooting and monitoring.
  # 确定是否启用pprof端点。此端点用于故障排除和监控。
  # pprof-enabled = true

  # Enables authentication on pprof endpoints. Users will need admin permissions
  # to access the pprof endpoints when this setting is enabled. This setting has
  # no effect if either auth-enabled or pprof-enabled are set to false.
  # 在pprof端点上启用身份验证。用户将需要管理权限以在启用此设置时访问pprof端点。
  # 这个设置如果auth启用，设置为false，则无效。
  # pprof-auth-enabled = false

  # Enables a pprof endpoint that binds to localhost:6060 immediately on startup.
  # This is only needed to debug startup issues.
  # 启用在启动时立即绑定到本地主机6060的pprof端点。这只需要调试启动问题。
  # debug-pprof-enabled = false

  # Enables authentication on the /ping, /metrics, and deprecated /status
  # endpoints. This setting has no effect if auth-enabled is set to false.
  # 在/ping,/metrics,deprecated,status端点上启用权限验证，默认不启用。
  # ping-auth-enabled = false

  # Determines whether HTTPS is enabled.
  # 确认是否启用https
  # https-enabled = false

  # The SSL certificate to use when HTTPS is enabled.
  # 启用HTTPS时要使用的SSL证书。
  # https-certificate = "/etc/ssl/influxdb.pem"

  # Use a separate private key location.
  # 使用单独的私钥位置。
  # https-private-key = ""

  # The JWT auth shared secret to validate requests using JSON web tokens.
  # JWT认证共享秘密，使用JSON web令牌验证请求。
  # shared-secret = ""

  # The default chunk size for result sets that should be chunked.
  # 应该被分块的结果集，默认chunk的大小
  # max-row-limit = 0

  # The maximum number of HTTP connections that may be open at once.  New connections that
  # would exceed this limit are dropped.  Setting this value to 0 disables the limit.
  # 一次可以打开的最大HTTP连接数。超过此限制的新连接将被删除。将此值设置为0将禁用此限制。
  # max-connection-limit = 0

  # Enable http service over unix domain socket
  # 通过unix域套接字启用http服务
  # unix-socket-enabled = false

  # The path of the unix domain socket.
  # unix域套接字的路径。
  # bind-socket = "/var/run/influxdb.sock"

  # The maximum size of a client request body, in bytes. Setting this value to 0 disables the limit.
  # 客户端请求主体的最大大小，以字节为单位。将此值设置为0将禁用此限制。默认23m左右
  # max-body-size = 25000000

  # The maximum number of writes processed concurrently.
  # Setting this to 0 disables the limit.
  # 并发处理的最大写操作数。将此设置为0将禁用此限制。
  # max-concurrent-write-limit = 0

  # The maximum number of writes queued for processing.
  # Setting this to 0 disables the limit.
  # 排队等待处理的最大写操作数。将此设置为0将禁用此限制。
  # max-enqueued-write-limit = 0

  # 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.
  # 写操作在要处理的队列中等待的最大持续时间。将此设置为0或将max-enqueued-write-limit设置为0将禁用该限制。
  # enqueued-write-timeout = 0

###
### [logging]
###
### Controls how the logger emits logs to the output.
### 控制日志记录器如何将日志发送到控制台
###

[logging]
  # Determines which log encoder to use for logs. Available options
  # are auto, logfmt, and json. 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.
  # 是使用自动编码
  # format = "auto"

  # Determines which level of logs will be emitted. The available levels
  # are error, warn, info, and debug. Logs that are equal to or above the
  # specified level will be emitted.
  # 日志级别  info，错误、警告、信息和调试都会打印
  # level = "info"

  # Suppresses the logo output that is printed when the program is started.
  # The logo is always suppressed if STDOUT is not a TTY.
  # 抑制程序启动时打印的徽标输出。如果STDOUT不是TTY，徽标总是被抑制的。
  # suppress-logo = false

###
### [subscriber]
###
### Controls the subscriptions, which can be used to fork a copy of all data
### received by the InfluxDB host.
### 控制订阅，订阅可用于由inflxudb主机接收，派生所有数据的副本。
###

[subscriber]
  # Determines whether the subscriber service is enabled.
  # 确定是否启用订阅服务器服务。
  # enabled = true

  # The default timeout for HTTP writes to subscribers.
  # 对订阅者的HTTP写入的默认超时。
  # http-timeout = "30s"

  # Allows insecure HTTPS connections to subscribers.  This is useful when testing with self-
  # signed certificates.
  # 允许不安全的HTTPS连接到订阅者。这在使用自我签署证书进行测试时非常有用。false不跳过安全验证。
  # insecure-skip-verify = false

  # The path to the PEM encoded CA certs file. If the empty string, the default system certs will be used
  # PEM编码的CA certs文件的路径。如果为空字符串，则使用默认的系统证书。
  # ca-certs = ""

  # The number of writer goroutines processing the write channel.
  # 写管道处理写请求的并发数
  # write-concurrency = 40

  # The number of in-flight writes buffered in the write channel.
  # 写通道中写缓冲的大小
  # write-buffer-size = 1000

###
### [continuous_queries]
###
### Controls how continuous queries are run within InfluxDB.
### 控制如何在InfluxDB中运行连续查询。
###

[continuous_queries]
  # Determines whether the continuous query service is enabled.
  # 是否开启CQ
  # enabled = true

  # Controls whether queries are logged when executed by the CQ service.
  # CQ服务执行时是否记录查询日志。
  # log-enabled = true

  # Controls whether queries are logged to the self-monitoring data store.
  # 是否将查询记录到自监视数据存储，即_internal
  # query-stats-enabled = false

  # interval for how often continuous queries will be checked if they need to run
  # CQ运行的频率，每秒1次
  # run-interval = "1s"

###
### [tls]
###
### Global configuration settings for TLS in InfluxDB.
### 在influxdb中TLS的全局配置设置。
###

[tls]
  # Determines the available set of cipher suites. See https://golang.org/pkg/crypto/tls/#pkg-constants
  # for a list of available ciphers, which depends on the version of Go (use the query
  # SHOW DIAGNOSTICS to see the version of Go used to build InfluxDB). If not specified, uses
  # the default settings from Go's crypto/tls package.
  # ciphers = [
  #   "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
  #   "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
  # ]

  # Minimum version of the tls protocol that will be negotiated. If not specified, uses the
  # default settings from Go's crypto/tls package.
  # 将要协商的tls协议的最小版本。如果未指定，则使用Go的crypto/tls包的默认设置。
  # min-version = "tls1.2"

  # Maximum version of the tls protocol that will be negotiated. If not specified, uses the
  # default settings from Go's crypto/tls package.
  # 需要协商的tls协议的最大版本。如果未指定，则使用Go的crypto/tls包的默认设置。
  # max-version = "tls1.3"
           

总结

配置内容大多根据英文翻译再加上自己的理解而得，删除了一些不常用的监听器的配置。阅读配置了解并应证了很多

inflxudb

的运行策略，如：

• data的配置，TSM文件存放位置、wal文件存放位置都可以自行修改。
• shard大小可配，默认1g，达到最大值，拒绝写入，shard空闲4个小时后将被压缩。
• cache大小可配，默认25m，到达这个阈值将创建快照输入tsm文件。空闲的cache没有达到25m，也会在10分钟后创建快照刷入tsm文件。
• 数据库最大的series数，默认100万。
• 写超时、最大并发数、查询 超时、慢日志、一次查询的最大point数等。
• 保留策略检查数据过期的时间间隔，默认半小时，这些都可以配置。
• 如果结合源码找到每个配置项的源码所在理解的就更通透了，但是花费的时间也是成倍的。

… …

PS: 如若文章中有错误理解，欢迎批评指正，同时非常期待你的评论、点赞和收藏。我是徐同学，愿与你共同进步！

参考：

官方英文文档：https://docs.influxdata.com/influxdb/v1.4/administration/config/#configuration-overview