MarketsIO Receiver

The MarketsIO Receiver collects OpenTelemetry metrics from MarketsIO monitoring segments for APX, PGX, and APG applications. Each receiver instance monitors one logical segment.

MarketsIO Receiver
Property	Value
Component ID	`marketsioreceiver`
Type	Receiver
Signal	Metrics
Applications	APX, PGX, APG
Availability	PHO Collector distribution

Capabilities

Monitors APX, PGX, and APG applications.
Selects telemetry by MarketsIO source class.
Reports segment availability and discovered entity counts.
Emits application telemetry under the mio.* namespace.
Supports multiple named receiver instances for multiple segments.

Prerequisites

A Linux host with access to the MarketsIO monitoring segment.
Read permission for the Collector service account.
The segment’s logical key.
At least one source class to monitor.
A PHO licence with one marketsioreceiver entitlement per configured instance.

Configuration

Configuration
Setting	Required	Default	Description
`application`	Yes	—	`APX`, `PGX`, or `APG`
`segment_key`	Yes	—	Logical MarketsIO segment name
`collection_interval`	No	`30s`	Collection frequency
`metric_groups.enabled_source_classes`	Yes	—	Source classes to collect

The segment key is a logical MarketsIO name such as EventStream.apx, not a filesystem path. Source-class names are exact and case-sensitive.

Example

extensions:
  pho_license:
    file: /etc/otelcol/license.json

receivers:
  marketsioreceiver/apx-primary:
    application: APX
    segment_key: EventStream.apx
    collection_interval: 30s
    metric_groups:
      enabled_source_classes:
        - AxisContext
        - DispatcherMonitor
        - EtaConnection

processors:
  batch: {}

exporters:
  otlp:
    endpoint: telemetry-gateway.example.com:4317

service:
  extensions: [pho_license]
  pipelines:
    metrics:
      receivers: [marketsioreceiver/apx-primary]
      processors: [batch]
      exporters: [otlp]

For multiple segments, configure multiple named instances:

receivers:
  marketsioreceiver/apx-primary:
    application: APX
    segment_key: EventStream.apx
    metric_groups:
      enabled_source_classes: [AxisContext, DispatcherMonitor]

  marketsioreceiver/pgx-primary:
    application: PGX
    segment_key: EventStream.pgx
    metric_groups:
      enabled_source_classes: [AxisContext, EtaConnection]

Supported source classes

The available set varies by application and release. Supported classes include:

APEngine, APService, APSession, APUserService
AxisContext, AxisGroupMgr, AxisServer, AxisService
DispatcherMonitor
EtaConnection, EtaServer
EventStream
GtpConnection, GtpServer, GtpStats
GtwyEngine, GtwyService, GtwySession, GtwySessionService
LoadBalancerEngine, LoadBalancerServer, LoadBalancerService
MuxConnection
QosEngine
ThreadContext, ThreadMgr, ThreadStats
VcEngine, VcService

Consult the PHO-provided application metric catalogue before enabling a class that may not be present in the selected application.

Source Classes by Application

The MarketsIO receiver supports the APX, PGX, and APG applications. Source class names are exact and case-sensitive.

APX

APX provides 22 source classes:

APEngine
APService
APSession
APUserService
AxisContext
AxisGroupMgr
AxisService
DispatcherMonitor
EtaConnection
EtaServer
EventStream
GtpConnection
GtpServer
GtpStats
GtwyEngine
GtwySession
LoadBalancerEngine
LoadBalancerService
QosEngine
ThreadMgr
ThreadStats
VcEngine

PGX

PGX provides 18 source classes:

APEngine
APService
APSession
AxisContext
AxisGroupMgr
AxisService
DispatcherMonitor
EtaConnection
EventStream
GtpConnection
GtpServer
GtpStats
GtwyEngine
GtwySession
QosEngine
ThreadMgr
ThreadStats
VcEngine

APG

APG provides 26 source classes:

APEngine
APService
APSession
APUserService
AxisContext
AxisGroupMgr
AxisServer
AxisService
DispatcherMonitor
EtaConnection
EtaServer
EventStream
GtwyEngine
GtwyService
GtwySession
GtwySessionService
LoadBalancerEngine
LoadBalancerServer
LoadBalancerService
MuxConnection
QosEngine
ThreadContext
ThreadMgr
ThreadStats
VcEngine
VcService

Receiver telemetry

Receiver telemetry
Metric	Unit	Description
`marketsio.receiver.up`	`1`	Whether the segment supplied a valid active snapshot
`marketsio.receiver.entities`	`1`	Entities found in each enabled source class
`marketsio.receiver.variables`	`1`	Monitored variables found in each enabled source class

Application metrics are emitted under mio.*. Depending on the application and selected classes, these cover:

Application and service health.
Sessions and connections.
Dispatcher and gateway activity.
Processing engines.
Queues and throughput.
Thread activity.
Quality-of-service information.
Load-balancing services.

Useful resource attributes include marketsio.application, marketsio.segment_key, service.name, and service.version. Entity metrics carry the identifiers appropriate to their source class.

Operational behaviour

Only selected source classes are emitted.
An inactive or unavailable segment is represented by marketsio.receiver.up = 0.
Invalid applications, unknown or duplicate source classes, and invalid segment keys are rejected at startup.
Metrics without a valid current value are omitted rather than reported as misleading zeroes.

Troubleshooting

Troubleshooting
Symptom	Recommended action
`marketsio.receiver.up` is `0`	Confirm the MarketsIO application is running and the configured segment is active
Receiver cannot access the segment	Verify the Collector service account’s permissions
Unknown source-class error	Check the spelling, case, and availability of the class for the selected application
Expected application metrics are absent	Confirm the relevant source class is enabled
A second instance does not start	Confirm the licence provides sufficient capacity for all instances

Services

Documentation

Technical support

Collector