1. Using Oracle Infrastructure Monitoring
  2. Agent-monitored Entity Types and Cloud Services

D Agent-monitored Entity Types and Cloud Services

The following table lists the JSON files associated with each entity type. For a thorough description of JSON file parameters for each entity type, see Download and Customize Oracle Infrastructure Monitoring JSONs.

Table D-1 Agent-monitored Entity Types

Entity Type JSON Files Entity Internal Name Comments
Linux Host (including Oracle Cloud Compute and Amazon EC2 that can be monitored as Linux Hosts) update_host_sample_1.14_and_on.json omc_host_linux See Enable Host Monitoring for more information about Host Entities.
Solaris Host update_host_sample_1.14_and_on.json omc_host_solaris  
AIX Host update_host_sample_1.14_and_on.json omc_host_aix  
Windows Host update_host_sample_1.14_and_on.json omc_host_windows See Enable Host Monitoring for more information about Host Entities.
MySQL Database omc_mysql_db_sample.json

omc_mysql_creds.json

 omc_mysql_db  
Oracle Database — Single Instance (including Database as a Service that can be monitored as an Oracle Database) omc_oracle_db_sample.json

omc_oracle_db_sample_creds.json

 omc_oracle_db

When a CDB is added, all PDBs contained within the CDB are automatically discovered. An auto-refresh process runs periodically to discover any newly added PDBs to the CDB.

Newly discovered PDBs will appear as new instances of type Oracle Pluggable Database.
Oracle Database — Real Application Clusters (RAC) omc_oracle_dbRAC_sample.json

omc_oracle_dbRAC_sample_creds.json

 omc_oracle_db RAC instances are automatically discovered on a periodic basis once you add an Oracle RAC database. RAC instances are monitored using metrics associated with the Oracle Database.

When a CDB is discovered, all PDBs contained within the CDB are automatically discovered. An auto-refresh process runs periodically to discover any newly added PDBs to the CDB.

Newly discovered PDBs will appear as new instances of type Oracle Pluggable Database.

Oracle  Automation Storage Management (ASM) omc_oracle_asm_sample.json

omc_oracle_asm_sample_creds.json

 omc_oracle_asm You discover RAC ASM targets one-by-one on each node. However, when discovering an ASM target on the first node, all nodes containing ASM instances will also be discovered.
Oracle Database Listener omc_oracle_db_listener_sample.json

omc_oracle_db_listener_creds.json

 omc_oracle_db_listener  
Oracle Database Listener Cluster

omc_oracle_db_listener_cluster_credless_sample.json

omc_oracle_db_listener_cluster_sample.json

omc_oracle_db_listener_cluster_sample_cred.json

 omc_oracle_db_listener_cluster

Cluster Listener discovery adds the following:

  1. Cluster Listener/SCAN Listener ( Entity Type: omc_oracle_db_listener_cluster)

  2. All the Nodes/ SI Listener of Cluster (omc_oracle_db_listener)
Oracle HTTP Server (OHS) omc_oracle_apache_sample.json

omc_oracle_apache_sample_creds_ohs11.json

omc_oracle_apache_sample_creds_ohs12.json

    
Oracle SOA Infrastructure omc_oracle_soainfra_sample_creds.json

omc_oracle_soainfra_sample.json

 omc_oracle_soainfra  
Oracle Service Bus omc_oracle_servicebus_sample.json

omc_oracle_servicebus_sample_creds.json

 omc_oracle_servicebus  
Microsoft SQL Server Database omc_sqlserver_db_sample.json

omc_sqlserver_db_creds.json

 omc_sqlserver_db  
MongoDB Database omc_mongodb.json omc_mongodb_creds.json omc_mongodb  
Tomcat omc_tomcat_secure_sample.json

omc_tomcat_creds_sample.json

 omc_tomcat If a Tomcat entity has been added to APM, it can be automatically discovered and monitored by Oracle Infrastructure Monitoring if the following conditions have been met:

  • Tomcat configuration is credential-less.

  • The Cloud Agent resides on the same machine as Tomcat.

  • The Cloud Agent must be at least version 1.17.

Note:

In order to auto-discover Tomcat Entities for Oracle Infrastructure Monitoring, make sure Tomcat entities are configured to make remote JMX connections.
WebLogic Server (including Java Cloud Service that can be monitored as a WebLogic Server) N/A omc_weblogic_j2eeserver See the comment for WebLogic Domain.
WebLogic Cluster N/A omc_weblogic_cluster See the comment for WebLogic Domain.
WebLogic Domain omc_weblogic_domain_sample.json

omc_weblogic_domain_creds.json

 omc_weblogic_domain When you add a WebLogic Domain, and all of the WebLogic Clusters and WebLogic Servers in the domain are automatically added. There is no need to add servers and clusters separately.

Note:

Only T3 and T3S protocols are supported for RMI communication between WebLogic Server and other Java programs.

When you add a WLS Domain entity using omcli (where the property capability=monitoring), the entity initially will not appear in the Oracle Infrastructure Monitoring UI.

To get the WLS Domain entity to display, navigate to the license UI, select the entity and change the edition on the WLS Domain. This will also change the edition for all members of the domain. Once done, the WLS Domain entity and any members will appear in the Oracle Infrastructure Monitoring UI.

Apache HTTP Server omc_generic_apache_sample.json

omc_oracle_apache_sample.json

 omc_generic_apache  
Docker Engine/Container omc_docker_engine_sample.json (used without the omc_docker_engine_sample_creds.json)

omc_docker_engine_secure_sample.json (used with the omc_docker_engine_sample_creds.json)

omc_docker_engine_sample_creds.json

 omc_docker_engine You add docker containers by adding the Docker Engine that manages the containers. Once a Docker Engine has been added, any managed containers are automatically added. An auto-refresh process runs periodically to discover new containers.
Traffic Director Instance omc_oracle_otd_cluster_sample.json

omc_oracle_otd_cluster_sample_creds.json

 omc_oracle_otd_instance The Oracle Traffic Director JSON files listed here can only be used with OTD 11g. Beginning with OTD 12, Oracle Traffic Director Instance discovery is part of the WLS Domain discovery.
Oracle Traffic Director Cluster omc_oracle_otd_cluster_sample.json

omc_oracle_otd_cluster_sample_creds.json

 omc_oracle_otd_cluster  
Cisco Ethernet (Catalyst) Switch omc_cisco_eth_switch_sample.json

omc_cisco_eth_switch_snmpv1_sample_creds.json

omc_cisco_eth_switch_snmpv3_sample_creds.json

 omc_cisco_eth_switch  
Oracle NoSQL omc_nosql_db_sample.json omc_oracle_nosql_db  
Arista Ethernet Switch omc_arista_eth_switch_sample.json

omc_arista_eth_switch_snmpv2_sample_creds.json

omc_arista_eth_switch_snmpv3_sample_creds.json

 omc_arista_eth_switch  
Cisco Nexus Ethernet Switch omc_cisco_nexus_eth_switch_sample.json

omc_cisco_nexus_eth_switch_snmpv2_sample_creds.json

omc_cisco_nexus_eth_switch_snmpv3_sample_creds.json

 omc_cisco_nexus_eth_switch  
Juniper Ethernet Switch omc_juniper_eth_switch_sample.json

omc_juniper_eth_switch_snmpv2c_sample_creds.json

omc_juniper_eth_switch_snmpv3_sample_creds.json

 omc_juniper_eth_switch  
Xen Virtual Server/ Xen Virtual Platform omc_xen_virtual_platform_sample.json

omc_xen_virtual_platform_with_root_creds.json

omc_xen_virtual_platform_with_sudo_creds.json

omc_xen_virtual_platform_with_ssh_keys.json

omc_xen_virtual_platform_with_sudo_ssh_keys.json

 omc_xen_virtual_platform  
Infiniband Switch omc_oracle_ib_switch_sample.json

omc_oracle_ib_switch_snmpv2c_sample_creds.json

omc_oracle_ib_switch_snmpv3_sample_creds.json

omc_oracle_ib_switch

  
Power Distribution Unit (PDU) omc_oracle_pdu_sample.json

omc_oracle_pdu_sample_snmpv1_creds.json

omc_oracle_pdu_sample_snmpv3_creds.json

 omc_pdu  

Oracle Fabric Manager / Virtual Networking / Xsigo

 omc_oracle_ovn_sample_creds.json

omc_oracle_ovn_sample.json

 omc_oracle_ovn  
Brocade Fibre Channel Switch omc_brocade_fc_switch_sample.json

omc_brocade_fc_switch_snmpv1_sample_creds.json

omc_brocade_fc_switch_snmpv3_sample_creds.json

 omc_brocade_fc_switch  
Oracle HTTP Server (OHS) omc_oracle_apache_sample.json

omc_oracle_apache_sample_creds_ohs11.json

omc_oracle_apache_sample_creds_ohs12.json

 omc_oracle_apache  
SCOM (System Center Operations Manager) omc_microsoft_scom_sample.json

omc_microsoft_scom_sample_creds.json

 omc_microsoft_scom This integration can be used to monitor Windows host servers by retrieving the host performance data from Microsoft SCOM.
SCOM Integration (Windows host)

  1. Deploy a Cloud Agent on the Windows machine.

  2. Copy the following files (available on the SCOM server) required by the Cloud agent: to this location:
    %ProgramFiles%\Microsoft System Center 2012 R2\Operations Manager\Server\SDK Binaries\Microsoft.EnterpriseManagement.Runtime.dll
    %ProgramFiles%\Microsoft System Center 2012 R2\Operations Manager\Server\SDK Binaries\Microsoft.EnterpriseManagement.OperationsManager.dll    
    %ProgramFiles%\Microsoft System Center 2012 R2\Operations Manager\Server\SDK Binaries\Microsoft.EnterpriseManagement.Core.dll

    Note:

    If the Cloud agent is deployed on the same Windows server as SCOM, there is no need to copy these files.
  3. Uncomment the following line in discovery.properties file:
    disable_monitoring_for_entitytype=omc_host_windows
The Windows host has already been added to OMC by the Cloud Agent., meaning this SCOM integration uses the windows host that is already added by the Cloud Agent and then starts populating its metrics. Hence, there is no need to have add duplicate Wndows host entities.

Note:

There is no need to bounce the Cloud Agent.

Once successfully integrated, OMC automatically refreshes every minute to detect new host Windows servers.

Monitoring of the following entities is supported:

  • Windows Hosts

  • SQL Server DB

  • Exchange Server

  • Hyper-V (via Virtual Platform and Virtual Server)

  • Active Directory

  • IIS
Juniper SRX Firewall omc_juniper_srx_sample.json

omc_juniper_srx_snmpv2_sample_creds.json

omc_juniper_srx_snmpv3_sample_creds.json

 omc_juniper_srx  
Fujitsu Computers omc_fujitsu_server_sample.json

omc_fujitsu_server_creds_sample.json

 omc_fujitsu_server  
Intel/SPARC Computers omc_ilom_server.json

omc_ilom_server_creds.json

 omc_ilom_server  
VMware vCenter omc_vmware_vcenter_sample.json

omc_vmware_vcenter_sample_creds.json

 NA vCenter is a composite entity consisting of the following entities:

  • Virtual Management System

  • Datacenter

  • Datastore

  • Resource Pool

  • Virtual cluster

  • Virtual application

  • Virtual Platform

  • Virtual Server
NGINX omc_nginx.json omc_nginx  
Docker Swarm Entity JSONs for Docker Swarm:

Adding Non-Secure Docker Swarm Target

Add_Entity_Docker_Swarm_Non_Secure.json

Adding 1WAY Docker Swarm Target

Add_Entity_Docker_Swarm_1way_SSL.json

Adding 2WAY Docker Swarm Target

Add_Entity_Docker_Swarm_2way_SSL.json

Credential JSONs:

:Docker_Swarm_Secure_Credentials.json

Entity JSONs for Docker Worker Engines:

Adding Non Secure Docker Worker Engine

Add_Entity_Worker_Docker_Engine_Non_Secure.json

Adding 1WAY Docker Worker Engine

Add_Entity_Worker_Docker_Engine_1way_SSL.json

Adding 2WAY Docker Worker Engine

Add_Entity_Worker_Docker_Engine_2way_SSL.json

 omc_docker_swarm

The Docker Engine credential json remains the same for Worker Engines.

For secure mode, apart from the jsons, you need to add the docker truststore certificate(CA ceritificate) in the agent default truststore($EMSTATE/sysman/config/montrust/AgentTrust.jks).

Command:

omcli secure add_trust_cert_to_jks -password welcome -trust_certs_loc <certificate location> -alias dockercertificate 

For example: slce03.cer is the CA certificate.

omcli secure add_trust_cert_to_jks -password welcome -trust_certs_loc /certificate_directory/slce03.cert -alias dockercertificate

 

Fetching Swarm ID:

Do a GET on LEADER_BASE_URL/swarm

For example: GET on http://myserver.mycompany.com:4243/swarm
Apache SOLR

Entity JSONs

omc_solr_instance_credless.json

omc_solr_instance_creds.json

omc_solrcloud_credless.json

omc_solrcloud_creds.json

Credential JSONs

solr_basic_authentication.json

solr_client_authentication.json

solr_client_with_basic_authentication.json

 omc_solr_instance  
Arbor Networks TMS

omc_arbor_tms_sample.json

omc_arbor_tms_snmpv2_sample_creds.json

omc_arbor_tms_snmpv3_sample_creds.json

 omc_arbor_tms  
Arbor Networks CP

omc_arbor_cp_sample.json

omc_arbor_cp_snmpv2_sample_creds.json

omc_arbor_cp_snmpv3_sample_creds.json

 omc_arbor_cp  

Juniper Netscreen

Firewall

omc_juniper_netscreen_sample.json

omc_juniper_netscreen_snmpv2_sample_creds.json

omc_juniper_netscreen_snmpv3_sample_creds.json

 omc_juniper_netscreen  
Juniper MX Router

omc_juniper_mx_sample.json

omc_juniper_mx_snmpv2_sample_creds.json

omc_juniper_mx_snmpv3_sample_creds.json

 omc_juniper_mx  
F5 BIG-IP LTM

omc_f5_bigip_ltm_sample.json

omc_f5_bigip_ltm_snmpv2_sample_creds.json

omc_f5_bigip_ltm_snmpv3_sample_creds.json

 omc_f5_bigip_ltm  
F5 BIG-IP DNS

omc_f5_bigip_dns_sample.json

omc_f5_bigip_dns_snmpv2_sample_creds.json

omc_f5_bigip_dns_snmpv3_sample_creds.json

 omc_f5_bigip_dns  
Hadoop Cluster

No Credentials

hadoop_credless.json

Credentials

hadoop_creds.json

Credential Input File

hadoop_credentials_input.json

omc_oracle_hadoop_cluster

omc_oracle_hadoop_hdfs

omc_oracle_hadoop_yarn

omc_hadoop_datanode

omc_hadoop_namenode

omc_hadoop_nodemanager

omc_hadoop_resourcemanager

When a Hadoop Cluster is added, the following entities of the Hadoop environment are automatically discovered. .

  • Hadoop HDFS

  • Hadoop YARN

  • Hadoop Namenode

  • Hadoop Datanode

  • Hadoop Nodemanager

  • Hadoop Resourcemanager
NetApp FAS

omc_netapp_fas_sample.json

omc_netapp_fas_snmp_sample_creds.json

 omc_netapp_fas  
ZFS Storage Appliance

omc_oracle_zfs_storage_appliance_sample.json

omc_oracle_zfs_storage_appliance_sample_creds.json

 omc_oracle_zfs_storage_appliance  
Kubernetes

Entity JSONs (Without Heapster & Heapter running as cluster service)

omc_kubernetes_cluster_insecure.json

omc_kubernetes_cluster_secure.json

Entity JSONs (With Heapster not running as cluster service)

omc_kubernetes_cluster_insecure(heapster).json

omc_kubernetes_cluster_secure(heapster).json

Credential JSONs

alias_creds.json

keystore_creds.json

token_creds.json

 omc_kubernetes  
ES2 Ethernet Switch

omc_es2_sample.json

omc_es2_snmpv2_sample_creds.json

omc_es2_snmpv3_sample_creds.json

 omc_es2  
Oracle Flash Storage

omc_oracle_flash_storage_sample.json

omc_oracle_flash_storage_creds_sample.json

 omc_oracle_flash_storage  
Cassandra DB

omc_cassandra_db.json

omc_cassandra_db_creds.json

 omc_cassandra_db  
EMC VMAX

omc_emc_vmax_sample.json

omc_emc_vmax_creds_sample.json

 omc_emc_vmax  
EMC VNX omc_emc_vnx_creds_sample.json

omc_emc_vnx_instance_sample.json

 omc_emc_vnx  
L2/L3 Generic Network Node omc_network_node_sample.json

omc_network_node_snmpv2_sample_creds.json

omc_network_node_snmpv3_sample_creds.json

 omc_network_node  
Oracle VM Server for SPARC (LDOM)

omc_sparc_ldoms_sample.json

 omc_sparc_ldoms  
JBoss omc_jboss_domain_sample.json

omc_jboss_domain_sample_creds.json

omc_jboss_domain_secure_sample.json

omc_jboss_domain_secure_sample_creds.json

omc_jboss_standalone_j2eeserver_sample.json

omc_jboss_standalone_j2eeserver_sample_creds.json

omc_jboss_standalone_j2eeserver_secure_sample.json

omc_jboss_standalone_j2eeserver_secure_sample_creds.json

 omc_jboss_domain

omc_jboss_standalone

  
Oracle Coherence omc_oracle_coherence.json

omc_oracle_coherence_cred.json

coherence_credentials.json

 omc_oracle_coherence  
Oracle Clusterware (CRS)

omc_oracle_clusterware_credless_sample.json

omc_oracle_clusterware_sample.json

omc_oracle_clusterware_credential_sample.json

 omc_oracle_clusterware
CRS discovery adds:

  1. CRS ( Entity Type: omc_oracle_clusterware)

  2. All the cluster nodes (omc_cluster_node) of the CRS. The cluster nodes are discovered automatically when CRS is added.

Both local and remote monitoring is supported.

Cluster node and CRS have the following association :

omc_oracle_clusterware contains omc_cluster_node
Oracle GoldenGate omc_oracle_goldengate_sample_arch_classic.json omc_oracle_goldengate_sample_arch_microservice.json omc_oracle_goldengate_sample_creds.json omc_oracle_goldengate  
Oracle VM Manager omc_oracle_vm_manager.json omc_oracle_vm_manager_creds.json omc_oracle_vm_manager omc_oracle_vm_zone omc_oracle_vm_server_pool omc_ovm_virtual_platform omc_ovm_virtual_server Oracle VM Manager is a composite entity consisting of the following entities:

  • Oracle VM Manager

  • Oracle VM Zone

  • Oracle VM Server Pool

  • Oracle VM Virtual Platform

  • Oracle VM Virtual Server

  • The user provides a json file with details to discover Oracle VM Manager, then all the Oracle VM Manager related entities such as Oracle VM Zone, Oracle VM Server Pool , Oracle VM Virtual Platform and Oracle VM Virtual Server are automatically discovered and updated periodically when things change in the Oracle VM Manager deployment.

Oracle JVM omc_jvm_sample.json

omc_jvm_sample_creds

 omc_jvm  

Table D-2 Supported Cloud Services

Cloud Vendor Cloud Service Comments
Oracle Cloud Compute Can be also monitored via Cloud agent for more comprehensive monitoring.
Amazon AWS Elastic Cloud Compute (EC2) Can be monitored via Cloud agent for more comprehensive monitoring.
Amazon AWS Relational Database Service (RDS) For RDS (Oracle) can be monitored via Cloud agent for more comprehensive monitoring.
Amazon AWS Simple Storage Service (S3)  
Amazon AWS Elastic Block Store (EBS)  
Amazon AWS Lambda  
Amazon AWS Redshift  
Amazon AWS Elastic Load Balancer (ELB)  
Amazon AWS

Elastic Load Balancer (ELB) - Application Load Balancer

  
Amazon AWS

Simple Queue Service (SQS)

  
Amazon AWS

Simple Notification Service (SNS)