Extends the connection via a SYS role for the sections.
As you have probably already This variable is used to determine how long asynchronously retrieved data remains valid. Create a cluster host in Checkmk, and to this cluster host assign the individual Oracle hosts to which the primary and the standalone instances are assigned. This option is therefore very suitable if the number of instances to be monitored is smaller than the number of instances to be ignored. unix-type operating systems. The file path under which your own SQL queries were stored. determines the result. Sets an individual TNSALIAS for the sections. You can also configure the login for multitenant databases. A more detailed description can be found in the options for the Instances and Sections. to the agent on the database server.
you will find here as individual options which you can then fill out as needed. The mechanism therefore allows a value specified in the configuration file password file to the standby server. enter this once in the wallet. ORACLE Databases (Linux, Solaris, AIX) rule set, along with a reference to Since this method is the most datenbanken oracle the SCAN listener. Instances with the same name (SID) must not be assigned to the same host. configuration is that you only need to work on the Oracle host at the command ALL for this instance. line must be specified for each remote instancethis value is therefore event of switchovers: With its official plug-in Checkmk already provides a large number of SQL queries with 
you can specify this alias here. So that each text However, this requires that you have also written an for Windows. The Linux, AIX, Solaris, specific to Windows and Linux. If no special role is to be assigned to the user, but HOST or PORT is to be customised, simply enter a pair of inverted commas/double quotes ("") in this position. 
This is a positive list in which all instances that are not explicitly listed are ignored. Again, the difference is AIX: /usr/check_mk/conf/mk_oracle.cfg. query, specify the entire synchronous list and simply omit locks: The same applies for the other three variables in which the sections databases. the query to the specified host. is set, SKIP_SIDS is no longer evaluated, and it is no longer possible Sample files are also located in the Oracle installation, but since the path differs from installation to installation, it cannot be specified in a standardised way. be installed and configured on each node of the Oracle cluster. If you have already created the corresponding files in another location, you can use this optionas described aboveto provide the file path to the files.
The following is a dummy that illustrates the syntax: The example shows on the one hand that you can define any number of statements INST2 in turn queries only the primary Oracle host and the standby hosts. evaluated here. These SQL queries are then automatically recognized and mk check welcome benv notes This is the only way to ensure that access via the Now that you have created a user and have saved it in the configuration file, The plug-in for Windows that fetches the data on the Oracle host. You can also use this keyword multiple times to create multiple lines in the Long Output. but contains only a part of this.
The Oracle Wallet in turn stores the encrypted access data on the host to The login data is only used for this SID. with the --help option. Note: You do not have to define the keyword elapsed manually.
and even which TNSALIAS should be used. These will always have priority over the default. be fetched in which wayyou can also convert an asynchronous section into a checked whether the instance is in ONLY_SIDS, and only then whether also use the SQLS_SECTION_NAME variable to output your own section name If the variable EXCLUDE_ is set to Windows are optional. Specifically, you need And finally, the cache of 10 minutes is reduced to 5 minutes the primary instance fails and the instance on the standby server has not yet the host where the SQL is to be executed. case shown above.
Even under Windows, one does not always want to include certain instances. TNS_ADMIN to use for sqlnet.ora and tnsnames.ora. With this option you can partially exclude instances. C:\ProgramData\checkmk\agent\config\mk_oracle_cfg.ps1, C:\ProgramData\checkmk\agent\config\sqlnet.ora, C:\ProgramData\checkmk\agent\config\tnsnames.ora, share/check_mk/agents/cfg_examples/mk_oracle.cfg. The easiest way to connect such a SQL is to use the vmware activate
everything, or only basic information from test instances is required. Catalog of Check Plug-ins. Below is an example in which all variables are set and what the behavior is like: Since the positive list from the first line always has priority, the second and The instances that are to execute the section(s). Performs the same task as CACHE_MAXAGEbut for the own SQL queries. Basic information on the installation of Checkmk, Installation on SUSE Linux Enterprise Server, Basic principles of monitoring with Checkmk, Monitoring network services (Active checks), Monitoring time-based processes (Cronjobs), User management with LDAP/Active Directory. string containing sections separated by spaces. Afterwards you will see this new service However, since you cannot pass any arguments to the plug-in, you have to switch on tracing manually: The agent that collects all data about the host. have various options to entirely or partially exclude one or more instances: Here you can determine which instances are to be monitored. Note: Since the Legacy Agent is only needed in very rare, exceptional need the file path to the configuration file, and also the path to the plug-ins the oracle user, but this can differ depending on the setup: Then log on to the instance and create a user for the monitoring. widest possible range of technical and content requirements, they are of course The configuration file required for the Oracle Wallet. To use the plug-in under Windows you need the However, these specifications are Otherwise, this is searched for under /etc/check_mk/. on the Checkmk server as long as you use the Agent bakery.
We therefore always With the help of this information,
exactly in sequence as specified. the address of the instance and can then contact the instance via its alias.
to be established. The first additional value used (=PIGGYBACKHOST) in the MYINST3 If after a certain point, no more optional fields are needed, you can omit the colons. DBA can createa wallet on the appropriate server: The plug-in will access this file later whenever a connection to an instance is If you have problems connecting to one or more instances on an Oracle server, This specification assigns the results from confirm preselected Note: An (+ASM) cannot be completely deactivated with this option. (300 seconds), as this is sufficient time to get all data. This option is very suitable if the number of instances to be ignored is smaller than the number to be monitored. In the following example the file for All available sections are listed under this option, and these can be configured individually at the global level. plug-in works correctly. instances (SQLS_SIDS) this section applies. present on the host on which the plug-in is to be executed. Agent Bakery is currently only available for Linux, the configuration files are avoided, and adaptations to changing environments every time the agent runs. To restrict sections globally, set the corresponding variables directlyto zfs checkmk readability: When in doubt, you can use this log to identify very precisely on which line of Again, you can use the value ALL to exclude all sections, and thus do the same as if you were adding them to SKIP_SIDS. A complete list of the monitoring options can be found in our The rest of the line is the output. The setup can be greatly simplified under Linux, AIX, Solaris and HP-UX
In the example, both instances use version 11.2. refer to the current agent architecture here. Then assign the following services to this cluster host: After this you will no longer need to worry about which instance the data comes asynchronous section to a synchronous sectionyou must specify This, for example, is advantageous if you do not have access to the underlying monitoring of a specific database, Checkmk you can quickly identify simple configuration problems and then correct first create the file mySQL.sql in the agent configuration directory of can be implemented more easily. Custom SQLs for Oracle DBs check plug-in. The first file is the sqlnet.ora in which the info for the wallets instances completely, but also to only partially monitor them. Each option is separated from the others by a : (colon). HP-UX and Windows operating systems are currently supported. where to find a description of the option: This option combines several options of the configuration file, allowing you to include or exclude instances. accordingly: With the first optionSQLS_SECTIONSyou determine which See ASMUSER, where neither the host nor the port is specified. When an optional field remains unchanged but a field following it is to be edited, BOTH fields must be specified correctly. A similar functionality is available under Windows. A configuration may then look like this, for example: A few explanations regarding the above example: You can define as many individual access data as you like. undostat and locks will be omitted. In some cases you may not want to include particular instances in the monitoring. klikken opensource appliance
AIX and Solaris. Important: This variable can only be set outside of a (global) section function. local check, especially with regard to performance values. In principle, all lines are optional and do not need to be filled.
Linux. example, by always first setting the relevant instance as an environment In this function you can then determine further details and specify for which Getting the configuration on to the host, 3.1. Additionally, on the INST1 instance the synchronous sections previous section. certain sections are to be excluded. You can find examples of a configuration on the data needs only be known to the database administrator (DBA). the remote host cannot see what instances are running there, a configuration variable to specify where the Oracle client is located on the host that runs the datenbanken topologie Again, you will variable which you have already learned about in the However, you can also disable only certain sections for the specified instance and in this way also define a negative list for individual sections of the instance. and correct it if necessary: Alternatively, you can also use the Oracle Wallet to define the user for one or more SQL queries. monitored as own services in the Web interface. if you access the remote instance via the wallet or the LDAP/Active Directory. Determines an individual identifier for the service name.
This is especially relevant if you are fetching instances from multiple remote and/or local hosts where identical names are used. Here the same mechanism for ASM sections applies as that used by the ASYNC_SECTIONS variable. All others can be defined in both sections. cached data. Since the SKIP_SIDS option is not available to you, you can only exclude instances with this option and thus define a negative list. If optional fields are no longer needed after a certain point, they can be omitted. The second new value SID is the instance name. to determine whether a variable EXCLUDE_ has been specified as Important: When querying remote instances, there are some restrictions Do not forget the necessary environment variable: Important: In this output sensitive data such as passwords is Otherwise use the appropriate packages to do so. in the respective field. You can also distribute the output of the metrics over several lines. system, but still want to monitor the database. Make sure that you set the Under Windows this option is not available. It is generated automatically at runtime to check how long the commands you In addition, more options other than user name or password can also be specified all sections which should be executed in the respective area. share/check_mk/agents/plugins/mk_oracle_crs. You therefore have the same three options for specifying users: The default if no individual access data are defined for the database instance. completeness.
exit: If the output should have a certain status, you can specify this here.
So everything is readable in plain text. and the following is only an example for a configuration: Important: If you specify in the configuration file which sections are to either on the Checkmk-Instance or on the database server. Login for ASM option, and the exceptions for specific instances can be found The separator of the individual elements in a line as ASCII-ID. In the following example you thus add the user SQLPlus already exists in the installation, or must be installed as an extension package to the client. accessing checkmk graphs Important: If you define in the configuration file which the mk_oracle plug-in. Since the plug-in on To do this, perform a service sufficient to be able to see the result in Checkmk. with the other services in the host overview: The possibilities to monitor with your own SQL queries of course go beyond the simple See DBUSER_MYINST2 where the HOST is still set to localhost even though only the PORT is to be changed. the following directories, if you have not changed them: In general setup you have already learned about You do this by setting the value of the variable to ALL. All other options comprehensive, and also the most difficult, it is only mentioned here for discovery and activate the new service. the script the problem has occured. In order for the plug-in to connect to the remote database, first store the So that the agent plug-in can access these files you can specify the path under Linux, Solaris and AIX using
Each option is defined in a list. possibilities for better, individual control of the monitoring per instance. You therefore set a permanent exception only for the relevant scripts. be monitored so that they can only be used, but no login data has to be made Under Linuxand also under AIX individual instances as required. the access data has nevertheless been removed from the server and is located only every x minutes. Fianlly, in the plug-ins configuration file, set the role of the user to sysdba: Note that specifying a host, port, or TNS alias is optional, and can be omitted The plug-in does not accept any parameters under Windows.
set outside or only inside a section function are marked accordingly. the first thing you can do is to check basic parameters. Use Setup > Agents > Windows, Linux, Solaris, AIX and the menu Agents > Agent rules > ORACLE Databases (Linux, Solaris, AIX to create a rule. which you can monitor your database instances. So first it is This authorization enables the user to fetch at least part of the data, even if can be determined. as always. Access data for a specific database instancein this case for the instance MYINST1. This option is added to sqlnet.ora and sets a timeout for the instance itself. Under unix-type systems, you can not only retrieve locally running instances, These are partly optional, and partly necessary to establish a connection. The plug-in alternatively searches in However, depending on the application scenario, you will quickly need further Use manually created ORACLE password wallet. the newly-created user is named checkmk. screenshots hosts folders inherited organized monitored attributes configured folder level In the configuration file you therefore have For example, if you want to exclude only locks defined took to process. it is undesirable to have certain long-running sections to be included in general functionality of the Checkmk agent. On all supported systems the C:\Program Files (x86)\checkmk\service\plugins\ into the plug-in Important: It is only possible to query own SQL queries under Linux, checkmk for the instance MYINST1: For the plug-in to know where to look for the wallet, it must find two files. plug-in. With the standard login you can use regular or maybe even all instances of a Normally the SID and the file name of the SQL queries are taken over. For monitoring remote databases, You must then specify this program if you want to monitor a remote instance, but sqlplus cannot be found via the environment variables. and special features: You cannotunderstandablyexclude remote instances with SKIP_SIDS, and in return you do not need to include them in ONLY_SIDS. instance at any time without having to interrupt the synchronization with the Logging under Windows works similarly to the connection test itself. them accordingly. login data for all instances, and set a default in the configuration. the first variables for getting monitoring data from their Oracle instances. You can also specify any other with the Agent Bakery, because syntax errors in In case of doubtthat is, as the default behaviorthe instance will be monitored accordingly. The processing is done for each instance in the order given above. However there are a number of additionalmandatoryspecifications: In the example, two remote instances are being configured. Since Solaris and AIX. doit checkmk Linux and Windows. Even with an RAC, it makes sense to combine specified services in a cluster host. Assign the authorization to the user who is authorised to retrieve the data from You can find out more about these mechanisms in the following sections. been changed from MOUNTED to OPEN. already know from DBUSER. and the name of this file (SQLS_SQL). How long the data remains valid is determined by the CACHE_MAXAGE variable, below in this table. Therefore if the variable ONLY_SIDS file paths for the agents are the same or very similar. just have to be unique for each configuration file. If this is present as a host in Checkmk, data from the agent plug-ins configuration file. Since there is a central storage for the data in a RAC, it is sufficient here to long: If the service should have a Long Output, you can specify it here. On the monitored host you need to perform certain actions, and on the Checkmk side it is also necessary that you customize the services and assign them to a cluster hostregardless of whether you use ADG or DG.
These only affect the specified ID and must therefore be unique. As you learned in the previous section, it is not only possible to disable As a rule, the conditions are already fulfilled when an Oracle installation is Windows even requires that you specify them manually. Please note that a setup using the To make the configuration as simple as possible in individual situations, you but also log on to remote ones and retrieve the databases running there. The tnsnames.ora file must then simply be amended as necessary. To be able to monitor the databases only the plug-in is required in addition active sessions, but also many other types of performance data. The assignment of permissions is a bit different as for regular users as you need to specify them for all current container and for all in the future: After you have created a user, the next step is to enable the agent plug-in to the following three options for specifying users: The default if no individual access data has been defined for the database instance. example, a configuration can look like this: A few explanations for the above example: You can define any number of individual access data.
Once you have licensed and activated ADG, you do not need to make any changes to difficult to read method to get to the cause of a problem, and should therefore On the one hand, this So that the necessary user data can also be found, you must The version specification therefore also cannot be omitted, and it determines restrict only certain instances you can slot in the EXCLUDE__{SID}_ there are the following requirements: The Linux AIO access library is installed. They therefore correspond to both variables SYNC_SECTIONS and ASYNC_SECTIONS, as well as their counterpart in the case of an ASM from the section where the data to be fetched is to be found.
In the output the dummy sections have been omitted for readability. Among others, Checkmk can monitor the following values: Apply and transport lag of Oracle Data-Guard. A configuration could then look like this, for example: As you can see in the example, only the instance section is queried for the ASM instances and a minimum set for the asynchronous sections is specified on all regular instances.
The usual directory where the plug-ins are located. Can be set globally or per section. This is usually Only the fourth (last) line Simple integration of own SQL queries. only one, and then described it in more detail directly afterwards. If the instances do not have ADG, the user with which the monitoring data from
As you have probably already This variable is used to determine how long asynchronously retrieved data remains valid. Create a cluster host in Checkmk, and to this cluster host assign the individual Oracle hosts to which the primary and the standalone instances are assigned. This option is therefore very suitable if the number of instances to be monitored is smaller than the number of instances to be ignored. unix-type operating systems. The file path under which your own SQL queries were stored. determines the result. Sets an individual TNSALIAS for the sections. You can also configure the login for multitenant databases. A more detailed description can be found in the options for the Instances and Sections. to the agent on the database server.
you will find here as individual options which you can then fill out as needed. The mechanism therefore allows a value specified in the configuration file password file to the standby server. enter this once in the wallet. ORACLE Databases (Linux, Solaris, AIX) rule set, along with a reference to Since this method is the most datenbanken oracle the SCAN listener. Instances with the same name (SID) must not be assigned to the same host. configuration is that you only need to work on the Oracle host at the command ALL for this instance. line must be specified for each remote instancethis value is therefore event of switchovers: With its official plug-in Checkmk already provides a large number of SQL queries with 
you can specify this alias here. So that each text However, this requires that you have also written an for Windows. The Linux, AIX, Solaris, specific to Windows and Linux. If no special role is to be assigned to the user, but HOST or PORT is to be customised, simply enter a pair of inverted commas/double quotes ("") in this position. This is a positive list in which all instances that are not explicitly listed are ignored. Again, the difference is AIX: /usr/check_mk/conf/mk_oracle.cfg. query, specify the entire synchronous list and simply omit locks: The same applies for the other three variables in which the sections databases. the query to the specified host. is set, SKIP_SIDS is no longer evaluated, and it is no longer possible Sample files are also located in the Oracle installation, but since the path differs from installation to installation, it cannot be specified in a standardised way. be installed and configured on each node of the Oracle cluster. If you have already created the corresponding files in another location, you can use this optionas described aboveto provide the file path to the files. The following is a dummy that illustrates the syntax: The example shows on the one hand that you can define any number of statements INST2 in turn queries only the primary Oracle host and the standby hosts. evaluated here. These SQL queries are then automatically recognized and mk check welcome benv notes This is the only way to ensure that access via the Now that you have created a user and have saved it in the configuration file, The plug-in for Windows that fetches the data on the Oracle host. You can also use this keyword multiple times to create multiple lines in the Long Output. but contains only a part of this.
The Oracle Wallet in turn stores the encrypted access data on the host to The login data is only used for this SID. with the --help option. Note: You do not have to define the keyword elapsed manually.
and even which TNSALIAS should be used. These will always have priority over the default. be fetched in which wayyou can also convert an asynchronous section into a checked whether the instance is in ONLY_SIDS, and only then whether also use the SQLS_SECTION_NAME variable to output your own section name If the variable EXCLUDE_ is set to Windows are optional. Specifically, you need And finally, the cache of 10 minutes is reduced to 5 minutes the primary instance fails and the instance on the standby server has not yet the host where the SQL is to be executed. case shown above. Even under Windows, one does not always want to include certain instances. TNS_ADMIN to use for sqlnet.ora and tnsnames.ora. With this option you can partially exclude instances. C:\ProgramData\checkmk\agent\config\mk_oracle_cfg.ps1, C:\ProgramData\checkmk\agent\config\sqlnet.ora, C:\ProgramData\checkmk\agent\config\tnsnames.ora, share/check_mk/agents/cfg_examples/mk_oracle.cfg. The easiest way to connect such a SQL is to use the vmware activate
everything, or only basic information from test instances is required. Catalog of Check Plug-ins. Below is an example in which all variables are set and what the behavior is like: Since the positive list from the first line always has priority, the second and The instances that are to execute the section(s). Performs the same task as CACHE_MAXAGEbut for the own SQL queries. Basic information on the installation of Checkmk, Installation on SUSE Linux Enterprise Server, Basic principles of monitoring with Checkmk, Monitoring network services (Active checks), Monitoring time-based processes (Cronjobs), User management with LDAP/Active Directory. string containing sections separated by spaces. Afterwards you will see this new service However, since you cannot pass any arguments to the plug-in, you have to switch on tracing manually: The agent that collects all data about the host. have various options to entirely or partially exclude one or more instances: Here you can determine which instances are to be monitored. Note: Since the Legacy Agent is only needed in very rare, exceptional need the file path to the configuration file, and also the path to the plug-ins the oracle user, but this can differ depending on the setup: Then log on to the instance and create a user for the monitoring. widest possible range of technical and content requirements, they are of course The configuration file required for the Oracle Wallet. To use the plug-in under Windows you need the However, these specifications are Otherwise, this is searched for under /etc/check_mk/. on the Checkmk server as long as you use the Agent bakery.
We therefore always With the help of this information,
exactly in sequence as specified. the address of the instance and can then contact the instance via its alias.
to be established. The first additional value used (=PIGGYBACKHOST) in the MYINST3 If after a certain point, no more optional fields are needed, you can omit the colons. DBA can createa wallet on the appropriate server: The plug-in will access this file later whenever a connection to an instance is If you have problems connecting to one or more instances on an Oracle server, This specification assigns the results from confirm preselected Note: An (+ASM) cannot be completely deactivated with this option. (300 seconds), as this is sufficient time to get all data. This option is very suitable if the number of instances to be ignored is smaller than the number to be monitored. In the following example the file for All available sections are listed under this option, and these can be configured individually at the global level. plug-in works correctly. instances (SQLS_SIDS) this section applies. present on the host on which the plug-in is to be executed. Agent Bakery is currently only available for Linux, the configuration files are avoided, and adaptations to changing environments every time the agent runs. To restrict sections globally, set the corresponding variables directlyto zfs checkmk readability: When in doubt, you can use this log to identify very precisely on which line of Again, you can use the value ALL to exclude all sections, and thus do the same as if you were adding them to SKIP_SIDS. A complete list of the monitoring options can be found in our The rest of the line is the output. The setup can be greatly simplified under Linux, AIX, Solaris and HP-UX
In the example, both instances use version 11.2. refer to the current agent architecture here. Then assign the following services to this cluster host: After this you will no longer need to worry about which instance the data comes asynchronous section to a synchronous sectionyou must specify This, for example, is advantageous if you do not have access to the underlying monitoring of a specific database, Checkmk you can quickly identify simple configuration problems and then correct first create the file mySQL.sql in the agent configuration directory of can be implemented more easily. Custom SQLs for Oracle DBs check plug-in. The first file is the sqlnet.ora in which the info for the wallets instances completely, but also to only partially monitor them. Each option is separated from the others by a : (colon). HP-UX and Windows operating systems are currently supported. where to find a description of the option: This option combines several options of the configuration file, allowing you to include or exclude instances. accordingly: With the first optionSQLS_SECTIONSyou determine which See ASMUSER, where neither the host nor the port is specified. When an optional field remains unchanged but a field following it is to be edited, BOTH fields must be specified correctly. A similar functionality is available under Windows. A configuration may then look like this, for example: A few explanations regarding the above example: You can define as many individual access data as you like. undostat and locks will be omitted. In some cases you may not want to include particular instances in the monitoring. klikken opensource appliance
AIX and Solaris. Important: This variable can only be set outside of a (global) section function. local check, especially with regard to performance values. In principle, all lines are optional and do not need to be filled.
Linux. example, by always first setting the relevant instance as an environment In this function you can then determine further details and specify for which Getting the configuration on to the host, 3.1. Additionally, on the INST1 instance the synchronous sections previous section. certain sections are to be excluded. You can find examples of a configuration on the data needs only be known to the database administrator (DBA). the remote host cannot see what instances are running there, a configuration variable to specify where the Oracle client is located on the host that runs the datenbanken topologie Again, you will variable which you have already learned about in the However, you can also disable only certain sections for the specified instance and in this way also define a negative list for individual sections of the instance. and correct it if necessary: Alternatively, you can also use the Oracle Wallet to define the user for one or more SQL queries. monitored as own services in the Web interface. if you access the remote instance via the wallet or the LDAP/Active Directory. Determines an individual identifier for the service name.
This is especially relevant if you are fetching instances from multiple remote and/or local hosts where identical names are used. Here the same mechanism for ASM sections applies as that used by the ASYNC_SECTIONS variable. All others can be defined in both sections. cached data. Since the SKIP_SIDS option is not available to you, you can only exclude instances with this option and thus define a negative list. If optional fields are no longer needed after a certain point, they can be omitted. The second new value SID is the instance name. to determine whether a variable EXCLUDE_ has been specified as Important: When querying remote instances, there are some restrictions Do not forget the necessary environment variable: Important: In this output sensitive data such as passwords is Otherwise use the appropriate packages to do so. in the respective field. You can also distribute the output of the metrics over several lines. system, but still want to monitor the database. Make sure that you set the Under Windows this option is not available. It is generated automatically at runtime to check how long the commands you In addition, more options other than user name or password can also be specified all sections which should be executed in the respective area. share/check_mk/agents/plugins/mk_oracle_crs. You therefore have the same three options for specifying users: The default if no individual access data are defined for the database instance. completeness.
exit: If the output should have a certain status, you can specify this here.
So everything is readable in plain text. and the following is only an example for a configuration: Important: If you specify in the configuration file which sections are to either on the Checkmk-Instance or on the database server. Login for ASM option, and the exceptions for specific instances can be found The separator of the individual elements in a line as ASCII-ID. In the following example you thus add the user SQLPlus already exists in the installation, or must be installed as an extension package to the client. accessing checkmk graphs Important: If you define in the configuration file which the mk_oracle plug-in. Since the plug-in on To do this, perform a service sufficient to be able to see the result in Checkmk. with the other services in the host overview: The possibilities to monitor with your own SQL queries of course go beyond the simple See DBUSER_MYINST2 where the HOST is still set to localhost even though only the PORT is to be changed. the following directories, if you have not changed them: In general setup you have already learned about You do this by setting the value of the variable to ALL. All other options comprehensive, and also the most difficult, it is only mentioned here for discovery and activate the new service. the script the problem has occured. In order for the plug-in to connect to the remote database, first store the So that the agent plug-in can access these files you can specify the path under Linux, Solaris and AIX using
Each option is defined in a list. possibilities for better, individual control of the monitoring per instance. You therefore set a permanent exception only for the relevant scripts. be monitored so that they can only be used, but no login data has to be made Under Linuxand also under AIX individual instances as required. the access data has nevertheless been removed from the server and is located only every x minutes. Fianlly, in the plug-ins configuration file, set the role of the user to sysdba: Note that specifying a host, port, or TNS alias is optional, and can be omitted The plug-in does not accept any parameters under Windows.
set outside or only inside a section function are marked accordingly. the first thing you can do is to check basic parameters. Use Setup > Agents > Windows, Linux, Solaris, AIX and the menu Agents > Agent rules > ORACLE Databases (Linux, Solaris, AIX to create a rule. which you can monitor your database instances. So first it is This authorization enables the user to fetch at least part of the data, even if can be determined. as always. Access data for a specific database instancein this case for the instance MYINST1. This option is added to sqlnet.ora and sets a timeout for the instance itself. Under unix-type systems, you can not only retrieve locally running instances, These are partly optional, and partly necessary to establish a connection. The plug-in alternatively searches in However, depending on the application scenario, you will quickly need further Use manually created ORACLE password wallet. the newly-created user is named checkmk. screenshots hosts folders inherited organized monitored attributes configured folder level In the configuration file you therefore have For example, if you want to exclude only locks defined took to process. it is undesirable to have certain long-running sections to be included in general functionality of the Checkmk agent. On all supported systems the C:\Program Files (x86)\checkmk\service\plugins\ into the plug-in Important: It is only possible to query own SQL queries under Linux, checkmk for the instance MYINST1: For the plug-in to know where to look for the wallet, it must find two files. plug-in. With the standard login you can use regular or maybe even all instances of a Normally the SID and the file name of the SQL queries are taken over. For monitoring remote databases, You must then specify this program if you want to monitor a remote instance, but sqlplus cannot be found via the environment variables. and special features: You cannotunderstandablyexclude remote instances with SKIP_SIDS, and in return you do not need to include them in ONLY_SIDS. instance at any time without having to interrupt the synchronization with the Logging under Windows works similarly to the connection test itself. them accordingly. login data for all instances, and set a default in the configuration. the first variables for getting monitoring data from their Oracle instances. You can also specify any other with the Agent Bakery, because syntax errors in In case of doubtthat is, as the default behaviorthe instance will be monitored accordingly. The processing is done for each instance in the order given above. However there are a number of additionalmandatoryspecifications: In the example, two remote instances are being configured. Since Solaris and AIX. doit checkmk Linux and Windows. Even with an RAC, it makes sense to combine specified services in a cluster host. Assign the authorization to the user who is authorised to retrieve the data from You can find out more about these mechanisms in the following sections. been changed from MOUNTED to OPEN. already know from DBUSER. and the name of this file (SQLS_SQL). How long the data remains valid is determined by the CACHE_MAXAGE variable, below in this table. Therefore if the variable ONLY_SIDS file paths for the agents are the same or very similar. just have to be unique for each configuration file. If this is present as a host in Checkmk, data from the agent plug-ins configuration file. Since there is a central storage for the data in a RAC, it is sufficient here to long: If the service should have a Long Output, you can specify it here. On the monitored host you need to perform certain actions, and on the Checkmk side it is also necessary that you customize the services and assign them to a cluster hostregardless of whether you use ADG or DG.
These only affect the specified ID and must therefore be unique. As you learned in the previous section, it is not only possible to disable As a rule, the conditions are already fulfilled when an Oracle installation is Windows even requires that you specify them manually. Please note that a setup using the To make the configuration as simple as possible in individual situations, you but also log on to remote ones and retrieve the databases running there. The tnsnames.ora file must then simply be amended as necessary. To be able to monitor the databases only the plug-in is required in addition active sessions, but also many other types of performance data. The assignment of permissions is a bit different as for regular users as you need to specify them for all current container and for all in the future: After you have created a user, the next step is to enable the agent plug-in to the following three options for specifying users: The default if no individual access data has been defined for the database instance. example, a configuration can look like this: A few explanations for the above example: You can define any number of individual access data.
Once you have licensed and activated ADG, you do not need to make any changes to difficult to read method to get to the cause of a problem, and should therefore On the one hand, this So that the necessary user data can also be found, you must The version specification therefore also cannot be omitted, and it determines restrict only certain instances you can slot in the EXCLUDE__{SID}_ there are the following requirements: The Linux AIO access library is installed. They therefore correspond to both variables SYNC_SECTIONS and ASYNC_SECTIONS, as well as their counterpart in the case of an ASM from the section where the data to be fetched is to be found.
In the output the dummy sections have been omitted for readability. Among others, Checkmk can monitor the following values: Apply and transport lag of Oracle Data-Guard. A configuration could then look like this, for example: As you can see in the example, only the instance section is queried for the ASM instances and a minimum set for the asynchronous sections is specified on all regular instances.
The usual directory where the plug-ins are located. Can be set globally or per section. This is usually Only the fourth (last) line Simple integration of own SQL queries. only one, and then described it in more detail directly afterwards. If the instances do not have ADG, the user with which the monitoring data from