I have tried this config.yaml on my conductor. It is referencing the branch1_router
name: user-agent
enabled: true
lib-directory: /var/lib/128t-monitoring
tags:
- key: router
value: branch1_router
- key: node
value: node1
sample-interval: 1
push-interval: 1
inputs:
- name: t128_events
- name: t128_metrics
- name: t128_device_state
- name: t128_peer_path
- name: t128_lte_metric
- name: system
outputs:
- name: t128_events
- name: t128_metrics
- name: t128_device_state
- name: t128_peer_path
- name: t128_lte_metric
- name: system
I can see some information being generated in a file called /tmp/metrics.out
mem,host=128t-conductor-5-3-0-94-automation-1.novalocal,node=node1,router=branch1_router used=3698421760i,free=1760661504i,huge_page_size=2097152i,mapped=289501184i,sreclaimable=228458496i,sunreclaim=81453056i,available=4128088064i,commit_limit=4070277120i,inactive=4776312832i,page_tables=61210624i,write_back=0i,total=8140558336i,high_free=0i,huge_pages_free=0i,low_total=0i,committed_as=10119565312i,buffered=16384i,shared=1232896i,swap_cached=0i,vmalloc_chunk=0i,active=1082556416i,huge_pages_total=0i,swap_free=0i,high_total=0i,slab=309911552i,cached=2681458688i,available_percent=50.71013428826315,dirty=3051520i,low_free=0i,swap_total=0i,vmalloc_total=35184372087808i,vmalloc_used=0i,write_back_tmp=0i,used_percent=45.432040498309135 1666914346000000000
cpu,cpu=cpu-total,host=128t-conductor-5-3-0-94-automation-1.novalocal,node=node1,router=branch1_router usage_idle=69.87341772051917,usage_nice=0,usage_iowait=0,usage_irq=1.012658227829273,usage_steal=0.5063291139146365,usage_user=23.29113924041866,usage_softirq=0.25316455695731827,usage_guest=0,usage_guest_nice=0,usage_system=5.063291139261492 1666914346000000000
cpu,cpu=cpu3,host=128t-conductor-5-3-0-94-automation-1.novalocal,node=node1,router=branch1_router usage_idle=50.505050505525624,usage_nice=0,usage_irq=1.0101010101095937,usage_guest=0,usage_user=38.383838383934894,usage_system=9.09090909100931,usage_iowait=0,usage_softirq=0,usage_steal=1.0101010101095937,usage_guest_nice=0 1666914346000000000
disk,device=sda1,fstype=xfs,host=128t-conductor-5-3-0-94-automation-1.novalocal,mode=rw,node=node1,path=/,router=branch1_router inodes_free=52290798i,inodes_used=137426i,total=107362627584i,free=91933908992i,used=15428718592i,used_percent=14.370660386388778,inodes_total=52428224i 1666914346000000000
cpu,cpu=cpu-total,host=128t-conductor-5-3-0-94-automation-1.novalocal,node=node1,router=branch1_router usage_idle=69.87341772051917,usage_nice=0,usage_iowait=0,usage_irq=1.012658227829273,usage_steal=0.5063291139146365,usage_user=23.29113924041866,usage_softirq=0.25316455695731827,usage_guest=0,usage_guest_nice=0,usage_system=5.063291139261492 1666914346000000000
disk,device=sda1,fstype=xfs,host=128t-conductor-5-3-0-94-automation-1.novalocal,mode=rw,node=node1,path=/,router=branch1_router inodes_free=52290798i,inodes_used=137426i,total=107362627584i,free=91933908992i,used=15428718592i,used_percent=14.370660386388778,inodes_total=52428224i 1666914346000000000
mem,host=128t-conductor-5-3-0-94-automation-1.novalocal,node=node1,router=branch1_router used=3698421760i,free=1760661504i,huge_page_size=2097152i,mapped=289501184i,sreclaimable=228458496i,sunreclaim=81453056i,available=4128088064i,commit_limit=4070277120i,inactive=4776312832i,page_tables=61210624i,write_back=0i,total=8140558336i,high_free=0i,huge_pages_free=0i,low_total=0i,committed_as=10119565312i,buffered=16384i,shared=1232896i,swap_cached=0i,vmalloc_chunk=0i,active=1082556416i,huge_pages_total=0i,swap_free=0i,high_total=0i,slab=309911552i,cached=2681458688i,available_percent=50.71013428826315,dirty=3051520i,low_free=0i,swap_total=0i,vmalloc_total=35184372087808i,vmalloc_used=0i,write_back_tmp=0i,used_percent=45.432040498309135 1666914346000000000
mem,host=128t-conductor-5-3-0-94-automation-1.novalocal,node=node1,router=branch1_router used=3698421760i,free=1760661504i,huge_page_size=2097152i,mapped=289501184i,sreclaimable=228458496i,sunreclaim=81453056i,available=4128088064i,commit_limit=4070277120i,inactive=4776312832i,page_tables=61210624i,write_back=0i,total=8140558336i,high_free=0i,huge_pages_free=0i,low_total=0i,committed_as=10119565312i,buffered=16384i,shared=1232896i,swap_cached=0i,vmalloc_chunk=0i,active=1082556416i,huge_pages_total=0i,swap_free=0i,high_total=0i,slab=309911552i,cached=2681458688i,available_percent=50.71013428826315,dirty=3051520i,low_free=0i,swap_total=0i,vmalloc_total=35184372087808i,vmalloc_used=0i,writ
------------------------------
Thomas Maclean
------------------------------
Original Message:
Sent: 10-27-2022 12:32
From: Anonymous User
Subject: Monitoring Agent
This message was posted by a user wishing to remain anonymous
Hi,
Thank you so much for the question. What do you have so far for a configuration? The documentation does have an example configuration to work with, but I do understand there are a lot details there to go through.
This section covers how to configure output to a file:
https://www.juniper.net/documentation/us/en/software/session-smart-router/docs/plugin_monitoring_agent/#outputs-1
Original Message:
Sent: 10-26-2022 15:04
From: Anonymous User
Subject: Monitoring Agent
This message was posted by a user wishing to remain anonymous
Hello,
Just wanted to setup a simple Monitoring Agent to collect everything available and output it to a file. I am using SSR 6.x code. I am looking for an example that I can replicate easily in my lab. I have the 128t documentation and there are lots of details in it. But I am just looking for a kb or something on the basic setup like what exactly does the config.yaml look like and so on.
- name: t128_arp_state
- name: t128_device_state
- name: t128_events
- name: t128_graphql
- name: t128_lte_metric
- name: t128_metrics
- name: t128_peer_path
- name: t128_session_records
- name: t128_top_analytics
I have been reading this documentation.
128T Monitoring Agent | SSN Docs| Juniper | remove preview |
| | 128T Monitoring Agent | SSN Docs | | The 128T Monitoring Agent is an entity for collecting data from a node running 128T software and to push it to a collector. It is capable of collecting the data from several sources such as metrics, events etc. The current mechanism of monitoring a 128T router involves performing REST or GraphQL queries from the conductor. | | View this on Juniper > |
|
|