PM Data Collection Guide
Overview
The PM Data Collection page allows you to manage which Performance Metrics (PM) counters are stored in InfluxDB. Nokia AirScale base stations report over 22,000 unique PM counters, but storing all of them is neither practical nor necessary for most use cases.
This guide explains how to select which counters to collect based on your monitoring requirements.
Quick Start
Accessing the PM Data Collection Page
- Navigate to the Control Panel:
https://localhost:9443 - Click on Data Filters in the navigation menu
- View and manage PM counter collection settings
Understanding the Interface
The page is divided into two main sections:
| Section | Description |
|---|---|
| Stored PM Data (Left) | Counters currently being collected and stored in InfluxDB |
| Available Counters (Right) | All 22,000+ counters available to add to your collection |
Counter Categories
PM counters are categorized by their code prefix, which indicates the technology and function:
| Category | Code Prefix | Count | Description |
|---|---|---|---|
| LTE | M8xxx | ~5,900 | LTE L1/L2/L3 counters (ERAB, RRC, handover, etc.) |
| WCDMA | M5xxx | ~885 | 3G WCDMA counters (MAC layer, CQI, HSDPA) |
| 5G-NR | M55xxx | ~14,500 | 5G NR counters (massive MIMO, beamforming, etc.) |
| 5G-Mobility | M51xxx | ~500 | 5G mobility and measurements |
| 5G-Common | M40xxx | ~250 | 5G common/shared counters |
Default Counters
On first startup, sensible defaults are loaded from priv/pm_counters.csv. These defaults include essential counters for:
- Energy: Power consumption monitoring
- Data Volume: Traffic volume metrics
- Availability: Cell availability statistics
- Accessibility: RRC connection success/failure
- PRB: Physical Resource Block utilization
- Throughput: UL/DL throughput metrics
- RRC: RRC connection statistics
- ERAB: E-RAB setup and release counters
- PDCP: PDCP layer metrics
- Handover: Inter-cell handover statistics
- Interference: UL interference measurements
Managing Counters
Adding Counters
- Use the search box or category filter in the "Available Counters" section
- Click on rows to select counters (checkbox will appear checked)
- Use Select All to select all visible counters
- Click Add Selected to move them to the stored collection
Removing Counters
- In the "Stored PM Data" section, select counters to remove
- Click Remove Selected to stop collecting those counters
Filtering and Searching
Both sections support:
- Text search: Filter by counter ID or description
- Category filter: Show only counters from a specific category (LTE, 5G-NR, etc.)
Resetting to Defaults
Click Reset to Defaults to restore the original counter list from priv/pm_counters.csv. This will remove any custom additions.
Persistence
Changes to your PM counter selection are:
- Persisted to disk in
priv/pm_filters.etf - Survive application restarts
- Take effect immediately (no restart required)
The InfluxDB batch writer is notified of changes and immediately starts/stops collecting the affected counters.
Storage Considerations
Why Not Collect Everything?
Collecting all 22,000+ counters would result in:
| Scenario | Impact |
|---|---|
| Storage | ~100-500 GB/month per site (depending on collection interval) |
| Write Load | Significant InfluxDB write pressure |
| Query Performance | Slower dashboard queries due to data volume |
| Cost | Higher storage and compute costs |
Recommended Approach
- Start with defaults: The pre-configured counters cover most common monitoring needs
- Add as needed: When building new dashboards, add specific counters you need
- Review periodically: Remove counters no longer being used
Counter Reference
Finding Counter Descriptions
The "Available Counters" section shows Nokia's official description for each counter. Use the search function to find counters by:
- Counter ID (e.g.,
M8012C23) - Description keywords (e.g.,
throughput,handover,RSRP)
Common Counter Examples
| Counter | Category | Description |
|---|---|---|
| M8012C23 | LTE | Average UL Throughput per cell |
| M8012C26 | LTE | Average DL Throughput per cell |
| M8001C2 | LTE | PDCP SDU Delay DL Mean |
| M8011C24 | LTE | UL PRB Utilization |
| M8011C37 | LTE | DL PRB Utilization |
| M8013C17 | LTE | RRC Connected Users |
| M8020C3 | LTE | Handover Success |
| M40001C0 | 5G | Energy Consumption |
Configuration Files
pm_counters.csv
Default counters loaded on first startup:
# Format: counter,category,description
M8012C23,Throughput,Average Uplink Throughput
M8012C26,Throughput,Average Downlink Throughput
M8001C2,Availability,Cell Availability
...
Location: priv/pm_counters.csv
pm_metrics.csv
Complete reference of all available counters:
# Format: PM_Code,Category,Description
M8000C6,LTE,S1_SETUP_ATT
M8000C7,LTE,S1_SETUP_SUCC
...
Location: priv/pm_metrics.csv
Troubleshooting
Counters Not Being Collected
- Verify the counter is in "Stored PM Data" (left side)
- Check that the eNodeB is pushing PM data (see InfluxDB Status page)
- Verify the counter ID matches exactly (case-sensitive)
Changes Not Taking Effect
- Filter changes are applied immediately to the batch writer
- New data only appears after the next PM push from the eNodeB (typically every 15 minutes)
- Check application logs for
[PmFilterStore]errors - Verify disk is writable for persistence file
Missing Counter Descriptions
- Counter descriptions come from
priv/pm_metrics.csv - Ensure this file is present and properly formatted
- Check for UTF-8 encoding issues
Related Documentation
- Data Retention Policy - How long PM data is kept
- Grafana Integration - Building dashboards with PM data
- InfluxDB Queries - Querying PM data
Access Points
- PM Data Collection:
https://localhost:9443/nokia/pm-filters - Data Retention:
https://localhost:9443/nokia/retention - InfluxDB Status:
https://localhost:9443/nokia/influx