Importing templates overwrites existing settings

[skatter]

How can I stop the template import process from overwriting my existing settings? I select "Use defaults for this installation (Recommended)" which I expected to retain my system's settings and only import the new data, but now all of the below "[update]" entries have munged up my existing settings.

Data Template
[success] Interface - Traffic [update]
[success] Interface - Errors/Discards [update]
[success] Interface - Unicast Packets [update]
[success] Interface - Non-Unicast Packets [update]

Graph Template
[success] Interface - Traffic (bits/sec) [update]
[success] Interface - Errors/Discards [update]
[success] Interface - Unicast Packets [update]
[success] Interface - Non-Unicast Packets [update]
[success] Interface - Traffic (bytes/sec) [update]
[success] Interface - Traffic (bits/sec, 95th Percentile) [update]
[success] Interface - Traffic (bits/sec, Total Bandwidth) [update]
[success] Interface - Traffic (bytes/sec, Total Bandwidth) [update]

Data Query
[success] SNMP - Interface Statistics [update]

[skatter]

Anyone?

[skatter]

So if I'm interpreting this correctly, the "Use defaults ..." checkbox is just for retaining the installation's RRA values, but not for retaining existing template information.

Is there a way to import a host template without overwriting existing templates such as Interface - Traffic bits/sec?

[noname]

At the moment, Cacti can't verify templates before importing.
(Perhaps it should be posted as feature requests..)
The template which has same hash code as existing template will overwrite it.

Is there a way to import a host template without overwriting existing templates such as Interface - Traffic bits/sec?

For example -- but it may be very troublesome -- as a workaround:

1) Setup another installation of Cacti as test environment
2) Import new host template to Cacti (test environment)
3) Duplicate all dependencies (host template, graph template, data template, data query, etc.) and bind each other
4) Export the "duplicated" host template
5) Import it to original Cacti (= production environment)

// But I've never tested this way..

[gandalf]

At the moment, Cacti can't verify templates before importing.
(Perhaps it should be posted as feature requests..)

It's a known feature request, created by myself. But it's hard to implement.

The template which has same hash code as existing template will overwrite it.

We call that a feature. This way, you will be able to e.g. import modified/fixed templates

R.

[Patas007]

At the moment, Cacti can't verify templates before importing.
(Perhaps it should be posted as feature requests..)

It's a known feature request, created by myself. But it's hard to implement.

Gandalf, would it be possible to setup import with checkboxes so user can check which templates included in the import file will be imported (overwritten) in Cacti?

The template which has same hash code as existing template will overwrite it.

We call that a feature. This way, you will be able to e.g. import modified/fixed templates

R.

To be honest this "feature" is giving user another overhead with correction of the templates which were overwritten by such "unwanted" import.

My idea "how to add only new templates from given file" or "how to preserve existing templates from being overwritten during template import"

1. export all existing templates (backup)
2. import of new templates (some of existing templates can be overwritten)
3. import templates from backup (this will reverse back the templates overwritten in step 2. New templates will remain added)

Do you agree with this solution?

thank you
PAT

[bigrow]

I've done the same thing.......

if this works it sounds good......

[Nadou21]

Thank's @Patas007, I tried your method and it works perfectly