ToolFeatured

DataMiner Starlink Enterprise connector: NOC monitoring of Starlink fleets

Sep 21, 2026Skyline CommunicationsSource: DataMiner Catalog405 views

Skyline's DataMiner connector polls Starlink's Enterprise Telemetry API every 60 seconds and the Management API for usage and activation, giving a NOC per-terminal signal quality, throughput, alerts, service lines and 12 months of data usage. Versions 1.1.0.x support API v2.

What it is

DataMiner is Skyline Communications' monitoring and orchestration platform, widely used in broadcast and satellite operations centres. Its Starlink Enterprise connector (formerly "Starlink Telemetry API"; version 1.0.0.1 of the new name equals 1.0.0.4 of the old) reads Starlink's Enterprise APIs over HTTP with JSON payloads and turns the data into DataMiner elements, alarms and trend graphs. Versions 1.0.0.x to 1.0.3.x speak Starlink API v1; 1.1.0.x speaks API v2 and requires at least one Starlink Enterprise Account element. It is installed from the DataMiner Catalog, with dashboards and alarm templates provisioned automatically.

What it monitors

  • User terminals: signal quality, downlink throughput, and an approximate position from the H3 cell the terminal reports (cell centre, not exact coordinates).
  • Service line statistics: aggregated KPIs per service line, which is how Starlink bills a fleet.
  • Alerts raised by terminals and routers, routers themselves and IP allocations.
  • Services and usage: active plans with automatic top-up, monthly and daily data usage kept for twelve months, split fixed/mobile and priority/standard, plus overage lines.

The Telemetry API is polled every 60 seconds; Management API calls (activation, deactivation, usage reports) are paginated. Terminals removed from the account are kept one day before deletion. Each terminal can be exposed as its own dynamic virtual element so that a customer sees only its own dishes. A demo mode with mock data runs until credentials are entered.

Who it is for

Operators of fleets rather than single sites: shipping companies running Starlink on dozens of vessels next to VSAT, managed service providers that resell Starlink to enterprises, broadcasters and event companies with terminals on the road. Starlink's own portal shows current status; what it lacks is long-term retention, configurable alarm thresholds and reports against an SLA. Those are the reasons a NOC puts Starlink in the same screen as its GEO capacity and terrestrial links. The Starlink maritime integrators and enterprise integrators in our directory are the companies that typically operate this kind of setup for their customers.

How to use it

  1. You need a Starlink Business or Enterprise account with API access: a client ID and client secret issued in the Starlink account portal.
  2. Install the Starlink Enterprise package from the DataMiner Catalog; create one "Starlink Account [name]" element per account and enter the credentials.
  3. Wait one to two minutes for the buffer to fill, then check the User Terminals and Service Line Statistics tables.
  4. Tune the alarm templates (signal quality, offline duration, usage thresholds) and enable per-terminal virtual elements if customers need their own view.

Limits

It requires a DataMiner system, which is a platform purchase, not a download; the connector adds nothing for a home or single-site user. Positions are H3 cell centres, so it is not a tracking tool. It reads what Starlink's Enterprise API publishes, so metrics such as obstruction detail that the local gRPC exposes (see starlink-grpc-tools) may not be available through it.

Related

Definitions: telemetry, maritime satellite connectivity, Starlink. Guide: Starlink Maritime vs VSAT for commercial fleets.

Find a provider

The listings this resource is relevant to — every company is profiled with services, coverage and contact details.

Keep reading

Related resources