Dashboard¶

The Dashboard is the operational starting point after signing in. It combines service health, data usage, latency, traffic volume, certificate warnings, and recent security information so that users can recognise a problem before opening the detailed configuration or reporting pages.

The figures shown are limited to the entities and services available to your account. A system administrator may see information for the full environment, while another user may see only their assigned entity and its permitted descendants.

Dashboard tabs¶

Tab	Use it to answer
Your Service Overview	Are services healthy? Which URLs use the most data? Are there slow requests, alerts, certificate problems, or recent blacklist entries?
Data Usage & Spend	How much data is being used? How does usage change by day, user, service, or mobile network operator?
Realtime Reports	What are the current request rate and latency patterns for the selected services?

The Dashboard provides an operational view. Use Usage Reports for formal usage reporting and the reconciled or unreconciled billing pages for billing values.

Using Dashboard filters¶

The three tabs share the same style of filter controls. Changing a filter reloads the charts and cards on the current tab.

Entity filter¶

System administrators can filter by entity. Other users see this control when their authorised scope contains more than one entity.

All Entities includes services available across the user's current scope.
Select one or more entities to limit results to services assigned to those entities.
If the currently selected service does not belong to the new entity selection, the portal clears the service automatically.

Selecting no entity does not mean “no data”; it means all entities available to the user.

Service filter¶

Select one service to investigate it, or choose All Services for an aggregate view. The available service list follows the entity selection, so select the entity first when both filters are shown.

Similar service names may refer to different upstream systems or environments. Confirm the complete service name before using a chart as evidence of an incident.

Date range¶

The default range is the current day and the preceding 29 days, for a total of 30 calendar days. To choose another range:

Select the date-range button.
Select the first day.
Select a later day to complete the range.
Wait for all cards and charts to finish loading.

The displayed range includes both the first and last day. Dashboard queries use the beginning of the first day through the end of the last day.

Note

Dashboard components can load at different speeds because health, usage, reporting, certificate, and support data come from different sources. Wait for the individual loading indicators to finish before comparing values.

Your Service Overview¶

Dashboard overview

This tab combines current operational status with usage information for the selected range.

Service Health¶

The health chart separates services into Healthy and Unhealthy counts. The summary card also shows:

Services Down — services currently classified as unhealthy;
Open Issues — support issues currently associated with the available entity context; and
Log New Issue — opens the support workflow for reporting a problem.

A service can be healthy while still returning some failed requests, and a temporary upstream problem may appear before a support issue is opened. Use the health result as a starting signal, then inspect the service alerts and Realtime Reports.

If the health component reports that data could not be retrieved, this does not prove that every service is down. It means the portal could not obtain the complete health result.

Daily Unique Users¶

The line graph shows the number of unique users observed each day. In the current reporting model, users are identified from traffic data such as client IP address rather than an MSISDN or portal-user account.

Use this chart to find adoption trends or unusual changes. Remember that several people behind a shared proxy can appear as one IP, while one person moving between networks can appear as several IPs.

Longest Request Times (Top 5)¶

The bubble chart highlights the five slowest request-time observations across the selected services using p90, p95, and p99 latency results. Darker or larger bubbles indicate slower values. Hover over a bubble to see its rank, percentile, service, time, and formatted duration.

Percentiles describe the distribution rather than one individual request:

p90 means 90% of measured requests completed at or below that value;
p95 means 95% completed at or below it; and
p99 focuses on the slowest one percent of traffic.

A high p99 with a normal p90 can indicate an intermittent slow path rather than a problem affecting every request.

Total Data Usage¶

Total Data usage shows megabytes used by the selected entities, services, and date range. Previous Total Data Usage shows the equivalent preceding comparison period returned by the reporting service.

Compare the values only after confirming that the current entity, service, and dates are correct. A higher total may simply reflect a longer range or more selected services.

Top URLs¶

The Top URLs section lists the ten URLs responsible for the most data usage in the selected period and shows each URL's share of the total. Use it to identify heavy endpoints, downloads, or unexpected request paths.

A URL at the top is not automatically a problem. Check whether its traffic is expected, whether large responses are part of the API design, and whether caching or request controls are appropriate.

Security and Certificate Updates¶

This section draws attention to certificates that are invalid or whose remaining validity could not be determined. Open Gateway Configuration > Certificates to inspect the SNI names, status, and expiry date.

An empty warning list generally means no certificate requiring attention was returned. It does not replace the organisation's external certificate monitoring and renewal process.

Service alerts and errors¶

The error breakdown groups current alerts by service. It may show HTTP status-code alerts or latency alerts. Use the service name, code, and measured latency to decide where to investigate:

repeated 4xx errors often indicate client credentials, permissions, paths, or request validation;
5xx errors commonly require gateway or upstream-service investigation; and
latency alerts require comparison of proxy latency, upstream time, and total request time.

IP addresses blacklisted in the last 48 hours¶

The blacklist panel shows recent service-specific or global blacklist entries and provides Unblock IP where permitted. Verify the address and scope before unblocking it. A blocked address may represent a shared organisation, NAT gateway, proxy, or security scanner rather than one end user.

Use Traffic Management > Blacklist Management for the complete list and reject history.

Product suggestions and help links¶

The overview can display Obsidian service suggestions and links to help content or newly released features. Treat product suggestions as recommendations to review, not automatic configuration changes.

Health, support, certificate, blacklist, and suggestion sections are hidden from Reporter users. Reporters still receive the usage-oriented Dashboard content available to that role.

Data Usage & Spend¶

Data Usage and Spend

Despite the tab name, this screen primarily presents traffic-usage measurements. Use the billing reports when you require reconciled monetary amounts.

Daily Data Usage¶

The line graph shows total usage in gigabytes for each day in the selected range. A gap can mean no recorded data, a restrictive filter, delayed reporting, or a source-query problem. It should not immediately be interpreted as a service outage.

Summary cards¶

Card	Meaning
Total Data usage	Total data for the current filters and date range, displayed in MB.
Avg Usage Per User	Average data per observed user, displayed in MB. Users are derived from traffic identity such as IP address.
AVG Daily TPS Usage	Average daily transactions per second for the selected scope and range.

An average can hide short peaks. Use Realtime Reports when a service experiences brief overload even though its daily average appears normal.

Total Data per MNO¶

The operator chart breaks data usage down by registered mobile network operator and shows data size and variance for the selected range. Traffic is classified using the configured operator information and ranges.

If traffic appears under the wrong operator or is missing, check Management > Operators > Operator Range and confirm that ranges do not overlap.

Monthly Usage for Last 3 Months¶

The four cards show:

current month-to-date usage;
the complete previous month;
two months ago; and
three months ago.

These calendar-month cards provide a stable trend view and are loaded separately from the selected Dashboard date range. Do not expect them to change to match a short custom date selection.

Realtime Reports¶

Realtime Reports

Realtime Reports use Grafana-backed operational measurements. “Realtime” means the data is refreshed and aggregated more frequently than formal reports; it does not guarantee that every request appears instantly.

Service TPS¶

Transactions per second indicates how many requests the selected service receives over time. Use it to identify bursts, traffic drops, and sustained load. A drop to zero can be expected outside operating hours, but it can also indicate routing, client, or upstream problems.

Proxy Latency per Service¶

Proxy latency is time spent in the gateway before it begins receiving the upstream response. High proxy latency can point to gateway processing, plugins, routing, or resource pressure.

Upstream Time per Service¶

Upstream time measures how long the upstream service takes to respond after the gateway forwards the request. High upstream time usually directs investigation toward the application, database, dependency, or network path behind the gateway.

Request Time per Service¶

Request time is the overall processing time observed for the request. It includes gateway and upstream portions, so compare it with both proxy latency and upstream time.

Pattern	Likely next check
High request time and high upstream time	Inspect the upstream application and its dependencies.
High request time but normal upstream time	Inspect gateway processing, plugins, network behaviour, or response transfer.
TPS spike followed by latency spike	Check capacity, connection pools, rate limits, and upstream scaling.
TPS suddenly falls while errors rise	Check routes, authentication, termination/rate-limit plugins, and upstream health.

These patterns are diagnostic clues, not proof of a root cause.

Investigate an unexpected Dashboard value¶

Record the tab, metric, entity, service, and displayed date range.
Wait for all loading indicators to finish.
Narrow the filter to one affected entity and service.
Compare a known-good period of the same duration.
Use Realtime Reports to compare TPS, proxy latency, upstream time, and request time.
Check service alerts, Audit Logs, and recent plugin or route changes.
Check Usage Reports or billing reports when validating a formal total.
When escalating, include the time, filters, metric name, expected value, and a screenshot without secrets.

If Dashboard data is empty¶

Confirm that the selected period contains expected traffic.
Clear the entity and service filters.
Check whether your account has access to the required entity and service.
Refresh the browser once and allow each data source to load.
Check for an on-screen error identifying the component that failed.
Remember that a zero is a returned measurement, while a blank chart can mean no rows or a query failure.

The left menu groups portal pages by task:

Menu group	Purpose
Dashboard	Return to operational overview and reporting tabs.
Gateway Configuration	Manage entities, services, routes, consumers, plugins, certificates, and workflows.
Gateway	Manage campaigns, campaign classes, service limits, and entity limits.
Traffic Management	Manage request rate limiting and blacklist rules.
Reports	Open reconciled billing, unreconciled billing, and usage reports.
Administration	Manage users, snapshots, audit logs, and Observation Mode.
Management	Manage reconciliation uploads, operators, rates, default rates, and currencies.

Navigation panel

Select Documentation or Help & Support in the navigation footer when you need guidance or support. Documentation visibility follows portal permissions, so users may not see guides for features they cannot access.