O&M Solution: Oracle Fusion Applications and OCI Observability Services

Introduction

Fusion Applications Observability Overview

In a typical Fusion environment, it is essential to ensure that end user performance, availability, and reliability are taken care to maintain smooth business operations. Through OCI Application Performance Monitoring (APM), Fusion Apps can gain an in-depth understanding of user experience, API performance, integrations, and business processes.

While Fusion Apps users rely on web-based UIs and Application Performance Monitoring helps to:

Track API response times, failures, and latency.
Monitor third-party & internal API integrations.
Track business transactions for delays and failures.
Identify bottlenecks in approval flows and order processing.
Use real-time alerts for early anomaly detection.
Track transactions across Fusion SaaS, OCI, and on-prem systems by taking advantage of distributed tracing.
Detects suspicious API activity and unauthorized access.
Track user sessions, role changes, and security events.

By utilizing APM Real User Monitoring, customers not only gain visibility of their Fusion Apps UI performance metrics, but they can also narrow down the area of the performance issue when troubleshooting with Oracle Support. At the same time, Logging Analytics, another Observability and Management service, can be used in Audit monitoring of the Fusion Apps.

For enterprises, Oracle Fusion SaaS applications are mission critical. The ability to monitor, analyze, and troubleshoot application behavior in real-time is vital for ensuring performance, reliability, and security. Since Fusion SaaS is fully managed by Oracle, direct access to system logs and infrastructure metrics is limited, making Observability and Management even more important in order to:

Ensure business continuity by proactively detecting and resolving issues.
Improve performance by monitoring API response times, UI, and integration.
Enhance security and compliance by tracking user activity, audit logs, and unauthorized actions.
Optimize integrations by monitoring Oracle Integration Cloud and third-party connections.

Oracle Fusion Cloud customers want to have observability and monitoring capabilities in order to have insights and be able to rule out performance issues caused by network, firewall, or even the issues from the browser version along with the auditing capability and monitoring the user activity for all the components of the Fusion Cloud. To monitor these, we can use Logging Analytics and Application Performance Monitoring services of the Observability and Management platform.

OCI Logging Analytics

OCI Logging Analytics (LA) provides powerful exploration and analysis capabilities, enabling users to efficiently monitor and troubleshoot logs. It ingests, indexes, and analyzes logs from various components, helping users to:

Detect patterns and anomalies in log data.
Correlate logs across multiple services for faster troubleshooting.
Perform advanced searches and visualizations using a rich query language.
Set up alerts and automated responses based on log insights.

With Logging Analytics service, we can enable strict access controls and regular audits which enhances IT security posture. For the list of available Oracle-defined Sources for Fusion Applications, see Oracle-defined Sources.

OCI Application Performance Monitoring

APM Real User Monitoring provides an understanding of the real user experience by doing the following:

Record user interaction with websites and sends browser spans and Real User Monitoring metrics to Application Performance Monitoring.
Provide an insight into the experience of the real user directly from the browser.
Identify performance degradation by closely watching various aspects of an application such as page loads, page performance/application performance index (Apdex), script errors, and AJAX calls.

Benefits of Observability for Fusion Applications

Detect issues before they impact users.
Get real-time alerts on performance bottlenecks, integration failures, or data load delays.
Predict outages or anomalies.
Meet compliance standards with audit logging and traceability.
Optimize usage of OCI infrastructure behind Fusion Apps.

Implementation Steps

Task 1: Configure Logging Analytics

Prerequisites

Understand Fusion Apps Audit Logs APIs. Refer to the Fusion Applications REST API documentation for details on how to retrieve audit trail data. The API Documentation covers functionality and usage details.
Ensure that Audit Trail API access is enabled and the required roles/privileges are assigned.
You must have the Endpoints values identified for the properties: login_url and pod_url from the Fusion Applications instance.

Enable Logging Analytics

Create an entity and confirm the entity has the following properties:
- login_url: The base URL of your Fusion Applications instance
- pod_url: The base URL of your Fusion Applications instance

Add Credentials on the host where Management Agent is installed. Upsert HTTPSBasicAuthCreds type credentials with the correct username and password.


{
    "source": "lacollector.la_rest_api",
    "name": "FA-CREDS",
    "type": "HTTPSBasicAuthCreds",
    "description": "These are HTTPS (BasicAuth) credentials.",
    "properties": [
        {
            "name": "HTTPSUserName",
            "value": "*******"
        },
        {
            "name": "HTTPSPassword",
            "value": "*******”
        }
    ]
}

Restart the Management Agent after credential upsert.
Configure out-of-the-box sources, and associate the source with the entity to schedule data collection. This uses Management Agent to periodically invoke the Fusion Audit APIs and to push data to Logging Analytics.
Description of the illustration create_source.png
Review and validate on Log Explorer.
Verify that the logs are being collected and analyzed properly in OCI Logging Analytics.
Description of the illustration log_explorer.png
To set up custom sources for other Fusion Apps products that are not part of Oracle defined sources, follow the steps here. Once all the logs are collected, you can use this information for audit analysis and create an overview dashboard for high-level monitoring.

Description of the illustration overview_dashboard.png
The serviceName and WebApplication can be changed to any (non-empty) desired value. Once done, save your changes.

Task 2: Deploy the Application Performance Monitoring Browser Agent

Deploy the APM browser agent by editing the global page template. This will ensure the browser agent monitors all pages.

If an APM domain doesn't exist in the OCI tenant, you need to create it before proceeding. For instructions, see Create an APM Domain.

Follow these steps to add the required JavaScript snippet:

Create a sandbox and select the Page Template Composer tool.

Description of the illustration create_sandbox.png
Go to Settings and Actions, and select Edit Global Page Template.

Description of the illustration edit_global_page.png
Make sure the top left logo title in the black ribbon is selected (marked in blue).

Description of the illustration oracle_logo.png
From the Add Content menu, select HTML Markup.
Description of the illustration html_markup.png
Open the Expression as shown in the below screenshots:

Description of the illustration expression.png

Description of the illustration expression_builder.png

Description of the illustration expression_builder_code.png
Paste the below script in the expression builder:


						
<script type="text/javascript" crossorigin="anonymous" src="https://static.oracle.com/cdn/apm/oci/1.1/1.1-1xx/1.1-107/apmrum.fus.base.combi.min.js"</script>
<script type="text/javascript">
	window.apmrum = (window.apmrum || {});
	window.apmrum.serviceName="FA-HCM";
	window.apmrum.webApplication="HCM";
	window.apmrum.ociDataUploadEndpoint="<APM_data_upload_URL>"; 
	window.apmrum.OracleAPMPublicDataKey="<APM_public_data_key>"; 
	window.apmrum.traceSupportingEndpoints = window.apmrum.traceSupportingEndpoints || [{headers: [], urlPattern: '.*'}]; 
	window.apmrum.trackPlainUserId=true;
	window.apmrum.trackScreenText='true';
	
	document.addEventListener('click', function() {
	window.apmrum.udfAttributes = [
		{ name: 'pageName', value: () => getPageName() }
	];
	}, false);

	function getPageName(){
		try {
			let titleElmList = document.getElementsByTagName('H1');
			if(titleElmList && titleElmList.length > 0){
				let txt = titleElmList[0].textContent;
				return txt;
			}    
		} catch (e) { 
			//do nothing
		}
	}
</script>

Replace the <APM_data_upload_URL> and <APM_public_data_key> with the relevant APM domain parameters. For instructions, see Obtain Data Upload Endpoint and Data Keys in Application Performance Monitoring.
The serviceName and WebApplication can be changed to any (non-empty) desired value.
Next, save your changes.
Description of the illustration expression_builder_save.png

Task 3: Verify Application Performance Monitoring Browser Agent Deployment

To generate some monitoring data, use the application you are setting up the monitoring for.
Go to the APM Trace explorer page to see the data loaded. For example, see APM screenshots below.
The user-name dimension is collected and hashed by default. If you want to have the user name in plain text, add the following to the javaScript:
window.apmrum.trackPlainUserId=true
If needed, verify that the APM data upload url (window.apmrum.ociDataUploadEndpoint) is reachable by doing the following:
1. Go to your application and use the Developer Tools in your browser to go to the Developer console. In most browsers, you can start the Developer Console by pressing the F12 key.
2. Select the Network tab and filter the URL list by observations/public-span, if required.
3. The Collector URL should be displayed with the 200 or 204 HTTP response code. If you do not see a 200 or 204 HTTP response code, then the browser is not able to access the Collector URL.

Description of trace_explorer.png follows

Description of the illustration trace_explorer.png

Description of real_user_mon_overview follows

Description of the illustration real_user_mon_overview.png

Use Cases

Log Correlation Across Tiers
Business Process Observability
Application Performance Troubleshooting
Audit and Compliance Tracking

Next Steps

Observability & Management for Fusion Apps is very critical for an organization to ensure that users have a smooth and efficient experience by identifying and addressing performance issues before they impact end-users. To get the maximum value of Fusion Apps, setup Logging Analytics and Application Performance Monitoring today. Access Logging Analytics and APM through the Observability and Management menu in the Oracle Cloud Infrastructure Console. The service is accessible through the Console, CLI, and REST API. These services are available in all OCI commercial regions. For more details and availability in US and other government regions, please check the OCI service availability page. Not yet a customer? Sign up for an Oracle Cloud Infrastructure free trial account!

Leverage OCI’s Observability & Monitoring ecosystem
Set up alerts for metrics that are emitted by the various O&M services.
Create custom dashboards with trace, log, and metric data.
Enable Weekly News Reports in Ops Insights

Acknowledgements

Primary Author: Jayaprakash Subramanian
Contributors: Avi Huber, Kumar Varun, Shivam Shishodia, Shaickmohamed Sirajudeen, Zubair Ansari

More Learning Resources

Explore other labs on docs.oracle.com/learn, take an OCI Observability Professional Course from Oracle University, or access more free learning content on the Oracle Learning YouTube channel. Additionally, visit education.oracle.com/learning-explorer to become an Oracle Learning Explorer.

For product documentation, visit Oracle Help Center.

Title and Copyright Information

O&M Solution: Comprehensive Monitoring of Oracle Fusion Applications

G33041-01

May 2025