| DBAmon |
|
|
Home |
Index/DBAmon Doc. |
|
|
DBC Common Parameters Parameter
| Description
| Example Value
| Default Value
| DBMS:
| The DBMS (or Software Package) that this DBC file will monitor. Allowed values are:
|
Oracle
| Informix
| EMail_Report:
| This parameter controls whether a weekly DBAmon Instance Report email report is created.
Use this parameter
to specify one or more email addresses to receive the report, if the report is desired. Note that if you're
specifying multiple email addresses, separate them with a comma (NO spaces).
| me1@gmail.com,her2@me.com
| (No report will be created)
| Host:
| The shortest possible hostname espressed in a way that is "reachable".
| catdog
| (None)
| ID1: through ID10:
|
Use this optional parameter for whatever you want. Every time
that a ticket is created, before invoking dbamon_make_tickets, these
values that you specified will be assigned to environment variables
ID1, ID2, etc... Also, if the specify the ID1_Breakout: dbamonrc
parameters, instances with common ID1 values will be grouped together
on separate WWW pages. This can be used, for example, as a way to
segregate instances based on their grography.
| London
| (None)
| Make_Tickets:
|
Instructs DBAmon to never make tickets for events on this instance.
| N
| Y
| Monitor:
| Whether or not to monitor. There are three possible values:
|
B
| Y
| Monitor_Hours:
| If specified, the hours of the day during which monitoring should
occur. For example, if specifed as 01,02,03 then monitoring should
only occur during the 01, 02 and 03 hours every days. If not specified,
then monitoring should occur during all hours of the day. NOTE: Hours
must be specified with 2 digits.
Entries must have a comma and NO SPACES between entries.
| 08,09,10,11,12,13,14,15,16
| (None)
| Monitor_Days:
| If specified, the days of the week during which monitoring should
occur. For example, if specifed as Mon,Tue,Wed,Thu,Fri then monitoring should
only occur during Monday through Friday. If not specified,
then monitoring should occur during all days of the week. NOTE: Days
must be specified as 3 character:
|
Mon,Tue,Wed,Thu,Fri
| (None)
| Monitor_Exclude:
| If specified, the Day-Hour combinations during which monitoring should NOT
occur. For example, if specifed as Mon-13 then monitoring should
NOT occur during the 13 hour of Monday. If not specified,
then monitoring should occur according to the above 2 rules. NOTE: Days
must be specified as 3 characters and hours at 2 characters
with a comma and NO SPACES between entries.
| Mon-13,Mon-14,Sun-03
| (None)
| Must_Be_Up:
| Must Be Online (Y/N). If set to N, only warning events will be
generated if instance is down. This is a good option for test DB's
where you want to monitor the DB when it is up, but you don't care
if it is down.
| N
| Y
| No_Tickets_For_Events:
|
Instructs DBAmon to never make tickets for the events that you specify here. NOTE that you must specify the events as
1 string with no blanks. Example: DBA123,DBA456,DBA789 - Note: DBA123, DBA456, DBA789. In that case, only DBA123 will recognized.
| DBA123,DBA456
|
| Notify_List:
| List number from USERS Section of the
dbamonrc Configuration File. For Critical
events, this is where Emails and Postnotes are sent. | Also, [STAR] can be specified. 3
| (None)
| Pager_Subject: (Obsolete)
|
If Pager_Subject: or Pager_EMail: are specified, then Paging
is activated for this instance.
If this system is to generate pager messages for
critical events, code here the subject part of the EMail message
to the pager gateway (for more details on
the use of a pager gateway, contact me (Bill Border).
| For only, if this value is DUMMY page_dbagap will be invoked. DBAmonMsg
| (None)
| Pager_EMail:
|
If Pager_Subject: or Pager_EMail: are specified, then Paging
is activated for this instance.
The EMail recipient(s) for the pager
gateway message (see above). Up to three fully qualified
EMail ID's separated by spaces.
| 7193334444@mypagervendor.com
| (None)
| Priority:
|
The priority of this instance. This parameter is passed to the Helpdesk Ticket Interface. At
tickets are H=2, M=3, L=4. Specify H, M or L.
| H
| M
| SLA:
|
The desired SLA (Service Delivery Level) for this instance. The values Bronze, Silver, Gold or Platinum
can be used. DBAmon doesn't do much with this, but when a ticket or pager message is sent, the value
is exposed to the Userexits, so you can code the userexits to act based on this value, etc.
| Silver
| (None) or DBAMONRC Default_SLA: value.
| Suppress_Events:
|
A list of DBAmon event Msg-ID's to be suppressed for this instance.
| DBA920,DBA921
| (None)
| Title1:
| A string that descibes this instance. The maximum length for
this parm is 40 characters.
| QA/AppServer2
| (None)
| Title1_URL:
| A URL that you specify that is to be associated with this title
on the System Summary page.
| http://catdog.abc.com/sys/catdog.html
| (None)
| Title2:
| A short string that descibes this instance. We specify the internal
organization here.
| ESG-Roseville
| (None)
| Title2_URL:
| A URL that you specify that is to be associated with this title
on the System Summary page.
| http://catdog.abc.com/t2/catdog.html
| (None)
| Title3:
| Another short string that descibes this instance. We use this field
to describe how we support this DB.
| 5x12:7-7
| (None)
| Userid:
| The userid that DBAmon will remsh to at the remote server. For SAP, this
defaults to DBC SAPSYSTEMNAME: appended with "adm". For example, if SAPSYSTEMNAME
is AB1, then Userid: will default to "ab1adm".
| informix
| (Userid that DBAmon runs under on Master -or- For SAP, SAPSYSTEMNAMEadm)
| Obsolete Parameters
| Download_Every:
|
ONLY USE THIS PARAMETER AT THE DIRECTION OF DBAmon SUPPORT:
Instructs DBAmon to re-download the probe software on every
iteration.
| Y
| N
| DBC_Class:
|
A different way from renaming a DBC file to cause it to be assigned to an alternate class.
| Z
| (None)
| Host_URL:
| A URL that you specify that is to be associated with this hostname
on the System Summary page.
| http://catdog.abc.com/sys/catdog.html
| (None)
| OpC_Application:
| (Optional) The appl part of the OpC message NOTE: If this
field is NON-BLANK, OpC messages will be generated for this host.
|
| (None)
| OpC_Object:
| (Optional) The application part of the OpC message
|
| (None)
| OpC_Msg_Group:
| (Optional) The message group part of the OpC message
|
| (None)
| OpC_Gateway:
| (Optional) This names the system where the opcmsg command
is to be executed. This will be different than the Host:
name only if this system does not run OpC.
|
| (None)
| | ||||||