Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
telegraf-nftables
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Due to inactivity, this project is scheduled to be deleted on 2035-04-24.
Why is this scheduled?
Show more breadcrumbs
vqgroup
telegraf-nftables
Commits
ce12913b
Unverified
Commit
ce12913b
authored
7 years ago
by
Daniel Nelson
Browse files
Options
Downloads
Patches
Plain Diff
Update precision documentation and examples
Precision is no longer used by the InfluxDB output. closes #3079
parent
d82c5062
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/CONFIGURATION.md
+7
-8
7 additions, 8 deletions
docs/CONFIGURATION.md
with
7 additions
and
8 deletions
docs/CONFIGURATION.md
+
7
−
8
View file @
ce12913b
...
...
@@ -66,10 +66,13 @@ interval. Maximum flush_interval will be flush_interval + flush_jitter
This is primarily to avoid
large write spikes for users running a large number of telegraf instances.
ie, a jitter of 5s and flush_interval 10s means flushes will happen every 10-15s.
*
**precision**
: By default, precision will be set to the same timestamp order
as the collection interval, with the maximum being 1s. Precision will NOT
be used for service inputs, such as logparser and statsd. Valid values are
"ns", "us" (or "µs"), "ms", "s".
*
**precision**
:
By default or when set to "0s", precision will be set to the same
timestamp order as the collection interval, with the maximum being 1s.
Precision will NOT be used for service inputs. It is up to each individual
service input to set the timestamp at the appropriate precision.
Valid time units are "ns", "us" (or "µs"), "ms", "s".
*
**logfile**
: Specify the log file name. The empty string means to log to stderr.
*
**debug**
: Run telegraf in debug mode.
*
**quiet**
: Run telegraf in quiet mode (error messages only).
...
...
@@ -178,7 +181,6 @@ fields which begin with `time_`.
[[outputs.influxdb]]
url
=
"http://192.168.59.103:8086"
# required.
database
=
"telegraf"
# required.
precision
=
"s"
# INPUTS
[[inputs.cpu]]
...
...
@@ -317,21 +319,18 @@ to avoid measurement collisions:
[[outputs.influxdb]]
urls
=
[
"http://localhost:8086"
]
database
=
"telegraf"
precision
=
"s"
# Drop all measurements that start with "aerospike"
namedrop
=
[
"aerospike*"
]
[[outputs.influxdb]]
urls
=
[
"http://localhost:8086"
]
database
=
"telegraf-aerospike-data"
precision
=
"s"
# Only accept aerospike data:
namepass
=
[
"aerospike*"
]
[[outputs.influxdb]]
urls
=
[
"http://localhost:8086"
]
database
=
"telegraf-cpu0-data"
precision
=
"s"
# Only store measurements where the tag "cpu" matches the value "cpu0"
[outputs.influxdb.tagpass]
cpu
=
[
"cpu0"
]
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment