OneMonVue
The fastest path from business impact to root cause.
One agent. A journey is the ordered path of a real call, stitched from a correlation or a session. The hop that left its baseline is marked before you open the trace.
- 01 User
- 02 CDN / load balancer
- 03 Firewall
- 04 Gateway · Apigee
- 05 Services
- 06 Kafka
- 07 Database
- 08 Stripe Fault
Illustration of the checkout path. In the demo the marked hop is Stripe EU.
Platform
What the product shows.
Six views of the same checkout. The pictures on those pages are screens from the planted demo, not mockups.
3D stack
The checkout opens as layers. The hop outside its baseline is marked before the trace.
Business journeys
Traces that share a correlation or a session become one path. No journey config.
Flows and network
Inbound hops and the outbound hop, on the same picture, with where, what, and why.
Vault
Secrets are sealed in the built-in vault. A normal read returns a mask. External connectors are coming soon.
Agents and deployment
One agent. The install commands are the ones the repository ships.
Integrations
Named systems such as Apigee, Kafka, and ServiceNow. A listed name is not the same as a wired connection.
How it works
Install, then the path appears.
- 01 Install the agent One command for the host you have. The flags are the ones in the install scripts.
- 02 Journeys build themselves Traces that share a correlation or a session become one path. Nothing is drawn first.
- 03 See where, what, and why The trace table names the service, the hop, and the reason. On the planted incident that hop is Stripe EU.
Docs
The tutorials live with the app.
A written path and six short films. This site explains the product and links to those lessons. It does not host the app.