You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using your plugin to configure collectd to a cluster of around 700 hundred machines. Thank you for the plugin, it seems to work very well and make it very easy to setup.
I have been using it for a while but now I changed something and I realized the problem doing a fresh server installation, seeing something weird.
In the first run of puppet, it loads collectd, installs everything and loads plugins, applying some parts of the configuration in some files. Then, it doesn't apply most of the plugins specific configurations until I don't run puppet for the second time. I am not sure it is a problem with how I'm doing it, but my config is simple.
My main problem comes because I want the cpu plugin to group all cpus in one value, so it uses less disk space since we have some servers with several cpus, but if I have it one hour sending all the metrics for each cpu then the main purpose of the option to group metrics goes away.
I could create a cron that deletes all cpu-* directories, but doesn't look like the ideal option.
What behavior did you expect instead
Well, what I would expect is to write configuration directly in the first run but, again, this is just because I'm not sure if is caused by our configuration or not, but I don't see anything
Output log
This is the output for the first run, it installs everything specified in classes included in the top of the puppet yaml.
Here is the output of the second run of puppet where you can see the actual options of the CPU plugin (as an example) being added.
Any additional information you'd like to impart
So, I think that's all, thank you so much,
Jordi
The text was updated successfully, but these errors were encountered:
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
I have been using your plugin to configure collectd to a cluster of around 700 hundred machines. Thank you for the plugin, it seems to work very well and make it very easy to setup.
I have been using it for a while but now I changed something and I realized the problem doing a fresh server installation, seeing something weird.
In the first run of puppet, it loads collectd, installs everything and loads plugins, applying some parts of the configuration in some files. Then, it doesn't apply most of the plugins specific configurations until I don't run puppet for the second time. I am not sure it is a problem with how I'm doing it, but my config is simple.
My main problem comes because I want the cpu plugin to group all cpus in one value, so it uses less disk space since we have some servers with several cpus, but if I have it one hour sending all the metrics for each cpu then the main purpose of the option to group metrics goes away.
I could create a cron that deletes all cpu-* directories, but doesn't look like the ideal option.
What behavior did you expect instead
Well, what I would expect is to write configuration directly in the first run but, again, this is just because I'm not sure if is caused by our configuration or not, but I don't see anything
Output log
This is the output for the first run, it installs everything specified in classes included in the top of the puppet yaml.
![1st run](https://user-images.githubusercontent.com/2203956/70922968-5039cc80-2027-11ea-91f9-1ba96aa0f1f2.png)
![2nd run](https://user-images.githubusercontent.com/2203956/70922969-50d26300-2027-11ea-9664-9fee5ccb26f8.png)
Here is the output of the second run of puppet where you can see the actual options of the CPU plugin (as an example) being added.
Any additional information you'd like to impart
So, I think that's all, thank you so much,
Jordi
The text was updated successfully, but these errors were encountered: