The Juniper Mist extension collects metrics and topology data from the Mist cloud through the Mist REST and WebSocket APIs, and builds Smartscape topology for your wireless and wired network. Use it to track device availability, health, and radio performance, and to receive Mist alarms as Dynatrace events.
The Juniper Mist extension monitors the network infrastructure managed by the Juniper Mist cloud. The extension runs as a Python extension on an ActiveGate and connects to the Juniper Mist cloud API, authenticating with a Mist organization API token.
The extension bundles its own data source: the Python collector runs on the ActiveGate and retrieves the data from the Mist cloud. On the Mist side, you only need to generate an organization API token and store it in the Dynatrace credential vault.
On each collection cycle, the extension:
Observer (read-only) privilege is sufficient.The extension supports the following Mist clouds:
You can configure any other Mist environment as a custom endpoint. For details, see Create the monitoring configuration.
Note the following constraints:
Activation has four parts: generate the Mist API token, store it in the credential vault, activate the extension from Dynatrace Hub, and create the monitoring configuration. For prerequisites, see Requirements.
In the Mist portal, go to Organization > Settings > API Token and generate an organization API token. A token with the Observer (read-only) privilege is sufficient.
In Dynatrace, store the token in the credential vault as a token credential.
Activate the Juniper Mist extension in
Hub (see Deploy an extension from Dynatrace Hub). Upon activation, the extension deploys the Python collector, the metric definitions, the OpenPipeline metrics source and pipeline, the unified analysis screens, and the overview dashboard.
Add a monitoring configuration, select an ActiveGate group with access to the Mist cloud, and fill in the fields below.
| Field | Description |
|---|---|
Environment | The Mist cloud hosting your organization, for example, |
Custom environment | Turn on to connect to a Mist API host that isn't in the list of supported clouds, and then enter its hostname. |
Verify SSL certificate | Available only for custom environments. Turn off only if the endpoint uses a self-signed or otherwise untrusted certificate. |
Mist Organization Token | The credential vault entry that holds the Mist organization API token. |
Use proxy | Route REST and WebSocket traffic through an HTTP proxy. Enter the proxy host and port, and optionally a username and password. |
Import alarms | Import Mist site alarms as Dynatrace events. |
Import up interfaces only | Skip metrics for physical interfaces in the |
Log level |
|
Frequency | Metric collection interval in minutes (default |
Then select the feature sets you want to collect.
The Juniper Mist extension collects metrics and topology data for:
The extension reports device and interface metrics under the platform's com.dynatrace.extension.network_device.* namespace where one exists, and under juniper-mist.* otherwise.
The Juniper Mist extension is packaged with:
The extension builds its topology on Smartscape on Grail. The bundled Juniper Mist metrics pipeline extracts nodes and edges from the metrics as they arrive.
The extension creates JUNIPER_MIST_ORGANIZATION, JUNIPER_MIST_SITE, JUNIPER_MIST_NETWORK_DEVICE, and JUNIPER_MIST_NETWORK_INTERFACE nodes. Each Mist network device and interface is also linked to the platform's EXT_NETWORK_DEVICE and EXT_NETWORK_INTERFACE nodes, so the built-in network device pages are populated. Sites belong to their organization, devices are linked to their organization and site, and interfaces belong to their device.
The nodes populate automatically once the first collection cycles complete. Allow a few minutes.
To explore the topology, open
Smartscape, or
Infrastructure & Operations > Network. Filter for the Juniper Mist node types, and select an entity to explore its connections.
Each Juniper Mist entity type has an inventory list and an entity details view. You can reach them from
Infrastructure & Operations > Network > Juniper Mist, by selecting the entity in
Smartscape, or through global search.
| Entity | Inventory screen |
|---|---|
Juniper Mist Organization | Organizations |
Juniper Mist Site | Sites |
Juniper Mist Network Device | Network devices |
Juniper Mist Network Interface | Network interfaces |
Each inventory screen lists every entity of that type with its health alerts and current counts. Each entity details screen opens on an Overview tab of current state, backed by a Properties tab of the entity's attributes.
This extension doesn't ingest logs.
When Import alarms is turned on, each Mist alarm is ingested as a Dynatrace event, attached to the affected device, site, or organization.
There is no charge to use the extension. You are only charged for the data that the extension ingests.
The extension polls the Mist REST API and streams the Mist WebSocket API. It reports custom metrics from the responses. The metrics consume Davis Data Units (DDUs) (Dynatrace classic license) or Metrics powered by Grail (DPS), according to your license model.
In the Dynatrace Platform Subscription, metric ingestion consumes Metrics powered by Grail according to the number of ingested metric data points.
The following formula provides approximate data points ingested per year, assuming all feature sets are enabled.
((( 5 * number of Organizations)+ ( 9 * number of Sites)+ ( 17 * number of Access Points)+ ( 8 * number of Access Point physical interfaces)+ ( 13 * number of Access Point wireless interfaces)+ ( 5 * number of Gateways)+ ( 5 * number of Gateway interfaces)+ ( 5 * number of Switches)+ ( 5 * number of Switch interfaces)) / <Metrics collection interval>) * 60 minutes * 24 hours * 365 days data points per year
Omit any line for a feature set you don't enable. To reduce the number of interface metrics, see How can I reduce the number of interface metrics ingested?.
In the classic licensing model, metric ingestion consumes Davis Data Units (DDUs) at the rate of .001 DDUs per metric data point. Multiply the above formula for annual data points by .001 to estimate annual DDU usage.
The DDU cost above doesn't include the events created from imported Mist alarms. For more information, see DDUs for custom Davis events.
Device metrics are delivered through the Mist WebSocket API. Confirm that the ActiveGate can open secure WebSocket (WSS) connections to the Mist API host of your cloud, including through the configured proxy, if any. A newly added device appears only after the next device inventory refresh, which runs every 15 minutes.
BLE and LLDP metrics are collected only when the Access Point BLE and Access Point LLDP feature sets are turned on. These feature sets are turned off by default. Some metrics are also available only on specific hardware models or when the related feature is in use. For example, LLDP power metrics require the access point to be powered over PoE.
Turn on Import up interfaces only in the monitoring configuration to skip physical interfaces that are down. You can also turn off the interface feature sets (Access Point Interfaces, Gateway Interfaces, and Switch Interfaces) or increase the collection frequency.
The com.dynatrace.extension.network_device.if.status metric is 1 when the interface is up and 0 when it's down. The same information is available in the oper.status dimension.