• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Telegraf / InfluxDB - additional config fails after X days

Scheduled Pinned Locked Moved Traffic Monitoring
4 Posts 2 Posters 743 Views 2 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    Armstrong
    last edited by Jul 9, 2020, 5:52 PM

    Hi All,

    Just curious if anyone else has had a similar issue. I run Telegraf to InfluxDB, and after a certain period of time (a few days usually), my metrics from the "additional config" section stop functioning. This primarily seems to affect Pfblocker metrics via the [[inputs.logparser]] entry.

    Generally if I click "save" on the Telegraf service it will kick it back on, or if I reboot Pfsense.

    I am using: https://github.com/VictorRobellini/pfSense-Dashboard

    Any thoughts or assistance is welcome. I considered some sort of cron job to restart telegraf every night, if that would work.

    D 1 Reply Last reply Jul 10, 2020, 12:49 PM Reply Quote 0
    • D Offline
      DaddyGo @Armstrong
      last edited by Jul 10, 2020, 12:49 PM

      @Armstrong

      hi,

      Have an original thread here in the forum, I think ask your question there:
      https://forum.netgate.com/topic/152132/grafana-dashboard-using-telegraf-with-additional-plugins/2

      Maybe you can get answers faster😉

      Cats bury it so they can't see it!
      (You know what I mean if you have a cat)

      1 Reply Last reply Reply Quote 0
      • A Offline
        Armstrong
        last edited by Jul 19, 2020, 4:31 PM

        @DaddyGo

        Thank you, I did have a dig to see if someone else had the same problem but it was unique, I meant to come back sooner saying I had resolved.

        As it turns out, two issues I had were actually one. I noticed during this that my listen queue was regularly overflowing by a considerable amount. Eventually I discovered that a particular (blocked) domain was being hammered, with multiple pings every second, over and over.

        I have since modified hosts files on the client machine to prevent it, and now everything works as intended. The sheer volume of connection attempts was causing DNSBL to fall over, and killing the listen queue.

        Thanks again for your reply.

        D 1 Reply Last reply Jul 21, 2020, 9:05 AM Reply Quote 0
        • D Offline
          DaddyGo @Armstrong
          last edited by Jul 21, 2020, 9:05 AM

          @Armstrong

          Good news, learning is for a lifetime 😉

          Cats bury it so they can't see it!
          (You know what I mean if you have a cat)

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            [[user:consent.lead]]
            [[user:consent.not_received]]