The admin UI handles the voice versus chat split fine, so the backend clearly supports it. We’ve tested nested objects and stripped the aggregation flag when querying for queue observations, but it’s still dumping everything into one combined total. Passed {"groupBy": ["queueId", "mediaType"], "interval": "hourly"} straight from the docs. Need the exact JSON structure to force that dual breakdown.
3 Likes