Hi @Mert, thanks for posting your questions!
Overall I think your goal here is pretty typical of the workflow for a number of users. The beauty of the
telegraf binary is that each of the collection plugins output the same line protocol when sending to
influxdb regardless of the OS for the given host. You can also specify custom tags in your modules that you could use as template variables in grafana/chronograf. In this case if you know you’re deploying a telegraf agent on a windows + linux host you might have a custom tag called
os=<windows|linux> as necessary and use that as part of your queries.
It usually comes down to personal preference on how to store this into
influxdb itself, whether you split into different databases based on your particular needs or keep them in one contiguous unit.
While there isn’t any prescription on how best to store this data, some things to keep in mind include:
- Retention Policy – think about how long you want to keep data around for in your
- Cardinality – a rough estimate of the uniqueness of your data, you’ll want to make sure you don’t define too many
field combinations that would drive your cardinality too high as this would impact query performance
- Enabling windows-specific collection agents – there are two plugins that are only capable of collecting on Windows machines, the win_perf_counters and win_services plugins. Following the guide there in the README might give better insight into how to configure your nodes
- Use grafana templates – the folks at grafana have a public repo of dashboard templates that might help you get started
Hope that helps to get you going, definitely post back any questions as you get along and let us know what you build!