<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>InfluxData Blog - Support InfluxDB</title>
    <description>Posts by Support InfluxDB on the InfluxData Blog</description>
    <link>https://www.influxdata.com/blog/author/supportat/</link>
    <language>en-us</language>
    <lastBuildDate>Fri, 14 Oct 2016 04:00:48 -0700</lastBuildDate>
    <pubDate>Fri, 14 Oct 2016 04:00:48 -0700</pubDate>
    <ttl>1800</ttl>
    <item>
      <title>InfluxData's Q&amp;A Session for Oct 13: Intro to InfluxDB Telegraf and the Plugin Ecosystem</title>
      <description>&lt;p&gt;We have posted the video archive for the &lt;a href="https://w2.influxdata.com/training/write-your-own-telegraf-plugin/"&gt;Oct 13: Intro to InfluxDB Telegraf and the Plugin Ecosystem&lt;/a&gt; and the following is a recap of the Q&amp;amp;A session during the training.&lt;/p&gt;

&lt;hr /&gt;

&lt;p&gt;&lt;i&gt;Q: Is Raspberry Pi supported? I had a problem with memory issues using InfluxDB version 0.8.&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;A: We have completely changed the product and build pipeline since v0.8. We now have ARM support. In addition, i&lt;span style="font-weight: 400;"&gt;f you’re looking to upgrade to v1.0 from v0.8 I recommend checking out one of our &lt;a href="https://w2.influxdata.com/resources/migrating-from-influxdb-0-8-and-up-to-1-0/"&gt;&lt;span style="font-weight: 400;"&gt;technical papers&lt;/span&gt;&lt;/a&gt;&lt;span style="font-weight: 400;"&gt; which goes into detail about the differences between the versions and the migration steps.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;

&lt;hr /&gt;

&lt;p&gt;&lt;i&gt;&lt;span style="font-weight: 400;"&gt;&lt;!--more--&gt;Q: In the beginning, you mentioned that timestamps can automatically be assigned.  Does Telegraf assign a timestamp when it receives each event? Or does this only happen when InfluxDB receives it?&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;&lt;span style="font-weight: 400;"&gt;A: InfluxDB Telegraf will assign timestamps as well.&lt;/span&gt;&lt;/p&gt;

&lt;hr /&gt;

&lt;p&gt;&lt;i&gt;&lt;span style="font-weight: 400;"&gt;Q: How would you recommend ensuring High Availability of each Telegraf agent? Specifically, regarding the host.&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;&lt;span style="font-weight: 400;"&gt;A: Load balancing an array of Telegraf instances works well for this. On a host level the systemd unit file that comes with the process should be sufficient. &lt;/span&gt;&lt;span style="font-weight: 400;"&gt;&lt;span style="font-weight: 400;"&gt;Please note that currently,  Telegraf does not support High Availability by itself. The best way to keep the agent up and running is through an external system. For example, you can run Telegraf inside a docker container and expose system resources/volumes to it so it can monitor host-level metrics.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;

&lt;hr /&gt;

&lt;p&gt;&lt;i&gt;&lt;span style="font-weight: 400;"&gt;Q: How does the exec process management work? I am familiar with collectd.&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;&lt;span style="font-weight: 400;"&gt;&lt;span style="font-weight: 400;"&gt;A: Exec will trigger your program and wait for it to produce output metrics until the configured timeout.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;

&lt;hr /&gt;

&lt;p&gt;&lt;i&gt;&lt;span style="font-weight: 400;"&gt;Q: So the exec plugin will reap children which don’t respond and restart them?&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;&lt;span style="font-weight: 400;"&gt;&lt;span style="font-weight: 400;"&gt;A: The plugin does not currently keep track of children processes. It is a good suggestion for future development.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;

&lt;hr /&gt;

&lt;p&gt;&lt;i&gt;&lt;span style="font-weight: 400;"&gt;Q: Are there any examples of running Telegraf in Docker - exposing the bits of the host OS to enable system monitoring?&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;&lt;span style="font-weight: 400;"&gt;&lt;span style="font-weight: 400;"&gt;A: We recommend that you look at published Docker guides that will help expose the required endpoints and volumes for system-level monitoring with Telegraf from inside the container.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;

&lt;hr /&gt;

&lt;p&gt;Please make sure you sign up for our next free training session on &lt;strong&gt;&lt;a href="https://w2.influxdata.com/training/7-intro-kapacitor-alerting-anomaly-detection/"&gt;“Intro to Kapacitor for Alerting and Anomaly Detection” webinar on 10/20&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt; &lt;/p&gt;
</description>
      <pubDate>Fri, 14 Oct 2016 04:00:48 -0700</pubDate>
      <link>https://www.influxdata.com/blog/influxdatas-qa-session-for-oct-13-intro-to-telegraf-and-the-plugin-ecosystem/</link>
      <guid isPermaLink="true">https://www.influxdata.com/blog/influxdatas-qa-session-for-oct-13-intro-to-telegraf-and-the-plugin-ecosystem/</guid>
      <category>Use Cases</category>
      <category>Developer</category>
      <author>Support InfluxDB (InfluxData)</author>
    </item>
  </channel>
</rss>
