Monitoring
The admin console provides two monitoring views: Request Analytics for authentication requests, and API Logs for API activity. Both views support filtering, searching, and CSV export.
Request analytics
Section titled “Request analytics”Navigate to Logs > Requests to see all authentication requests across your organization.
Summary cards
Section titled “Summary cards”The top of the page shows four summary cards for the selected time period:
- Total Requests — the total number of authentication requests
- Top Country — the country with the most requests
- Countries — the number of unique countries
- Peak Day — the day with the highest request volume
Request details table
Section titled “Request details table”Each row in the request table shows:
| Column | Description |
|---|---|
| Time | When the request was created |
| User | The user’s name and email |
| Location | Country, city, and IP address of the login attempt |
| Application | Which application the user was signing in to |
| Method | How the user authenticated: Push, Passcode, or BlokBadge |
| Status | The outcome of the request |
Request statuses
Section titled “Request statuses”| Status | Meaning |
|---|---|
| Accepted | User approved the sign-in request |
| Denied | User explicitly rejected the request |
| Expired | Request timed out before the user responded (default: 120 seconds) |
| Passcode | User authenticated using an administrative override passcode |
| BlokBadge | User authenticated using proximity-based badge scan |
| Superseded | A newer request replaced this one before it was completed |
Viewing request details
Section titled “Viewing request details”Click any row to open the request detail dialog, which shows:
- User and account information — who was signing in
- Location details — country, city, region, and IP address
- Timeline — when the request was issued, retrieved by the device, and responded to (with response time)
- Technical details — issuer DID, subject DID, and request identifiers
Filtering
Section titled “Filtering”Use the filter controls above the table to narrow results:
- Date range — 7 days, 30 days (default), 90 days, or a custom date range
- Search — search by user name, email, or application name
Exporting
Section titled “Exporting”Click Export to CSV to download the filtered request data as a spreadsheet.
API logs
Section titled “API logs”Navigate to Logs > API to see API call activity for your organization. This view is useful for tracking device registrations, integration activity, and troubleshooting.
Summary cards
Section titled “Summary cards”- Total API Calls — total calls in the selected period
- Success Rate — percentage of calls that returned HTTP 2xx
- Unique IPs — number of distinct IP addresses
- Peak Period — the period with the highest activity
API log table
Section titled “API log table”Each row shows:
| Column | Description |
|---|---|
| Time | When the API call was made |
| Method | HTTP method (GET, POST, PUT, DELETE) |
| Event | Event type, if applicable (device_not_recognized, etc.) |
| Endpoint | The API path that was called |
| User | The user associated with the call, if any |
| Status | HTTP response status code |
Filtering
Section titled “Filtering”API logs support additional filters:
- Date range — 24 hours (default), 7 days, 30 days, or 90 days
- HTTP Method — filter by GET, POST, PUT, PATCH, or DELETE
- Event Type — filter by specific event types like
device_not_recognized - Search — full-text search across log entries
Common troubleshooting patterns
Section titled “Common troubleshooting patterns”Authentication failures
Section titled “Authentication failures”Filter requests by status to find failed authentications:
- Expired requests may indicate notification delivery issues — check that the user’s device has push notifications enabled
- Denied requests mean the user actively rejected the sign-in — they may have received an unexpected request
Missing push notifications
Section titled “Missing push notifications”If users report not receiving notifications:
- Check the request log — if the request was created but never retrieved, the push notification may not have been delivered
- Verify the user’s device has a push token registered (check the user’s device list in their detail page)
- Ask the user to check their phone’s notification settings for the BlokSec app