Ad Widget

Collapse

Web Scenario monitoring : alerts incomplete

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • fab83xxx
    Junior Member
    • Jul 2025
    • 1

    #1

    Web Scenario monitoring : alerts incomplete

    Hi

    I'm monitoring a VR web application with multiple critical user journeys using web scenarios. The platform has several complex workflows that need continuous monitoring.

    I've set up a web scenario with 12 steps covering the complete session flow:
    • Login authentication
    • VR device pairing
    • Biometric sensor initialization
    • Session configuration
    • Real-time data streaming
    • Session completion & data export

    My current trigger configuration:

    last(/Zabbix server/web.test.fail[Critical Web Services])=1


    The trigger only fires when step 1 (login) fails, but completely ignores failures in steps 4-12. This is problematic since VR device pairing or sensor failures are more critical than login issues. When an alert fires, I only get "Patient Session Flow failed" without knowing which specific step broke or why. For a healthcare platform, I need to know immediately if it's a device connectivity issue, API timeout, or sensor malfunction.

    What I need: Triggers that detect failures at ANY step in the scenario. Alert messages showing the failed step name, URL, and error details. Ideally, different severity levels based on which step fails

    Has anyone successfully implemented comprehensive web scenario monitoring for multi-step applications? Are there alternative approaches using dependent items or custom LLD rules?


    Thanks for any guidance!

    Zabbix version: 6.4 LTS Environment: Production healthcare platform
Working...