title: How to explain telegraf high cardinality?
body: <p>I need you help regarding to Telegraf monitoring of influxDB instance and a behavior I cannot explain. </p>
  
  <p>The configuration is the following: </p>
  
  <ul>
  <li>Two independent instances of InfluxDB v1.7.10 are running on seperate servers, say <em>server A</em> and <em>server B</em></li>
  <li>Two telegraf services v1.13.4 are running with the same configuration: 
  
  <ul>
  <li>One output being a "monitoring" database created in the influx database</li>
  <li>Several inputs (system, disk, ping, ...) </li>
  </ul></li>
  <li>Grafana is used on both server to explore Telegraf stored values</li>
  </ul>
  
  <p><strong>On server A, which is running fine, the monitoring shard size and cardinality are quite regular. On server B on the other hand, the monitoring shard size and cardinality are much more important (by a factor 10).</strong> </p>
  
  <p>I cannot explain this difference and I have already checked:</p>
  
  <ul>
  <li>tag and field cardinality of the inputs used on both server</li>
  <li>telegraf configuration on both server</li>
  </ul>
  
  <p><strong>Any idea about where to look to explain this behavior ?</strong> </p>
  
  <p>Tanks for your help ! </p>