Frequently asked questions

undefined

FAQ list

How is this different from Datadog or Control-M?

Those tools monitor infrastructure — they tell you a job failed and show you metrics.

Orping is built specifically to read Oracle’s ESS errors, logs, and output files, and email the explanation in the language your team works in. Notifications are email only.

Many customers run both: an observability tool for infrastructure, and Orping for translation and team visibility.

Do I still need someone checking the ESS console?

No. That’s the point. Orping polls ESS continuously so no one has to keep a tab open or wait for an error email that only goes to one inbox.

What exactly does Orping read to build the explanation?

The job’s error output, its execution log, and any output/log file the ESS job itself produced — the same information you’d currently have to open the Fusion console to find manually.

What is Orping.io?

Orping emails Oracle Fusion ESS notifications. Oracle sends the notice in English and a code. Orping emails the alert, a clear explanation, and the log in your language. Notifications are email only.

What is Orping ESS Notifier?

Orping watches your Fusion ESS scheduled processes and emails you when a job fails or misses its schedule — with the failure explained in your language. Notifications are email only.

Does Orping fix ESS jobs or data?

No. Orping only emails the notification. You fix the job in Oracle Fusion.

How do I monitor Oracle ESS jobs in Fusion Cloud?

An admin connects one Fusion user with the ESS Monitor role. On the central dashboard they choose the jobs and who is notified. Each person gets the alert, explanation, and log by email, in their own language.

Which Oracle Fusion modules does ESS monitoring cover?

All Fusion modules that run ESS scheduled processes — including Financials (GL, AP, AR, close), Supply Chain (inventory, costing, orders), HCM (payroll, benefits), Projects, and any custom jobs your team runs in Fusion.

Does Orping monitor OIC or other integration platforms?

No. Orping focuses exclusively on Oracle Fusion ESS scheduled processes. We do not monitor Oracle Integration Cloud (OIC) or third-party integration runtimes.

Can we watch the same ESS job with different parameters?

Yes. Critical Fusion jobs often run with different ledgers, periods, business units, or submission parameters. Add each combination you care about; Orping polls them separately and emails you when that specific run fails or is late.

Does Orping work for period close and month-end jobs?

Yes. Add any ESS job involved in period close, quarter-end, or financial close — including GL, AP, AR, FA, SCM costing, and custom processes. The email arrives instead of discovering failures in the morning.

Is this only for Oracle Fusion Cloud?

Orping.io is designed for Oracle Fusion Cloud (SaaS) ESS and scheduled processes accessed via the standard REST API. On-prem EBS batch monitoring is on our roadmap — join the waitlist to influence priority.

Do I need agents or firewall changes?

No OCI agent and no desktop install. Orping uses outbound HTTPS from our servers to your Fusion tenant. If your environment restricts API access by IP, add Orping's egress IP to your OCI allow list (we provide it at setup). Rarely, a corporate firewall may need to allow outbound HTTPS to your fa-*.oraclecloud.com hostname.

What if our Oracle tenant restricts access by IP?

Whitelist Orping's egress IP in your OCI IP access policy (or equivalent Fusion restriction). No agent is required — email hello@orping.io during setup for the current IP. If connection still fails, check that outbound HTTPS to your Fusion hostname is allowed through your corporate firewall.

How many ESS jobs can we monitor at once?

An admin selects the jobs on the central dashboard.

One ESS Monitor user connects the instance, so Oracle still limits which jobs that role can see.

What does each person receive?

The alert, a clear explanation, and the log, in their own language, by email, for the jobs an admin assigned to them.

How does billing work?

Team is $249 per month per Fusion instance, for up to 20 people. Enterprise adds SSO setup, OAuth 2.0, custom terms, and additional instances.

Taxes may apply at checkout. Paid purchases are sold by Dodo Payments as Merchant of Record.

Who controls what a user can see?

Oracle limits the ESS Monitor user to the jobs that role can see. An admin then chooses which of those jobs are watched and who is emailed.

Is there a free trial?

Book a demo to see it.

Team is $249 per month per Fusion instance, for up to 20 people.

Which languages can Orping explain a failure in?

Oracle sends the ESS notice in default English and a cryptic code. Orping explains that same failure simply, in your language.

The languages on the homepage are English, Spanish, Portuguese, Italian, French, and German, plus Japanese, Korean, Chinese, Indonesian, Thai, and Arabic.

Who is Orping for?

Fusion teams who run ESS jobs and want the alert, explanation, and log in their language — Finance, SCM, HCM, and ERP admins.

What happens when an Oracle ESS job fails?

Orping emails the job name, status, and a simple explanation in your language. Notifications are email only. Oracle’s own notice stays in English and a cryptic code.

Which integrations does Orping support?

Oracle Fusion. One user with the ESS Monitor role connects the instance. An admin chooses the jobs and who is notified.

Each person receives the alert, the explanation, and the log, in their language.

Still have questions?

Book a live demo — we onboard Oracle Fusion teams personally and walk through your ESS jobs.

Book demo →