MONITORING
Monitoring and analytics for messaging workloads
See connections, usage, and project health in QPub Cloud. Stream stats and logs over channels for app dashboards, and use APIs where your stack needs programmatic access.
Usage in QPub Cloud
Projects, API keys, and workload visibility from the console your team already uses to ship.
Console-first operations
Create projects, manage keys, and watch connections and message volume without building a custom ops stack on day one.
- Per-project usage and connection signals
- API keys and environment separation
- Same console for Channels and Queues
Illustrative console metrics — see live usage in QPub Cloud for your projects.
Signals in your architecture
Publish metrics and log events to dedicated channels for live dashboards. Pair in-app telemetry with Cloud usage views and REST APIs for billing and automation.
- Stats channels for realtime KPIs
- Log-style events over the same Socket surface
- Cloud APIs and console for platform usage
From project to insight
Four steps to operational visibility.
- 1
Create a project
Sign up in QPub Cloud and provision an API key for your environment.
- 2
Watch Cloud usage
Open the console to monitor connections and message volume for the project.
- 3
Emit app metrics
Publish stats or log events to channels your dashboards subscribe to.
- 4
Plan capacity
Compare usage against plan limits and upgrade before you hit ceilings.
Frequently asked questions
- What can I see in QPub Cloud today?
- The console focuses on project setup, API keys, and usage-oriented signals for your messaging workloads. See Cloud documentation for the current surface.
- How do stats and logs channels work?
- Treat dedicated channel names like any other publish/subscribe surface — backends or clients publish events; dashboards and workers subscribe for live views.
- Where are plan limits documented?
- Pricing and plan docs describe concurrent connections, message volume, and upgrade paths. Your Cloud project reflects usage against your plan.