Yandex Cloud
Documentation
PresentationContact UsTry it for free
© 2026 Direct Cursus Technology L.L.C.
Yandex Smart Web Security
  • Getting started
    • All guides
    • Address lists
    • Viewing operations
    • Configuring monitoring
    • Setting up alerts
    • Configuring logs via Smart Web Security
    • Configuring logs via Application Load Balancer
    • Migrating to the new condition format in the API, CLI, and Terraform
    • Overview
    • Security profiles
    • WAF profiles
    • ARL (request limit)
    • Rules
    • Conditions
    • Lists
    • Managing bot traffic
    • Protecting domains
    • Response templates
    • Logging
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  1. Step-by-step guides
  2. Configuring monitoring

Monitoring in Smart Web Security

Written by
Yandex Cloud
Updated at November 11, 2026
View in Markdown

Monitoring allows you to track the rate of requests to a protected resource: allowed, blocked, redirected to a JS challenge, cookie challenge, or SmartCaptcha, and processed by an ARL profile. You can also set up alerts to get notifications when request rate thresholds are exceeded.

Yandex Cloud offers pre-configured dashboards for Smart Web Security monitoring.

You can view the dashboards using one of the following options:

  • On the Smart Web Security page, select Monitoring and a tab:
    • Anti-DDoS: Charts for security profiles and ARL profiles.
    • SolidWall WAF: Charts for your SolidWall WAF profile.
  • To view the dashboard in Monium, click Open in Monium at the top right of the Monitoring section.
  • On the Application Load Balancer page:
    1. Select the load balancer with an associated security profile.
    2. Navigate to Monitoring.
    3. Go to the Smart Web Security tab.

Description of Smart Web Security monitoring dashboardsDescription of Smart Web Security monitoring dashboards

Charts of requests sent for verification use metrics with the service=application-load-balancer label. The metric name is set in the name label. Traffic is selected based on folder (folderId), load balancer (load_balancer), security profile (security_profile), and rule (rule_name). For security profile charts, the HTTP router (http_router) and virtual host (virtual_host) labels are also used; for ARL charts, the ARL profile ID (arl_profile) is used.

The values ​​of the selected time series are summed by the series_sum() function, and the NaN values are replaced with zero using replace_nan(0).

  • Inbound total RPS: Total number of incoming requests per second (RPS) reaching the load balancer with the security profile.

    Metric: load_balancer.requests_count_per_second.

  • Allowed by Security Profile RPS: Number of incoming requests per second the security profile has checked and allowed.

    Metric: load_balancer.smart_web_security.requests_per_second filtered by antirobot_verdict=allow.

  • Denied by Security Profile RPS: Number of incoming requests per second the security profile has checked and blocked.

    Metric: load_balancer.smart_web_security.requests_per_second filtered by antirobot_verdict=deny.

  • Redirected to SmartCaptcha RPS: Number of incoming requests per second routed to SmartCaptcha for additional verification.

    Metric: load_balancer.smart_web_security.requests_per_second filtered by antirobot_verdict=captcha.

  • Redirected to JS challenge RPS: Number of incoming requests per second redirected to a client-side JavaScript challenge.

    Metric: load_balancer.smart_web_security.requests_per_second filtered by antirobot_verdict=js_challenge.

  • Redirected to Cookie challenge RPS: Number of incoming requests per second redirected to a client-side cookie challenge.

    Metric: load_balancer.smart_web_security.requests_per_second filtered by antirobot_verdict=cookie_challenge.

    Note

    When matching against Inbound total RPS, consider the charts of requests that were allowed, blocked, or routed for various types of checks. Not all requests allowed at this stage and labeled with antirobot_verdict=allow will reach the protected node. They may get blocked by the ARL profile limiting the incoming request rate.

  • Allowed by ARL Profile RPS: Number of incoming requests per second not exceeding the ARL profile limit.

    Metric: load_balancer.smart_web_security.arl_requests_per_second filtered by the arl_verdict=allow label.

  • Denied by ARL Profile RPS: Number of incoming requests per second exceeding the ARL profile limit and blocked.

    Metric: load_balancer.smart_web_security.arl_requests_per_second filtered by arl_verdict=deny.

  • Redirected to SmartCaptcha by ARL Profile RPS: Number of incoming requests per second the ARL profile routes to SmartCaptcha for additional verification.

    Metric: load_balancer.smart_web_security.arl_requests_per_second filtered by arl_verdict=captcha.

    Note

    When matching against Allowed by Security Profile RPS, consider the charts of requests that were allowed, blocked, or routed for CAPTCHA within the ARL profile.

You can combine multiple metrics in a single chart and configure your own dashboards in Monitoring.

Useful linksUseful links

  • Yandex Monitoring metric reference
  • Dashboards in Monitoring

Was the article helpful?

Previous
Viewing operations
Next
Setting up alerts
© 2026 Direct Cursus Technology L.L.C.