Hi all,I've noted that on new version of an database probe (oracle/sqlserver) at header exist an "delete" argument after the tag.Based on this, i've tried to delete obsolete tresholds and exclude lists using distribute process with some like this:
<checkpoints> overwrite <database_state> overwrite active = yes description = Monitors database state qos = yes qos_list = yes clear_msg = database_state_1 clear_sev = clear scheduling = rules condition = != column = state key = $object samples = 5 exclude_defs = yes include_defs = yes use_exclude = no use_include = no msg_variables = $check.x;$profile.x;$instance.x;$object.c;$state.i;$state_desc.x type = 2 interval = 1 min sql_timeout = 2 min <excludes> delete <0> delete pattern = ProjectServer_Reporting_SP </0> <1> delete pattern = ProjectServer_Reporting_SharepointB2W </1> <2> delete pattern = ProjectServer_Reporting_INFRA </2> <3> delete pattern = ProjectServer_Published_INFRA </3> <4> delete pattern = ProjectServer_Draft_SP </4> <5> delete pattern = ProjectServer_Draft_SharepointB2W </5> <6> delete pattern = ProjectServer_Draft_INFRA </6> <7> delete pattern = ProjectServer_Archive_SP </7> <8> delete pattern = ProjectServer_Archive_SharepointB2W </8> <9> delete pattern = ProjectServer_Archive_INFRA </9> </excludes> <qos_lists> overwrite <0> overwrite qos_name = database_state qos_desc = SQL Server Database State qos_unit = State qos_abbr = State qos_value = state qos_key = $object qos_max = </0> </qos_lists> <thresholds> overwrite <default> overwrite <0> overwrite tagid = 0 value = 0 unit = minutes sev = critical msg = database_state_2 condition = != clear_msg = database_state_1 scheduling = rules key_col_name = key_col_value = default </0> </default> </thresholds> </database_state></checkpoints>
This have installed successfully and the "pattern" was cleared but the sequencer (id) stay in configuration.Anyone got success on remove all tresholds/messages/exclude/include from an checkpoint based on a single "fix" configuration file (oracle_monitor.cfx / sqlserver_monitor.cfx) ??
If you are trying to remove an entire section from the config file rather than individual keys, you have to use the "clear" tag rather than "delete". If you switch your config to "<excludes> clear", you should be able to skip all of the individual exclude entries from the CFX file.
Here is a brief example to illustrate the difference between the tags...
<setup> loglevel = 0</setup><profiles> <server1> active = yes ip = 192.168.0.11 </server1> <server2> active = yes ip = 192.168.0.12 </server2> <server3> active = yes ip = 192.168.0.13 </server3> <server4> active = yes ip = 192.168.0.14 </server4></profiles>
<profiles> <server1> delete </server1> <server2> delete ip = </server2> <server3> clear </server3></profiles>
Config after applying CFX file:
<setup> loglevel = 0</setup><profiles> <server1> active = yes ip = 192.168.0.11 </server1> <server2> active = yes </server2> <server4> active = yes ip = 192.168.0.14 </server4></profiles>