Technical fit
Will Pulse fit your MarkLogic estate?
Pulse runs on your MarkLogic Server—alongside Admin UI and Query Console—so day-2 insight stays on-estate. Use this page to check topology and time-to-value before a demo.
How Pulse sits next to MarkLogic
- Runs where MarkLogic already is. Deploy Pulse modules and databases on your MarkLogic Server—no separate SaaS stack required for day-2 insight.
- Complements Admin and Query Console. Admin remains the control plane; Query Console remains for interactive development. Pulse adds shared ops views for logs, cluster health, queries, indexes, Optic, and XML. For workstation authoring, seeIDE tools—VS Code and IntelliJ IDEA plugins available now on their marketplaces, with the same MarkLogic developer workflows.
- Your data stays on your estate. Logs, metrics, and operational views live in Pulse databases you control—without a required SaaS collector at runtime.
Typical path to first signal
- Bootstrap Pulse databases, forests, and scheduled tasks (Query Console script).
- Deploy Pulse modules to your MarkLogic modules database.
- Open the Setup wizard as MarkLogic
admin—finish infrastructure, bootstrap logs, wait and finalize, check ingest status, and verify. - Assign Viewer / Operator / Admin (and per-module roles) in Pulse Roles.
Setup shows auto-discovered cluster topology and an integrity seal after deploy so environments stay complete and comparable.
What buyers usually confirm
- MarkLogic version and whether the estate is single-node or multi-host
- Who signs in (digest auth on the Pulse app server)
- Whether External Logs / API-key ingest is in scope
- Whether Indexes Explorer, RBAC, and Audit Log are in scope for your team
FAQ
Common fit questions
Which MarkLogic versions does Pulse support?
Pulse is built for MarkLogic Server estates. Indexes Explorer targets MarkLogic 10+. Confirm your exact version and topology on a demo so we can match your environment.
Does Pulse need a cloud or SaaS runtime?
No. Pulse runs on your MarkLogic Server. Observability metrics and logs stay on your estate—there is no required outbound SaaS dependency at runtime.
Single-node and clusters?
Yes. Setup auto-discovers hosts and shows forest placement for single-node and multi-host installs. Pulse forests typically place on up to three data nodes; other hosts still participate in log ingest and cluster visibility.
Can we ingest application logs too?
Yes. Log Manager External Logs accepts API-key ingest alongside MarkLogic Logs, so app and MarkLogic signals can be triaged in one product.