Sending Data to Oracle Management Cloud

Sending Data to Oracle Management Cloud

Lately I’ve been busy helping customers deploy the new Oracle Management Cloud (OMC) services and discover what it can do for them.   One of the most frequent questions I get when talking with new customers about OMC is how do we collect the data and send it to Oracle’s Cloud?  Using Agents installed on-premises or in the Cloud, we can collect various points of data to be used in the many services that make up Oracle Management Cloud.  The goal of this blog is to introduce you to our points of communication and explain where we get data and how it’s used.

It’s important to note, all communication is outbound from Agents to Oracle Cloud.   There is no inbound communication.  All agent communication is over HTTPS.  If your systems have direct access to the internet, they can communicate directly.  Most enterprise customers will likely configure a proxy or firewall/ACL changes to allow communication over certain servers and ports.

Each tenant will have a unique URL that the agents would access, typically it would look like:

https://<tenant>.itom.management.us2.oraclecloud.com/*

Example:
https://tenant1.itom.management.us2.oraclecloud.com/registry

OMC Architecture

Agents

Cloud Agent

The Cloud Agent is responsible for collecting log, monitoring and performance data to be used in the various services (Log Analytics, IT Analytics and Infrastructure Monitoring).  This agent will sit on the target host, whether on-premises or in a Cloud.  The agent can communicate to OMC directly, via a proxy, or the Gateway (to be discussed below).

APM Agent

When using Application Performance Monitoring (APM), you’ll be using the APM agent which is installed on the server where the application runs. Whether the application is Java, .Net or Node.js, the agent collects and sends performance data about the application to OMC.  This agent can communicate directly, via a proxy, or through the Gateway.  As APM also collects End User Metric data from the application users browser, that data is sent directly to OMC.

Gateway

The Gateway is an optional component and is used to buffer and send all data from Cloud Agents, APM Agents and Data Collectors to the Oracle Cloud.   This way, only one server has to have internet access.  Due to the amount of activity for buffering data, this may require a standalone machine as the CPU utilization can be up to 20% for large environments depending on the number of agents and volume of data being sent.

Data Collector

There is also an optional Data Collector component for users who already have Oracle Enterprise Manager (OEM) configured.  The Data Collector extracts target properties, associations, metrics, incidents, version and additional configuration data about the targets in OEM and shares this with OMC.   The Data Collector talks to OMC through the Gateway.  You can have multiple Data Collectors if you have more than one OEM configured.  This is a great opportunity to consolidate data into one place if your OEM is separated by organization, geography or lifecycle status.

Deployment

Installing these agents is easy.  Customers download a master install kit from  OMC which is used for all installs.  The install kit contains tenant information and a registration key is provided during install to authenticate your agents.

A sample installation command for installing the Cloud Agent communicating through a Gateway:

$ ./AgentInstall.sh AGENT_TYPE=cloud_agent AGENT_BASE_DIR=/u01/app/oracle/omc/cloud_agent GATEWAY_HOST=hostname.server.com GATEWAY_PORT=1840 AGENT_REGISTRATION_KEY=<tenant specific> 

Downloading lama agent software ...
Generating emaas.properties ...
Extracting Agent Software ...
Installing the Agent ...
Registering the Agent ...
Downloading Certificates ...
Configuring the Agent ...
Cleanup temporary files ...

The following configuration scripts need to be executed as the root user
#!/bin/sh
#Root script to run
/u01/oracle/omc/cloud_agent/core/1.12.0/root.sh

Maintaining Agents

Since Oracle Management Cloud is an agile product with monthly releases, the agents may be updated monthly as well.  This does not mean you have to upgrade your agents monthly, but upgrading quarterly will keep your agents in top shape.   When you’re ready to upgrade your agent, you simply go to the Agents administration page and select Upgrade.  This will instruct your agent to download the latest agent and perform an out-of-place upgrade seamlessly.  If the upgrade fails for some reason, your original agent will remain active.   There is also an option to batch upgrade your Agents.

Summary

As you can see, communication to Oracle Management Cloud has a couple of options to meet different needs.  All communication will go over https and can communicate directly to the cloud or through a centralized gateway.  If you’re looking for additional information, you may find these sources helpful: