You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Still not sure why but when I add bgp profile to my router the telegraf_mx container is unable to start up. It keep restarting in log i see only:
2024-10-08T13:01:05Z I! Using config file: /etc/telegraf/telegraf.conf
2024-10-08T13:01:08Z I! Starting Telegraf 1.0.6
2024-10-08T13:01:08Z I! Using config file: /etc/telegraf/telegraf.conf
2024-10-08T13:01:15Z I! Starting Telegraf 1.0.6
2024-10-08T13:01:15Z I! Using config file: /etc/telegraf/telegraf.conf
2024-10-08T13:01:28Z I! Starting Telegraf 1.0.6
2024-10-08T13:01:28Z I! Using config file: /etc/telegraf/telegraf.conf
2024-10-08T13:01:54Z I! Starting Telegraf 1.0.6
2024-10-08T13:01:54Z I! Using config file: /etc/telegraf/telegraf.conf
When trying to test it with analyzer eg. /network-instances/network-instance/protocols/protocol/bgp/
All works fine and it returns the data.
Any idea what could wrong ?
The text was updated successfully, but these errors were encountered:
Hi,
Still not sure why but when I add bgp profile to my router the telegraf_mx container is unable to start up. It keep restarting in log i see only:
2024-10-08T13:01:05Z I! Using config file: /etc/telegraf/telegraf.conf
2024-10-08T13:01:08Z I! Starting Telegraf 1.0.6
2024-10-08T13:01:08Z I! Using config file: /etc/telegraf/telegraf.conf
2024-10-08T13:01:15Z I! Starting Telegraf 1.0.6
2024-10-08T13:01:15Z I! Using config file: /etc/telegraf/telegraf.conf
2024-10-08T13:01:28Z I! Starting Telegraf 1.0.6
2024-10-08T13:01:28Z I! Using config file: /etc/telegraf/telegraf.conf
2024-10-08T13:01:54Z I! Starting Telegraf 1.0.6
2024-10-08T13:01:54Z I! Using config file: /etc/telegraf/telegraf.conf
When trying to test it with analyzer eg. /network-instances/network-instance/protocols/protocol/bgp/
All works fine and it returns the data.
Any idea what could wrong ?
The text was updated successfully, but these errors were encountered: