Telegraf Charm

disable input.conntrack on containers

Bug #1799583 reported by Drew Freiberger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Telegraf Charm
Fix Released
Medium
Xav Paice

Bug Description

We're seeing errors on new clouds where telegraf is reporting that it can't read conntrack info from proc. Suggest disabling conntrack (and possibly others) when in a container.

Related branches

~xavpaice/charm-telegraf/+git/telegraf-charm:lp1799583
Paul Gear (community): Approve
Diff: 101 lines (+40/-8)
2 files modified
reactive/telegraf.py (+33/-7)
templates/base_inputs.conf (+7/-1)
Revision history for this message
Xav Paice (xavpaice) wrote :

Also bcache checks

Changed in telegraf-charm:
status: New → Confirmed
importance: Undecided → Medium
tags: added: canonical-bootstack
Revision history for this message
Junien F (axino) wrote :

I fixed bcache already, it will only add the bcache input if there is a bcache directory somewhere

Xav Paice (xavpaice)
Changed in telegraf-charm:
assignee: nobody → Xav Paice (xavpaice)
Revision history for this message
Xav Paice (xavpaice) wrote :

Fix included in cs:telegraf-22

Changed in telegraf-charm:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.