Hello Alex,
I've just faced up with a little problem while porting the test configuration file from one version of HostMon to another.
The problem is that the test configuration is stored not in .htm-file only but also in the set of *.lst files. Configuration export to the text file doesn't take into account *.lst-file settings, so the schedules, action profiles, notification lists, etc. cannot be exported.
It is just a proposal -- is it possible to implement a configuration export to the text file taking into account the following wishes:
- having only one text file (it is easier to backup / port to another server / another version);
- exporting all the configuration details (alert profiles, schedules, etc) in this file;
Thanks in advance for your consideration.
Best Regards,
Igor Bareev (registered KS-HostMon user)
Configuration export to the text file
Yes, it will be implemented in future.
But I do not understand why you use export/import functions to "porting the test configuration file from one version of HostMon to another"?
HostMonitor can read configuration files those was created by previous versions of the program. Just install new version over old one (using "Update" button in the setup program).
Regards
Alex
But I do not understand why you use export/import functions to "porting the test configuration file from one version of HostMon to another"?
HostMonitor can read configuration files those was created by previous versions of the program. Just install new version over old one (using "Update" button in the setup program).
Regards
Alex
-
- Posts: 6
- Joined: Sun Jan 12, 2003 6:00 pm
- Location: France
I have several reasons for it. First, I would prefer to have only ONE config file to port between pre-prod and prod monitoring hosts. Second, it is just simplier.
This question was raised by unsuccessful upgrade incident (somebody of my team just installed the recent version of KS-HostMonitor over the previous one without upgrading, so all the alarms, e-mail profiles, schedules etc. had been lost. I've spent half a day recovering... but it would be MUCH simplier if I would have a text config file.) With text config, it is more safe to do the upgrade, etc.
Also, I cannot use the binary files in the documentation process. Text file would be better and more clear for this purpose.
P.S. Last question -- do you have any plans about the management console (maybe, MMC-compatible)? I'm running HostMon as service, and it is very inconvinient for the moment to view the status of the tests online or to change configuration online.
This question was raised by unsuccessful upgrade incident (somebody of my team just installed the recent version of KS-HostMonitor over the previous one without upgrading, so all the alarms, e-mail profiles, schedules etc. had been lost. I've spent half a day recovering... but it would be MUCH simplier if I would have a text config file.) With text config, it is more safe to do the upgrade, etc.
Also, I cannot use the binary files in the documentation process. Text file would be better and more clear for this purpose.
P.S. Last question -- do you have any plans about the management console (maybe, MMC-compatible)? I'm running HostMon as service, and it is very inconvinient for the moment to view the status of the tests online or to change configuration online.