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
de03ee3c
Unverified
Commit
de03ee3c
authored
7 years ago
by
Daniel Nelson
Browse files
Options
Downloads
Patches
Plain Diff
Update nats readme
parent
fbd3544a
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
plugins/inputs/nats/README.md
+35
-5
35 additions, 5 deletions
plugins/inputs/nats/README.md
plugins/inputs/nats/nats.go
+1
-1
1 addition, 1 deletion
plugins/inputs/nats/nats.go
with
36 additions
and
6 deletions
plugins/inputs/nats/README.md
+
35
−
5
View file @
de03ee3c
# NATS
Monitoring
Input Plugin
# NATS Input Plugin
The
[
NATS
](
http://www.nats.io/about/
)
monitoring plugin
read
s from
specified NATS instance and submits metrics to InfluxDB.
The
[
NATS
](
http://www.nats.io/about/
)
monitoring plugin
gathers metric
s from
the NATS
[
monitoring http server
](
https://www.nats.io/documentation/server/gnatsd-monitoring/
)
.
## Configuration
##
#
Configuration
```
toml
[[inputs.nats]]
## The address of the monitoring end
-
point of the NATS server
## The address of the monitoring endpoint of the NATS server
server
=
"http://localhost:8222"
## Maximum time to receive response
# response_timeout = "5s"
```
### Metrics:
-
nats
-
tags
-
server
-
fields:
-
uptime (integer, nanoseconds)
-
mem (integer, bytes)
-
subscriptions (integer, count)
-
out_bytes (integer, bytes)
-
connections (integer, count)
-
in_msgs (integer, bytes)
-
total_connections (integer, count)
-
cores (integer, count)
-
cpu (integer, count)
-
slow_consumers (integer, count)
-
routes (integer, count)
-
remotes (integer, count)
-
out_msgs (integer, count)
-
in_bytes (integer, bytes)
### Example Output:
```
nats,server=http://localhost:8222 uptime=117158348682i,mem=6647808i,subscriptions=0i,out_bytes=0i,connections=0i,in_msgs=0i,total_connections=0i,cores=2i,cpu=0,slow_consumers=0i,routes=0i,remotes=0i,out_msgs=0i,in_bytes=0i 1517015107000000000
```
This diff is collapsed.
Click to expand it.
plugins/inputs/nats/nats.go
+
1
−
1
View file @
de03ee3c
...
...
@@ -25,7 +25,7 @@ type Nats struct {
var
sampleConfig
=
`
## The address of the monitoring endpoint of the NATS server
server = "http://localhost:
1337
"
server = "http://localhost:
8222
"
## Maximum time to receive response
# response_timeout = "5s"
...
...
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