| import{_ as i}from"./telegraf-en-Dkx3-E-P.js";import{_ as l,a as o}from"./Telegraf_2-BQSVg6VR.js";import{_ as r,c as p,b as n,d as e,e as s,a as d,f as c,r as u,o as g}from"./app-C8175JBb.js";const m={};function f(h,t){const a=u("RouteLink");return g(),p("div",null,[t[12]||(t[12]=n('<h1 id="telegraf-plugin-iotdb" tabindex="-1"><a class="header-anchor" href="#telegraf-plugin-iotdb"><span>Telegraf Plugin(IoTDB)</span></a></h1><h2 id="_1-product-overview" tabindex="-1"><a class="header-anchor" href="#_1-product-overview"><span>1. Product Overview</span></a></h2><h3 id="_1-1-telegraf" tabindex="-1"><a class="header-anchor" href="#_1-1-telegraf"><span>1.1 Telegraf</span></a></h3><p><a href="https://www.influxdata.com/time-series-platform/telegraf/" target="_blank" rel="noopener noreferrer">Telegraf</a> is an open-source agent designed for collecting, processing, and transmitting metrics and telemetry data, developed by InfluxData.</p><p>Telegraf offers the following key features:</p><ul><li>Plugin Architecture: Telegraf’s power lies in its extensive plugin ecosystem. It supports a wide range of input, output, and processor plugins, seamlessly integrating with various data sources and destinations. <ul><li>Data Collection: Telegraf excels at gathering metrics from diverse sources, such as system metrics, logs, databases, and more. Its versatility makes it ideal for monitoring applications, infrastructure, and IoT devices.</li><li>Output Destinations: Once collected, data can be routed to multiple output destinations, including popular databases like InfluxDB. This flexibility allows Telegraf to adapt to diverse monitoring and analytics setups.</li></ul></li><li>Simple Configuration: Telegraf configurations are managed via TOML files. This simplicity enables users to easily define inputs, outputs, and processors, streamlining customization.</li><li>Community & Support: As an open-source project, Telegraf benefits from an active community. Users can contribute plugins, report issues, and seek assistance through forums and documentation.</li></ul><h3 id="_1-2-telegraf-iotdb-plugin" tabindex="-1"><a class="header-anchor" href="#_1-2-telegraf-iotdb-plugin"><span>1.2 Telegraf-IoTDB Plugin</span></a></h3><p>The Telegraf-IoTDB plugin enables exporting monitoring data stored in Telegraf to IoTDB. This output plugin connects and writes data using the IoTDB session interface.</p><figure><img src="'+i+'" alt="" tabindex="0" loading="lazy"><figcaption></figcaption></figure><h2 id="_2-installation-requirements" tabindex="-1"><a class="header-anchor" href="#_2-installation-requirements"><span>2. Installation Requirements</span></a></h2><p>Telegraf supports multiple operating systems, including Linux, Windows, and macOS. To ensure successful installation, it is recommended to run Telegraf with administrator (root) privileges. For detailed requirements, refer to <a href="https://docs.influxdata.com/telegraf/v1/install/" target="_blank" rel="noopener noreferrer">Installation Requirements</a>.</p><h2 id="_3-installation-steps" tabindex="-1"><a class="header-anchor" href="#_3-installation-steps"><span>3. Installation Steps</span></a></h2><p>For specific installation instructions, see <a href="https://docs.influxdata.com/telegraf/v1/install/" target="_blank" rel="noopener noreferrer">Installation Steps</a>.</p><ul><li>Note: This plugin is a built-in plugin of Telegraf and requires no additional installation.</li></ul><h2 id="_4-usage-guide" tabindex="-1"><a class="header-anchor" href="#_4-usage-guide"><span>4. Usage Guide</span></a></h2><h3 id="_4-1-configuring-input-sources" tabindex="-1"><a class="header-anchor" href="#_4-1-configuring-input-sources"><span>4.1 Configuring Input Sources</span></a></h3><p>In the <code>telegraf.conf</code> configuration file, locate the <code>INPUT PLUGINS</code> section to define input sources. Key configuration parameters are listed below:</p>',17)),e("table",null,[t[11]||(t[11]=e("thead",null,[e("tr",null,[e("th",null,[e("strong",null,"Parameter")]),e("th",null,[e("strong",null,"Description")]),e("th",null,[e("strong",null,"Notes")])])],-1)),e("tbody",null,[t[5]||(t[5]=e("tr",null,[e("td",null,"alias"),e("td",null,"Name the plugin instance."),e("td")],-1)),t[6]||(t[6]=e("tr",null,[e("td",null,"interval"),e("td",null,"Frequency for collecting metrics. Adjust this to reduce data rate limits."),e("td",null,"Default plugins use a global interval; override here for specific inputs.")],-1)),t[7]||(t[7]=e("tr",null,[e("td",null,"precision"),e("td",null,"Override the agent’s precision setting. Metrics are rounded to this value."),e("td",null,"When set for a service input (e.g., statsd), the database may merge events with identical timestamps.")],-1)),t[8]||(t[8]=e("tr",null,[e("td",null,"collection_jitter"),e("td",null,"Override the agent’s collection_jitter setting. Adds randomness to intervals."),e("td",null,"Helps stagger data collection across multiple inputs.")],-1)),e("tr",null,[t[3]||(t[3]=e("td",null,"name_override",-1)),t[4]||(t[4]=e("td",null,"Custom time series path name for output to IoTDB.",-1)),e("td",null,[t[1]||(t[1]=s("The path name must comply with the ")),d(a,{to:"/UserGuide/latest/SQL-Manual/Syntax-Rule.html"},{default:c(()=>t[0]||(t[0]=[s("syntax rules")])),_:1}),t[2]||(t[2]=s("."))])]),t[9]||(t[9]=e("tr",null,[e("td",null,"name_prefix"),e("td",null,"Prefix appended to the measurement name."),e("td")],-1)),t[10]||(t[10]=e("tr",null,[e("td",null,"name_suffix"),e("td",null,"Suffix appended to the measurement name."),e("td")],-1))])]),t[13]||(t[13]=n('<figure><img src="'+l+'" alt="" tabindex="0" loading="lazy"><figcaption></figcaption></figure><h3 id="_4-2-configure-output-source" tabindex="-1"><a class="header-anchor" href="#_4-2-configure-output-source"><span>4.2 Configure Output Source</span></a></h3><p>Find the <code>outputs.iotdb </code>section in the <code>telegraf.conf</code> configuration file to configure the output source. Specific configuration items are shown in the following table. For configuration examples, refer to the <a href="https://docs.influxdata.com/telegraf/v1/configuration/#output-configuration-examples" target="_blank" rel="noopener noreferrer">Output Source Examples</a>.</p><table><thead><tr><th><strong>Configuration Item</strong></th><th><strong>Description</strong></th><th><strong>Before Modification</strong></th><th><strong>After Modification</strong></th><th><strong>Notes</strong></th></tr></thead><tbody><tr><td>host</td><td>IoTDB host address</td><td># host = "127.0.0.1"</td><td>host = "deployment host of IoTDB"</td><td>Default: 127.0.0.1</td></tr><tr><td>port</td><td>IoTDB port number</td><td># port = "6667"</td><td>port = "deployment port of IoTDB"</td><td>Default: 6667</td></tr><tr><td>user</td><td>IoTDB username</td><td># user = "root"</td><td>user = "IoTDB username"</td><td>Default: root</td></tr><tr><td>password</td><td>IoTDB password</td><td># password = "root"</td><td>password = "IoTDB password"</td><td>Default: root</td></tr><tr><td>timestamp_precision</td><td>Timestamp precision</td><td>timestamp_precision = "millisecond"</td><td>timestamp_precision = "same timestamp precision as IoTDB"</td><td>Check "timestamp_precision" field in "iotdb-system.properties"</td></tr><tr><td>sanitize_tag</td><td>Database version compatibility</td><td>N/A</td><td>sanitize_tag = "0.13/1.0/1.1/1.2/1.3"</td><td>Configure according to the actual IoTDB version</td></tr></tbody></table><figure><img src="'+o+`" alt="" tabindex="0" loading="lazy"><figcaption></figcaption></figure><h3 id="_4-3-start-telegraf-service" tabindex="-1"><a class="header-anchor" href="#_4-3-start-telegraf-service"><span>4.3 Start Telegraf Service</span></a></h3><div class="language-bash line-numbers-mode" data-highlighter="shiki" data-ext="bash" data-title="bash" style="background-color:#282c34;color:#abb2bf;"><pre class="shiki one-dark-pro vp-code"><code><span class="line"><span style="color:#61AFEF;">telegraf</span><span style="color:#D19A66;"> -config</span><span style="color:#98C379;"> /path/to/telegraf.conf</span></span></code></pre><div class="line-numbers" aria-hidden="true" style="counter-reset:line-number 0;"><div class="line-number"></div></div></div><h2 id="_5-usage-example" tabindex="-1"><a class="header-anchor" href="#_5-usage-example"><span>5. Usage Example</span></a></h2><p>The following example demonstrates how to use Telegraf to collect CPU metrics and output them to IoTDB using the Telegraf-IoTDB plugin.</p><ol><li>Generate a Configuration File</li></ol><p>Use the <code>telegraf</code> command to generate a sample configuration file for CPU input and IoTDB output:</p><div class="language-bash line-numbers-mode" data-highlighter="shiki" data-ext="bash" data-title="bash" style="background-color:#282c34;color:#abb2bf;"><pre class="shiki one-dark-pro vp-code"><code><span class="line"><span style="color:#61AFEF;">telegraf</span><span style="color:#D19A66;"> --sample-config</span><span style="color:#D19A66;"> --input-filter</span><span style="color:#98C379;"> cpu</span><span style="color:#D19A66;"> --output-filter</span><span style="color:#98C379;"> iotdb</span><span style="color:#ABB2BF;"> > </span><span style="color:#98C379;">cpu_iotdb.conf</span></span></code></pre><div class="line-numbers" aria-hidden="true" style="counter-reset:line-number 0;"><div class="line-number"></div></div></div><ol start="2"><li>Modify the Input Plugin Configuration</li></ol><p>In the <code>cpu_iotdb.conf</code> file, locate the <code>[[inputs.cpu]]</code> section and configure it as follows. The <code>name_override</code> field defines the custom time series path in IoTDB:</p><div class="language-bash line-numbers-mode" data-highlighter="shiki" data-ext="bash" data-title="bash" style="background-color:#282c34;color:#abb2bf;"><pre class="shiki one-dark-pro vp-code"><code><span class="line"><span style="color:#7F848E;font-style:italic;"># Read metrics about cpu usage</span></span> |
| <span class="line"><span style="color:#ABB2BF;">[[inputs.cpu]]</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Whether to report per-cpu stats or not</span></span> |
| <span class="line"><span style="color:#61AFEF;"> percpu</span><span style="color:#98C379;"> =</span><span style="color:#D19A66;"> true</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Whether to report total system cpu stats or not</span></span> |
| <span class="line"><span style="color:#61AFEF;"> totalcpu</span><span style="color:#98C379;"> =</span><span style="color:#D19A66;"> true</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## If true, collect raw CPU time metrics</span></span> |
| <span class="line"><span style="color:#61AFEF;"> collect_cpu_time</span><span style="color:#98C379;"> =</span><span style="color:#D19A66;"> false</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## If true, compute and report the sum of all non-idle CPU states</span></span> |
| <span class="line"><span style="color:#61AFEF;"> report_active</span><span style="color:#98C379;"> =</span><span style="color:#D19A66;"> false</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## If true and the info is available then add core_id and physical_id tags</span></span> |
| <span class="line"><span style="color:#61AFEF;"> core_tags</span><span style="color:#98C379;"> =</span><span style="color:#D19A66;"> false</span></span> |
| <span class="line"><span style="color:#61AFEF;"> name_override</span><span style="color:#98C379;"> =</span><span style="color:#98C379;"> "root.demo.telgraf.cpu"</span></span></code></pre><div class="line-numbers" aria-hidden="true" style="counter-reset:line-number 0;"><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div></div></div><ol start="3"><li>Configure the IoTDB Output Plugin</li></ol><p>Locate the <code>[[outputs.iotdb]]</code> section in <code>cpu_iotdb.conf</code> and modify the settings as shown below. Ensure alignment with your IoTDB deployment parameters.</p><table><thead><tr><th><strong>Configuration Item</strong></th><th><strong>Description</strong></th><th><strong>Before Modification</strong></th><th><strong>After Modification</strong></th><th><strong>Notes</strong></th></tr></thead><tbody><tr><td>host</td><td>IoTDB host address</td><td># host = "127.0.0.1"</td><td>host = "your_iotdb_host"</td><td>Default: 127.0.0.1</td></tr><tr><td>port</td><td>IoTDB port number</td><td># port = "6667"</td><td>port = "your_iotdb_port"</td><td>Default: 6667</td></tr><tr><td>user</td><td>IoTDB username</td><td># user = "root"</td><td>user = "your_iotdb_username"</td><td>Default: root</td></tr><tr><td>password</td><td>IoTDB password</td><td># password = "root"</td><td>password = "your_iotdb_password"</td><td>Default: root</td></tr><tr><td>timestamp_precision</td><td>Timestamp precision</td><td>timestamp_precision = "millisecond"</td><td>timestamp_precision = "same_as_iotdb"</td><td>Match the timestamp_precision in iotdb-system.properties</td></tr><tr><td>sanitize_tag</td><td>Database version compatibility</td><td>Not present</td><td>sanitize_tag = "0.13/1.0/1.1/1.2/1.3"</td><td>Configure based on your IoTDB version</td></tr></tbody></table><div class="language-bash line-numbers-mode" data-highlighter="shiki" data-ext="bash" data-title="bash" style="background-color:#282c34;color:#abb2bf;"><pre class="shiki one-dark-pro vp-code"><code><span class="line"><span style="color:#7F848E;font-style:italic;"># Save metrics to an IoTDB Database</span></span> |
| <span class="line"><span style="color:#ABB2BF;">[[outputs.iotdb]]</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Configuration of IoTDB server connection</span></span> |
| <span class="line"><span style="color:#61AFEF;"> host</span><span style="color:#98C379;"> =</span><span style="color:#98C379;"> "127.0.0.1"</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> # port = "6667"</span></span> |
| <span class="line"></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Configuration of authentication</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> # user = "root"</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> # password = "root"</span></span> |
| <span class="line"></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Timeout to open a new session.</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## A value of zero means no timeout.</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> # timeout = "5s"</span></span> |
| <span class="line"></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Configuration of type conversion for 64-bit unsigned int</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## IoTDB currently DOES NOT support unsigned integers (version 13.x).</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## 32-bit unsigned integers are safely converted into 64-bit signed integers by the plugin,</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## however, this is not true for 64-bit values in general as overflows may occur.</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## The following setting allows to specify the handling of 64-bit unsigned integers.</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Available values are:</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## - "int64" -- convert to 64-bit signed integers and accept overflows</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## - "int64_clip" -- convert to 64-bit signed integers and clip the values on overflow to 9,223,372,036,854,775,807</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## - "text" -- convert to the string representation of the value</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> # uint64_conversion = "int64_clip"</span></span> |
| <span class="line"></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Configuration of TimeStamp</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## TimeStamp is always saved in 64bits int. timestamp_precision specifies the unit of timestamp.</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Available value:</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## "second", "millisecond", "microsecond", "nanosecond"(default)</span></span> |
| <span class="line"><span style="color:#61AFEF;"> timestamp_precision</span><span style="color:#98C379;"> =</span><span style="color:#98C379;"> "millisecond"</span></span> |
| <span class="line"></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Handling of tags</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Tags are not fully supported by IoTDB.</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## A guide with suggestions on how to handle tags can be found here:</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## https://iotdb.apache.org/UserGuide/Master/API/InfluxDB-Protocol.html</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ##</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Available values are:</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## - "fields" -- convert tags to fields in the measurement</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## - "device_id" -- attach tags to the device ID</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ##</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## For Example, a metric named "root.sg.device" with the tags \`tag1: "private"\` and \`tag2: "working"\` and</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## fields \`s1: 100\` and \`s2: "hello"\` will result in the following representations in IoTDB</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## - "fields" -- root.sg.device, s1=100, s2="hello", tag1="private", tag2="working"</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## - "device_id" -- root.sg.device.private.working, s1=100, s2="hello"</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> # convert_tags_to = "device_id"</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Handling of unsupported characters</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Some characters in different versions of IoTDB are not supported in path name</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## A guide with suggetions on valid paths can be found here:</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## for iotdb 0.13.x -> https://iotdb.apache.org/UserGuide/V0.13.x/Reference/Syntax-Conventions.html#identifiers</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## for iotdb 1.x.x and above -> https://iotdb.apache.org/UserGuide/V1.3.x/User-Manual/Syntax-Rule.html#identifier</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ##</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Available values are:</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## - "1.0", "1.1", "1.2", "1.3" -- enclose in \`\` the world having forbidden character</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## such as @ $ # : [ ] { } ( ) space</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## - "0.13" -- enclose in \`\` the world having forbidden character</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## such as space</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ##</span></span> |
| <span class="line"><span style="color:#7F848E;font-style:italic;"> ## Keep this section commented if you don't want to sanitize the path</span></span> |
| <span class="line"><span style="color:#61AFEF;"> sanitize_tag</span><span style="color:#98C379;"> =</span><span style="color:#98C379;"> "1.3"</span></span></code></pre><div class="line-numbers" aria-hidden="true" style="counter-reset:line-number 0;"><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div></div></div><ol start="4"><li>Run Telegraf with the Configuration File</li></ol><p>Start Telegraf using the <code>cpu_iotdb.conf</code> file.</p><p>After running Telegraf for a period of time, you can query the collected CPU metrics in IoTDB. Use IoTDB’s CLI or REST API to verify the data.</p>`,22))])}const q=r(m,[["render",f],["__file","Telegraf.html.vue"]]),T=JSON.parse('{"path":"/UserGuide/latest/Ecosystem-Integration/Telegraf.html","title":"Telegraf Plugin(IoTDB)","lang":"en-US","frontmatter":{"description":"Telegraf Plugin(IoTDB) 1. Product Overview 1.1 Telegraf Telegraf is an open-source agent designed for collecting, processing, and transmitting metrics and telemetry data, develo...","head":[["link",{"rel":"alternate","hreflang":"zh-cn","href":"https://iotdb.apache.org/zh/UserGuide/latest/Ecosystem-Integration/Telegraf.html"}],["meta",{"property":"og:url","content":"https://iotdb.apache.org/UserGuide/latest/Ecosystem-Integration/Telegraf.html"}],["meta",{"property":"og:site_name","content":"IoTDB Website"}],["meta",{"property":"og:title","content":"Telegraf Plugin(IoTDB)"}],["meta",{"property":"og:description","content":"Telegraf Plugin(IoTDB) 1. Product Overview 1.1 Telegraf Telegraf is an open-source agent designed for collecting, processing, and transmitting metrics and telemetry data, develo..."}],["meta",{"property":"og:type","content":"article"}],["meta",{"property":"og:image","content":"https://iotdb.apache.org/img/telegraf-en.png"}],["meta",{"property":"og:locale","content":"en-US"}],["meta",{"property":"og:locale:alternate","content":"zh-CN"}],["meta",{"property":"og:updated_time","content":"2025-04-11T03:39:09.000Z"}],["meta",{"property":"article:modified_time","content":"2025-04-11T03:39:09.000Z"}],["script",{"type":"application/ld+json"},"{\\"@context\\":\\"https://schema.org\\",\\"@type\\":\\"Article\\",\\"headline\\":\\"Telegraf Plugin(IoTDB)\\",\\"image\\":[\\"https://iotdb.apache.org/img/telegraf-en.png\\",\\"https://iotdb.apache.org/img/Telegraf\\\\\\\\_1.png\\",\\"https://iotdb.apache.org/img/Telegraf\\\\\\\\_2.png\\"],\\"dateModified\\":\\"2025-04-11T03:39:09.000Z\\",\\"author\\":[]}"]]},"headers":[{"level":2,"title":"1. Product Overview","slug":"_1-product-overview","link":"#_1-product-overview","children":[{"level":3,"title":"1.1 Telegraf","slug":"_1-1-telegraf","link":"#_1-1-telegraf","children":[]},{"level":3,"title":"1.2 Telegraf-IoTDB Plugin","slug":"_1-2-telegraf-iotdb-plugin","link":"#_1-2-telegraf-iotdb-plugin","children":[]}]},{"level":2,"title":"2. Installation Requirements","slug":"_2-installation-requirements","link":"#_2-installation-requirements","children":[]},{"level":2,"title":"3. Installation Steps","slug":"_3-installation-steps","link":"#_3-installation-steps","children":[]},{"level":2,"title":"4. Usage Guide","slug":"_4-usage-guide","link":"#_4-usage-guide","children":[{"level":3,"title":"4.1 Configuring Input Sources","slug":"_4-1-configuring-input-sources","link":"#_4-1-configuring-input-sources","children":[]},{"level":3,"title":"4.2 Configure Output Source","slug":"_4-2-configure-output-source","link":"#_4-2-configure-output-source","children":[]},{"level":3,"title":"4.3 Start Telegraf Service","slug":"_4-3-start-telegraf-service","link":"#_4-3-start-telegraf-service","children":[]}]},{"level":2,"title":"5. Usage Example","slug":"_5-usage-example","link":"#_5-usage-example","children":[]}],"git":{"createdTime":1737376026000,"updatedTime":1744342749000,"contributors":[{"name":"majialin","username":"majialin","email":"107627937+mal117@users.noreply.github.com","commits":1,"url":"https://github.com/majialin"},{"name":"W1y1r","username":"W1y1r","email":"150988475+W1y1r@users.noreply.github.com","commits":1,"url":"https://github.com/W1y1r"},{"name":"leto-b","username":"leto-b","email":"bingqian.bai@timecho.com","commits":2,"url":"https://github.com/leto-b"}]},"readingTime":{"minutes":4.08,"words":1225},"filePathRelative":"UserGuide/latest/Ecosystem-Integration/Telegraf.md","localizedDate":"January 20, 2025","autoDesc":true}');export{q as comp,T as data}; |
