A security-first breakdown of the proxy model, the polling mechanism, and how 11 live status cards stay current in your browser — without WebSockets, without inbound ports, and without touching your Oracle binaries.
Process and port state at the OS level. No Oracle credentials required for these — runs as the oracle OS user.
SQL against EBS schema views. Read-only. SELECT_CATALOG_ROLE only. No DML, no DDL, no locks.
All results from both probe categories are bundled into a single JSON payload and pushed outbound. One HTTPS POST per cycle. No persistent connection kept open.
Oracle EBS has no event stream for the 11 status surfaces we monitor — Concurrent Manager state, Workflow Mailer health, OPMN/WLS process counts, port liveness. These are operational metrics you can only observe by querying them. Polling is the only mechanism that works across every EBS version and configuration.
Fast enough to catch a CM stall or Mailer flameout within one alerting window. Light enough to be invisible to the database — every query uses SELECT_CATALOG_ROLE, no DML, no locks. At 30s cadence, TuneVault occupies <0.01% of typical EBS database I/O.
~200ms total CPU time per poll cycle on the customer host. ~2 KB JSON outbound per cycle. The proxy has no memory growth, no open socket held between polls, and no background threads. It runs, pushes, and exits. Zero persistent footprint between cycles.
The proxy is a single Python script provided directly to you. You install it. You review it. You can kill it any time with no impact on your Oracle instance. It is not a daemon with persistent state — it's a cron job that runs a script.
The Python proxy on your Oracle host POSTs a JSON bundle: OS process state, port map, DB metrics. API stores latest payload per connection_id. Validates API key, logs receipt timestamp.
When you open the Live Monitor panel, your browser GETs a streaming endpoint. TuneVault keeps this connection open with a Content-Type: text/event-stream response. Standard HTTP — works through corporate proxies and load balancers, unlike WebSockets.
When a new proxy payload lands, the API emits an event: update down every open SSE connection subscribed to that connection_id. Multiple browser tabs get the update simultaneously.
The dashboard parses the incoming JSON and updates each of the 11 status cards: Concurrent Manager (running / max), Workflow Mailer state, WLS AdminServer, OACore ports, Forms ports, OPMN, OPP, Apache/OHS, DB health signal, uptime, and last-seen timestamp. No full page reload required.
SELECT_CATALOG_ROLE only. No DDL (CREATE/ALTER/DROP). No DML (INSERT/UPDATE/DELETE). No data is exfiltrated — only aggregated metrics and counts. Full grant list at tunevault.app/trust.
The proxy is a standalone Python script that runs as the Oracle OS user. It does not modify, patch, inject into, or hook Oracle executables. It has no persistent daemon, no shared memory interface, and no kernel module.
Oracle credentials stored in TuneVault's database are encrypted with AES-256-GCM before write. The proxy API key is also encrypted at rest. Keys are never logged or transmitted in plaintext.
The proxy initiates all connections. TuneVault never connects inbound to your network. No firewall rules to open. No inbound ports required on the Oracle host. The proxy's only outbound destination is tunevault.app over port 443.
The Python proxy script is provided directly to you at installation. Your security team can review it line by line before it runs. No compiled binary, no obfuscation. What you see is what runs.
Stopping the proxy is pkill -f oracle-proxy.py or removing the cron entry. The Oracle instance is unaffected. TuneVault's dashboard shows "proxy offline" within one polling interval.
See an anonymized report from a representative Oracle EBS deployment. No sign-up required. Full setup guide walks through proxy installation in under 5 minutes.