Complete Visibility Into Your Notifications
When you send notifications across multiple channels -- Telegram, Email, Slack, Discord, WhatsApp, and SMS -- you need a single place to see what is happening. The One-Ping dashboard gives you a unified view of every notification sent through the API, showing you delivery statuses, performance metrics, and error details in real time.
No more jumping between Telegram bot analytics, email delivery reports, and Slack workspace logs. One-Ping consolidates everything into a clean, developer-friendly interface that answers the questions you actually care about: Did my notification get delivered? How fast? And if it failed, why?
Available on all plans. The dashboard is included with every One-Ping account, including the free tier. Pro and Business plans unlock advanced analytics and longer log retention.
Dashboard Overview
When you log in to your One-Ping dashboard, the overview screen gives you an immediate snapshot of your notification activity. At a glance, you can see total messages sent, delivery success rate, active channels, and any recent failures that need your attention.
The overview is designed to surface problems quickly. If your Telegram delivery rate drops suddenly or your email bounce rate spikes, you will see it immediately on the main screen. Color-coded status indicators make it easy to distinguish between healthy channels and those that need attention.
Dashboard Overview: The main screen shows four key metric cards at the top -- Total Messages Sent, Delivery Success Rate, Active Channels, and Failed Deliveries. Below that, a line chart displays your sending volume over the last 7, 14, or 30 days, broken down by channel. A live activity feed on the right shows your most recent notifications with their delivery status.
Key Metrics Tracked
The One-Ping dashboard tracks a comprehensive set of metrics to help you understand your notification performance and optimize your delivery strategy.
Delivery Rate
Percentage of notifications successfully delivered across all channels. Broken down per channel so you can identify which ones perform best for your use case.
Response Time
Average time from API call to confirmed delivery for each channel. Track latency trends over time to ensure your notifications arrive when they should.
Channel Breakdown
See exactly how many messages go through each channel -- Telegram, Email, Slack, Discord, WhatsApp, SMS -- with percentage distribution and volume trends.
Error Rate
Track failure rates per channel with detailed error categorization. Identify whether failures are due to invalid recipients, rate limits, or channel outages.
Retry Success Rate
When the automatic retry system kicks in, see how often retries succeed and how many attempts it typically takes to deliver.
Usage Quota
Track your monthly message usage against your plan limits. Get visual warnings as you approach your quota so you can upgrade before hitting the cap.
Real-Time Delivery Tracking
Every notification sent through the One-Ping API appears in your delivery log within seconds. Each log entry shows the notification ID, timestamp, recipient, channels used, delivery status per channel, and response time. You can click on any entry to see the full request and response details, including the exact JSON payload sent and any error messages returned by the downstream channel.
Delivery statuses are updated in real time as channels process your notifications. A notification might show "sent" for Telegram immediately while the email channel shows "queued" as it waits for SMTP confirmation. When delivery is confirmed (or fails), the status updates automatically without needing to refresh the page.
Delivery Log View: A sortable table displays each notification with columns for ID, Timestamp, Recipient, Channels, Status (with color-coded badges: green for delivered, yellow for queued, red for failed), and Response Time. Clicking a row expands it to show the full JSON request body, per-channel response details, and any retry attempts.
Channel Analytics
The channel analytics section provides a deep dive into how each notification channel performs for your account. This is especially valuable when you are deciding which channels to prioritize for different types of notifications or use cases.
For each connected channel, you get dedicated analytics including message volume over time, average delivery latency, success and failure rates, and the most common error types. If you notice that your Slack notifications have higher latency than Telegram, you can adjust your channel priority accordingly.
Per-Channel Metrics
| Metric | Description | Available On |
|---|---|---|
| Volume | Total messages sent per channel over a selected time period | All plans |
| Delivery Latency | Average, median, and P95 delivery time per channel | Pro, Business |
| Success Rate | Percentage of messages successfully delivered per channel | All plans |
| Error Breakdown | Categorized failure reasons (invalid recipient, rate limit, timeout) | Pro, Business |
| Retry Metrics | Number of retries triggered and their success rate per channel | Pro, Business |
| Hourly Heatmap | Message volume by hour and day of week to identify peak usage patterns | Business |
Error Logs and Debugging
When a notification fails, you need to know exactly what went wrong. The One-Ping error log provides detailed debugging information for every failed delivery attempt, so you can quickly diagnose and fix issues.
Each error log entry includes the original request payload, the HTTP status code returned by the downstream channel, the error message, and a suggested fix. For common errors like invalid bot tokens or expired webhook URLs, One-Ping provides actionable suggestions directly in the log, so you do not have to dig through channel-specific documentation.
Error Categorization
Errors are grouped by type: authentication failures, invalid recipients, rate limits, channel outages, and timeout errors. Filter by category to focus on what matters.
Request Replay
Failed notifications can be resent directly from the error log with one click. Fix the underlying issue and replay the exact same payload without writing any code.
Error Trends
Spot recurring issues with error trend charts. If a specific channel starts failing more often, you will see the pattern before it becomes a major problem.
Alert Notifications
Configure alerts to notify you when error rates exceed a threshold. Get notified via your own One-Ping channels when something breaks.
Log Filtering, Search, and Export
With high notification volumes, finding a specific message in your logs needs to be fast. The One-Ping dashboard provides powerful filtering and search capabilities to help you locate any notification instantly.
Filter Options
- By channel: Show only Telegram, Email, Slack, Discord, WhatsApp, or SMS notifications
- By status: Filter by delivered, queued, failed, or retrying
- By date range: Select custom date ranges or use presets (last hour, 24 hours, 7 days, 30 days)
- By recipient: Search for all notifications sent to a specific email, phone number, or channel ID
- By notification ID: Look up a specific notification using its unique message ID
- By metadata: Search by custom metadata keys and values you attached to notifications via the API
Export Capabilities
Need your notification data outside the dashboard? One-Ping supports exporting your logs and analytics in multiple formats for reporting, compliance, or further analysis.
- CSV export: Download filtered log data as CSV for spreadsheet analysis
- JSON export: Get raw log data in JSON format for programmatic processing
- Scheduled reports: Set up weekly or monthly email reports with your key metrics (Business plan)
- API access: Query your logs programmatically via the dashboard API endpoint
Getting Started with the Dashboard
Create your account
Sign up at app.one-ping.com/register. The dashboard is available immediately after registration, even on the free plan.
Send notifications via the API
Use the REST API to send your first notification. It will appear in your delivery log within seconds, complete with status tracking and latency data.
Monitor and optimize
Use the analytics to identify your best-performing channels, troubleshoot failures, and optimize your notification strategy for maximum delivery rates.
Pro tip: Set up webhook callbacks alongside the dashboard for real-time programmatic tracking. Use the dashboard for manual monitoring and debugging, and webhooks for automated responses to delivery events.
Log Retention by Plan
| Plan | Log Retention | Analytics History | Export |
|---|---|---|---|
| Free | 7 days | 7 days | CSV |
| Pro ($9/mo) | 30 days | 90 days | CSV, JSON |
| Business ($29/mo) | 90 days | 1 year | CSV, JSON, Scheduled Reports |