Connect your servers, message brokers, APIs, databases, and log sources once. Pulse Monitor continuously monitors all of them — across every environment — with polling intervals, alert thresholds, and scheduler jobs all tuned to your load and team.
Operators register every monitored system from Application Configuration. The Server Type you choose determines which collector runs and what the credential fields mean.
Host:Port = AdminServer T3 listen address. Collector prepends t3:// automatically. FTP used for log download when Log Analyzer is enabled.
Host:Port = full base URL e.g. https://tomcat-uat-01:8443. Requires a manager-script role user. FTP for log analysis. Prefer HTTPS in SIT/UAT/PROD.
Host:Port = kube-apiserver URL. Username is repurposed as the namespace (blank = cluster-wide). Password is the ServiceAccount bearer token. Log analysis skipped by policy.
Host:Port = Docker Engine HTTP API e.g. http://docker-host:2375. User/password only needed if a reverse proxy enforces Basic auth. Log analysis skipped by policy.
Pulse Monitor is deployed as a single application package. Environment-specific settings — server connections, alert thresholds, polling intervals, API keys, and credentials — are all managed through configuration files. No code changes between environments.
Connect your servers, message brokers, databases, and APIs once per environment. From that point on, Pulse tracks all of them continuously — automatically adjusting to your load and setup.
All Pulse Monitor configuration, metrics, alerts, deployment records, and log analysis data lives in your existing Oracle schema. We provide the database scripts — a DBA can have the schema ready in minutes.
Pulse Monitor uses your existing Oracle DB — no separate database purchase or additional infrastructure.
We provide schema creation and seed data scripts. A DBA runs them once — Pulse handles the rest automatically.
All Pulse data is stored behind your firewall in your Oracle instance — nothing leaves your infrastructure.
HSTS, CSP, browser security headers, and TLS-only traffic. CIDR-allowlisted forwarded header trust so X-Forwarded-Proto/For cannot be spoofed by untrusted proxies. Controlled per environment via pulse.security.* flags.
Flow token issued at POST /flow/token. PageFlowFilter enforces token for all authenticated GET navigation and AJAX patterns.
Path-to-menu RBAC mapping. Users see only navigation entries they are authorised to access. Menu search respects the same allowedMenus set.
Synchronizer token validation on all mutating requests. Client-side JS injects X-CSRF-Token, X-Pulse-Flow-Token, and X-Requested-With automatically. GET /logout renders a confirm page that POSTs back with the CSRF token in SIT/UAT/PROD, blocking drive-by logout attacks.
Bounded LRU map with TTL eviction protects all endpoints. A separate stricter cap applies to POST /login to slow credential stuffing. Per-IP key is derived only after CIDR-trusted forwarded headers, so it cannot be spoofed.
Get in touch and we'll walk you through the setup for your environment.