ebswatch

Know before the users call.

Read-only monitoring for Oracle E-Business Suite. Failed concurrent requests, slow jobs, sleeping managers and full tablespaces — sent to Slack, Teams or email in seconds.

Most EBS teams find out from users.

A request failed at 2 AM, Journal Import is crawling, or APPS_TS_TX_DATA hit 100% — and nobody knew until month-end close stalled.

How it works

Nothing connects inbound. The agent only reaches out to send alerts.

  1. Step 1

    Install a small agent

    Runs inside your network, next to (or near) the database. No inbound connections, no VPN into your environment.

  2. Step 2

    Give it a read-only DB user

    The agent queries EBS's own tables and views. It cannot write, and it never sees the APPS password.

  3. Step 3

    Get alerts in your team chat

    Failures, slow jobs and full tablespaces post to Slack, Teams or email — with enough detail to act.

What it checks

Straight from EBS's own tables and views — nothing guessed, nothing scraped from screens.

Failed & warning requests

Concurrent requests that errored or completed with a warning.

FND_CONCURRENT_REQUESTS

Long-running vs. usual runtime

Compares each program's current run against its own historical baseline.

FND_CONCURRENT_REQUESTS

Managers down or short

Concurrent manager queues that are stopped or running fewer processes than defined.

FND_CONCURRENT_QUEUES

Tablespace usage

Datafile and tablespace growth, so you add space before it hits 100%.

DBA_TABLESPACE_USAGE_METRICS

Blocking sessions

Sessions holding locks that are blocking other sessions.

V$SESSION

Workflow mailer & deferred queue

Notification mailer status and a growing deferred workflow queue.

WF_DEFERRED

An alert you can act on

Not just "something broke." A likely cause, the request ID, and one click to open, acknowledge or mute.

#erp-alertsPROD

EBS Watch

Autoinvoice Import failed

Request
48213906
Error
ORA-01653: unable to extend table AR.RA_CUSTOMER_TRX_LINES_ALL

Likely cause: APPS_TS_TX_DATA is 91% full. Add a datafile, then resubmit.

Security

Built for teams that can't let monitoring become the next audit finding.

Read-only DB user

The agent connects with a database user that has SELECT only. It cannot modify EBS data or configuration.

Outbound-only agent

The agent opens connections out to EBS Watch and your chat tool. Nothing is exposed for inbound access.

Open-source agent code

The agent that runs inside your network is open source, so your team can read exactly what it queries and sends.

No business data leaves your network

Only alert metadata — program name, status, request ID, error code — is sent out. Never row-level business data.

Pricing

Simple, per-instance pricing. No per-seat charges.

Early access

[PRICE]/ instance / month

Free during the pilot.

Join waitlist

Frequently asked

Which EBS versions are supported?

R12.1 and R12.2 [CONFIRM].

Do you need the APPS password?

No. The agent connects with a dedicated read-only database user — it never sees or needs the APPS password.

Cloud or on-prem?

Either. The agent runs inside your network next to the database, whether that's on-prem, OCI, or another cloud VPC. It only makes outbound connections, so nothing needs to be exposed.

Is EBS Watch affiliated with Oracle?

No. EBS Watch is an independent, third-party monitoring tool and is not affiliated with, sponsored by, or endorsed by Oracle.

Join the waitlist

We're onboarding a small group of EBS teams for a free pilot. Tell us about your environment and we'll reach out.