hI Mônica
As far as I know, Genesys Cloud doesn't natively provide a ready-made metric for token consumption, APIs, data tables, etc.
What indirectly have is aggregated data in the "usage/query" API.
For granularity (e.g., by minute/second), you usually need your own logging (API gateway, proxy, etc.) or open a support ticket (Genesys Care)..etc.
There are even reported cases of this issue at this link:
https://community.genesys.com/discussion/rate-limit?utm_source=chatgpt.com
I also know that the license consumption API is quite rudimentary, but it has seen improvements, and there were signs that these improvements would be released by the middle of the year so that we would have license consumption data via the API.
In a real-world example from the past (a client here in Brazil), the client used DataDog for monitoring.
In the inbound flows, we made several calls to DataDog(by API), such as API failures/timeouts, client browsing data before the transfer, datatable failures, etc.
With this data, the client created alerts in their monitoring.
They also had A3S appfoundry, and DataDog retrieved data (JSON) to generate alerts based on various metrics, such as statuses not responding for more than X amount of time, clients waiting in the queue for more than X amount of time, etc.
This combination of API-driven metrics, external observability, and error monitoring gave their operations team much better visibility and helped them proactively justify limit increases with historical data, rather than reacting only after a limit had already been reached.
In practice, many organizations end up treating Genesys Cloud like any other SaaS platform: exporting operational signals into their centralized observability stack and building proactive monitoring there.
------------------------------
Kaio Oliveira
GCP - GCQM - GCS - GCA - GCD - GCO - GPE & GPR - GCWM
PS.: I apologize if there are any mistakes in my English; my primary language is Portuguese-Br.
------------------------------