Hi, I am sorry if this an elementary question, but I cannot find where to enter data into the 5 custom fields I see in the alarm console. We would like to attempt to use these for filtering as our Usertag_1 and 2 are used already. Thank you.
key = custom_1
value = your value
Thank you Neal,
I assume this is at the probe level? I have attached a screenshot of what I set up, it does not seem to work
I think those configuration options are specific to the NAS and affect the column headings shown in the alarm console rather than the field values.
I think you need to use a pre-processing rule or AO profile to set the custom fields with Lua. Or you can do this from outside the NAS using the set_alarm callback.
Did you restart your alarm console and nas. Below is my setup section hope this helps. If you have multiple nas you will have to put on all I believe.
<setup> debug = 2 logfile = nas.log suppression = yes supp_divisor = 10 supp_approximate = 1 supp_app_len = 30 allow_supp_key = yes allow_close_on_suppkey = yes logging = yes network_logging = no activity_logging = yes transactionlog_filter = 15 transactionlog_size = 1 transactionlog_check = 3600 transactionlog_compress = 3 transactionlog_age = 7 transactionlog_summary = 60 transactionlog_divisor = 10 transactionlog_details = yes name_lookup_mode = 0 activity_flag = 959 distsrv = /MSN-MSP/MSN-Primary/nimbus-hub/distsrv reset_suppkey_on_severity = yes i18n_active = no logsize = 500 <custom_headers> custom_1 = CP Request ID custom_2 = Quick Note </custom_headers> <db_connections> nas = Provider=SQLITE3;Database=database.db tlog = Provider=SQLITE3;Database=transactionlog.db </db_connections></setup>
for the screenshot you are referring to, you would need either lua or perl, to distinguish your action or decision layer, or use Auto Operator on NAS to determine the action of your alarm. If you use Auto Operator, you still need a script to action your decision (see Neal answer on lua definition).
you can also run a perl script to read your config of your probe, decide THERE what you want to happen and then use the set_alarm callback function to enter the string you need into your custom1->custom5.
It's all really down to what you want it to do.
Retrieving data ...