I think I found a couple of bugs with data templates.
The first one I already brought up in a different thread: The state of the "use per-data source value" checkbox next to the "associated RRAs" in the data template settings screen seems to be ignored. If the checkbox is not checked and I change which RRA's are associated, the change doesn't propogate to all the data sources based on that template.
The second bug has to do with removing a data source item from the data template. I had three data source items in the template but ended up only using two. To reduce the size of the .rrd files and to hopefully speed things up a bit, I went into the data template screen and deleted the one source item I wasn't using. However, all of the data sources that use that temlate still had 3 data source items. To try to fix it, I selected all of the several hundred data source items I have and chose "change data template" and selected the template I was already using. Unfortunately, that didn't reset all the data sources to have only two source items.
Thanks for this product, it's quite handy! (even with the bugs! )
Data template bugs?
Moderators: Developers, Moderators
Re: Data template bugs?
I removed this checkbox from the "Data Input Source" and "Associated RRA's" fields since it was basically useless. These two fields will always be part of the template no matter what. All changes made to the "Associated RRA's" field at the data template level should be propagated to attached data sources now.sparkyflashpants wrote:The first one I already brought up in a different thread: The state of the "use per-data source value" checkbox next to the "associated RRAs" in the data template settings screen seems to be ignored. If the checkbox is not checked and I change which RRA's are associated, the change doesn't propogate to all the data sources based on that template.
This was more like an unfinished feature, but needed finished nevertheless. I took the time to add all of the necessary propagation stuff to make this work. Both adding and removing data source items to a data template should reflect in all of the attached data sources.sparkyflashpants wrote:The second bug has to do with removing a data source item from the data template. I had three data source items in the template but ended up only using two. To reduce the size of the .rrd files and to hopefully speed things up a bit, I went into the data template screen and deleted the one source item I wasn't using. However, all of the data sources that use that temlate still had 3 data source items. To try to fix it, I selected all of the several hundred data source items I have and chose "change data template" and selected the template I was already using. Unfortunately, that didn't reset all the data sources to have only two source items.
I must thank you for pointing me at some of these bugs directly. Not only did I fix the ones you pointed out, but a few additional template related ones as well.
-Ian
Data template bug
I am having the same problem with Data Input Source (Use per datasource input value) in Data Templates. The checkbox value does not stay selected and I cannot create a Data Template with None Data Input Source Selected.
Is there a quick fix for this?
Is there a quick fix for this?
The "Data Input Source" field works the same way as the "Associated RRA's" field. It can never be changed on a per-template basis. The reason for this is because these two fields change too much to justify their use in a template. It would be difficult trying to mantain two data sources using the same data template, both with different data input sources for instance.
As I explained above, I fixed this in the next release so the "use per-data source value" checkbox is not visible for these fields.
-Ian
As I explained above, I fixed this in the next release so the "use per-data source value" checkbox is not visible for these fields.
-Ian
Strong disagreement on use of Data Templates
Ian:
I strongly disagree with you that it is hard to maintain Data Sources that share the same Data Template but are getting their values from different sources. That is the whole point of templating. Like in my cases I am monitoring about 20-30 counters. I would like to use the same RRAs, the same min/max values, the same time steps.... But my data is coming from different sources.
The way you have set up templating I am better off not using it because I need to create 20-30 templates for my counters. The way I describe it above I just need to create one template if you will allow me to vary the Data Input Source and thus templating works as expected. You cannot call it a template if you need to create a template for every single Data Source.
Bragi
I strongly disagree with you that it is hard to maintain Data Sources that share the same Data Template but are getting their values from different sources. That is the whole point of templating. Like in my cases I am monitoring about 20-30 counters. I would like to use the same RRAs, the same min/max values, the same time steps.... But my data is coming from different sources.
The way you have set up templating I am better off not using it because I need to create 20-30 templates for my counters. The way I describe it above I just need to create one template if you will allow me to vary the Data Input Source and thus templating works as expected. You cannot call it a template if you need to create a template for every single Data Source.
Bragi
Who is online
Users browsing this forum: No registered users and 0 guests