- About LogicMonitor
- Cloud Monitoring
- Dashboards and Widgets
- Getting Started
- LM Service Insight
- Backup and Recovery Systems
- Cloud Resources
- Networking & Firewalls
- Fortinet FortiWLC Monitoring
- Fortinet FortiWeb Monitoring
- Fortinet FortiSwitch Monitoring
- Fortinet FortiManager Monitoring
- Fortinet FortiMail Monitoring
- Fortinet FortiAuthenticator Monitoring
- Fortinet FortiADC Monitoring
- Ruckus ZoneDirector Monitoring
- Cisco VoIP Monitoring
- Cisco UCS Monitoring
- Cisco Wireless Monitoring
- Brocade Application Delivery Controllers
- Checkpoint Firewalls
- Cisco APIC Monitoring
- Cisco ASA/ASR
- Cisco Device SNMP and NTP Configuration
- Cisco Firepower Chassis Manager Monitoring
- Cisco IP SLA Monitoring
- Citrix NetScalers
- Dell Switch Monitoring
- F5 BIG-IP Monitoring
- Fortinet FortiGate Monitoring
- Infoblox Monitoring
- Interface Status alerting and Bandwidth Utilization
- Juniper SRX
- Kemp LoadMaster Load Balancers
- Meraki Cloud Access Controllers
- NetFlow Monitoring
- Palo Alto Firewalls
- pfSense Firewalls
- Sonicwall Firewalls
- Operating Systems & Virtualization
- VMware Horizon Monitoring
- Citrix XenServer Monitoring
- Citrix XenApp/XenDesktop Monitoring
- ESXi Servers and vCenter/vSphere Monitoring
- Linux Disk Performance
- Linux File Systems reporting more than 100% usage
- Linux Inodes
- Linux Interface Bandwidth Utilization
- Linux NFS Server
- Monitoring a Domain Controller (DC)
- Monitoring Remote Linux Files
- NTP Configuration
- NTP Monitoring
- Nutanix HyperConverged Infrastructure
- SNMP v1/v2 Configuration
- SNMPv3 Configuration
- Solaris Monitoring
- Troubleshooting Perfmon Access
- Troubleshooting SNMP
- Troubleshooting WMI
- VMware vCenter Server Appliance (VCSA) Monitoring
- Windows Cluster Monitoring
- Windows Firewall Issues
- Windows Server 2000
- Windows XP
- Applications & Databases
- Atlassian Statuspage (statuspage.io) Monitoring
- Microsoft Office 365 Monitoring
- OpenMetrics Monitoring
- Zoom Monitoring
- Windows Server Failover Cluster (on SQL Server) Monitoring
- Slack Status Monitoring
- Unomaly Monitoring
- Apache Monitoring
- Cassandra Monitoring
- ConnectWise Monitoring
- Email Service Monitoring
- Java Applications
- Lighttpd Monitoring
- Microsoft Exchange Monitoring
- Microsoft SQL Server Monitoring
- MongoDB Monitoring
- MySQL Monitoring
- Nginx Monitoring
- Oracle Monitoring
- Pick & D3
- Postfix Monitoring
- PostgreSQL Monitoring
- RabbitMQ Monitoring
- Redis Monitoring
- Twilio Monitoring
- Varnish HTTP Accelerator
- Server & Operations Hardware
- Storage Systems
- Cisco HyperFlex Monitoring
- Dell SC Monitoring
- Apache Hadoop Monitoring
- EMC ECS
- EMC Isilon Monitoring
- EMC Unity Monitoring
- EMC VMAX
- EMC VNX/Clariion SAN
- EMC VNXe
- EMC VPLEX
- EMC XtremIO
- HPE 3PAR Storage
- HP MSA / StorageWorks / P2000
- HP P4000/Lefthand SANs
- NetApp E/EF-Series Monitoring
- NetApp Monitoring
- Nimble Storage
- Panzura Cloud Storage
- Quantum Small Tape Libraries
- VMware vSAN Monitoring
- Rest API Developers Guide
- RPC API Developers Guide - Deprecated
- Servicenow CMDB Integration
- Terminology and Syntax
With LogicMonitor’s Oracle package, you can monitor a large number of Oracle operations including blocked session metrics, library cache performance, backup and recovery activities, and resource usage to name just a few.
Oracle databases are monitored using Groovy script with JDBC connections via a user account with read-only permissions to certain statistics tables. If present, LogicMonitor will auto-discover multiple Oracle database instances and, for clients with correctly configured systems (SSH for Linux or WMI for Windows access), will automatically begin monitoring new databases as they are found/created.
LogicMonitor’s Oracle package is verified to be compatible with:
- Oracle version 12c through 19c
The package may work with earlier Oracle versions with the caveat that some datapoints may not be available. Additionally, the user creation instructions provided in the following section may be different for Oracle versions older than 12c.
As Oracle releases newer versions of its database server, LogicMonitor will test and extend coverage as necessary.
From the LogicMonitor repository, import all Oracle LogicModules, which are listed in the LogicModules in Package section of this support article. If these LogicModules are already present, ensure you have the most recent version.
Add Devices Into Monitoring
Add your Oracle resources into monitoring. For more information on adding resources into monitoring, see Adding Devices.
Set Up Oracle User
Note: The instructions provided in this section assume the reader has some knowledge of PL/SQL and has the administrative privileges (e.g. SYSDBA) necessary to set up a new user.
The LogicMonitor Collector must provide the appropriate credentials in order to successfully access the Oracle resource. These credentials must belong to an Oracle user account with access to specific system tables. No user tables need to be exposed and the Oracle user account should be read only.
The process for setting up an Oracle user account for LogicMonitor monitoring purposes varies depending upon whether the Oracle database is a container or non-container database. Follow the instructions provided in the Determining Whether a Database Is a CDB section of the Oracle Database Administrator’s Guide to discover what type of Oracle database it is.
User Setup for Container Database
Run the following script to create an Oracle user on a container database with access to only those specific system tables queried by LogicMonitor. Be sure to update the <password> and <username> placeholders with the credentials you would like to assign to the user account.
alter session set "_ORACLE_SCRIPT"=true; CREATE USER <username> IDENTIFIED BY <password> ; GRANT CREATE SESSION TO <username> CONTAINER=ALL; GRANT SELECT ON V_$SYSSTAT TO <username> CONTAINER=ALL; GRANT SELECT ON v_$session TO <username> CONTAINER=ALL; GRANT SELECT ON v_$process TO <username> CONTAINER=ALL; GRANT SELECT ON v_$sql TO <username> CONTAINER=ALL; GRANT SELECT ON v_$LIBRARYCACHE TO <username> CONTAINER=ALL; GRANT SELECT ON v_$LOCK TO <username> CONTAINER=ALL; GRANT SELECT ON DBA_TABLESPACE_USAGE_METRICS to <username> CONTAINER=ALL; GRANT SELECT ON DBA_TABLESPACES TO <username> CONTAINER = ALL; GRANT SELECT ON v_$SESSION_LONGOPS TO <username> CONTAINER=ALL; GRANT SELECT ON DBA_SEGMENTS TO <username> CONTAINER=ALL; GRANT SELECT ON V_$RESOURCE_LIMIT TO <username> CONTAINER=ALL; GRANT SELECT ON V_$BACKUP_FILES TO <username> CONTAINER=ALL; GRANT SELECT ON V_$RMAN_OUTPUT TO <username> CONTAINER=ALL; GRANT SELECT ON V_$RMAN_BACKUP_JOB_DETAILS TO <username> CONTAINER=ALL; GRANT SELECT ON V_$BACKUP_ASYNC_IO TO <username> CONTAINER=ALL; GRANT SELECT ON v_$SYSMETRIC to <username> CONTAINER=ALL;
For additional resources on setting up Oracle user accounts, see:
- Multitenant : Manage Users and Privileges For Container Databases (CDB) and Pluggable Databases (PDB) in Oracle Database 12c Release 1 (12.1)
- Overview of the Multitenant Architecture
User Setup for Non-Container Database
Run the following script to create an Oracle user on a non-container database with access to only those specific system tables queried by LogicMonitor. Be sure to update the <password> and <username> placeholders with the credentials you would like to assign to the user account.
alter session set "_ORACLE_SCRIPT"=true; CREATE USER <username> IDENTIFIED BY <password>; GRANT CREATE SESSION TO <username> ; GRANT SELECT ON V_$SYSSTAT TO <username> ; GRANT SELECT ON v_$session TO <username> ; GRANT SELECT ON v_$process TO <username> ; GRANT SELECT ON v_$sql TO <username> ; GRANT SELECT ON v_$LIBRARYCACHE TO <username> ; GRANT SELECT ON v_$LOCK TO <username> ; GRANT SELECT ON DBA_TABLESPACE_USAGE_METRICS to <username> ; GRANT SELECT ON DBA_TABLESPACES TO <username> ; GRANT SELECT ON v_$SESSION_LONGOPS TO <username> ; GRANT SELECT ON DBA_SEGMENTS TO <username> ; GRANT SELECT ON V_$RESOURCE_LIMIT TO <username> ; GRANT SELECT ON V_$BACKUP_FILES TO <username> ; GRANT SELECT ON V_$RMAN_OUTPUT TO <username> ; GRANT SELECT ON V_$RMAN_BACKUP_JOB_DETAILS TO <username> ; GRANT SELECT ON V_$BACKUP_ASYNC_IO TO <username> ; GRANT SELECT ON v_$SYSMETRIC to <username>;
Once an Oracle user account has been established for monitoring purposes, the credentials for that account must be set as properties on the Oracle resource(s) within LogicMonitor. As highlighted in the following tables, there are other (optional) properties that can also be set for Oracle resources. For more information on setting properties, see Resource and Instance Properties.
If you have multiple Oracle databases with multiple users and/or port numbers, use the following properties to establish these settings on a per-database-basis. These properties must be set at the resource level to override the jdbc.oracle.user/pass/port properties highlighted in the previous table.
Migration from Legacy Oracle DataSources
In December of 2019, LogicMonitor released a new suite of Oracle DataSources. The new DataSources are automatically multi database, with each database represented as an instance. Because the new DataSources are multi-database aware and, therefore, create new instances, they are not able to remain backwards compatible with the existing suite.
If you are currently monitoring Oracle using the legacy Oracle DataSources, you will not experience any data loss upon importing the newer DataSources in this package. This is because DataSource names have been changed to eliminate module overwriting.
However, you will collect duplicate data and receive duplicate alerts for as long as both sets of DataSources are active. For this reason, we recommend that you disable the legacy Oracle DataSources. Legacy Oracle DataSources are those with names prepended by “Oracle_DB_” as compared to the new naming convention of “Oracle_Database_”.
When a DataSource is disabled, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSources altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSources, see Disabling Monitoring for a DataSource or Instance.
The “Oracle Database Troubleshooter” DataSource exists to capture configuration and permissions issues. If data is not being returned as expected, navigate to this DataSource in the Resources tree and check for the existence of errors (errors display as instances in the Resources tree). Additionally, any errors captured by the troubleshooter DataSource are included in alert details.
LogicModules in Package
LogicMonitor’s package for Oracle consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.
When setting static datapoint thresholds on the various metrics tracked by this package, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.
In this Article: