Monitor a webhook's performance

From Genesys Documentation
Jump to: navigation, search

Learn how to monitor a webhook's performance

Prerequisites

Monitor a webhook's performance

Use the Action Map Performance to monitor your webhook performance. When you create an action map that uses a webhook, the metric names have the following, specific meanings.

Metric Description
Web Actions Qualified Number of visitors who matched a segment, activity, or outcome score that triggered the action map.
Web Actions Offered Number of times the webhook made a request to the Genesys Cloud integration.
Web Actions Accepted Number of times the webhook request connected with the third-party product's endpoint.
Web Actions Started Not applicable.
Web Actions Engaged Number of times the webhook and Genesys Cloud integration connected successfully with the third-party product.
Web Actions Rejected Number of times Genesys Cloud rejected the webhook's request because the webhook's request was wrong. The rejection can occur in the following scenarios:
  • Action map is not providing enough data to the webhook.
  • Action map is firing intensively and exceeding the Genesys Cloud rate limits (more than 15 requests/second). Requests aren't retried once the throttling threshold is exceeded.
Web Actions Errored Number of times the web action request resulted in an error.
Web Actions Timed out Number of times the web action request timed out.