# What’s New in Particle Horizon Collector 0.2

Particle Horizon Collector **0.2.x** expands the standalone OpenTelemetry distribution from its DACS foundation into a broader application and infrastructure telemetry platform.

The headline changes are two new Particle Horizon receivers, stronger packaged deployment behaviour, and a major expansion of the upstream OpenTelemetry components available in the binary.

## The 0.2 story

<table><caption class="sr-only">The 0.2 story</caption><thead><tr><th scope="col">Patch</th><th scope="col">What changed</th></tr></thead><tbody><tr><td><strong>0.2.0</strong></td><td>Introduced <strong>MosaicOA PE</strong> and <strong>VisualEdge</strong> receivers and shipped the Particle Horizon custom component set on the 0.2.0 release line.</td></tr><tr><td><strong>0.2.1</strong></td><td>Corrected Linux systemd package paths and aligned the collector with <code>phocol_components v0.2.1</code>.</td></tr><tr><td><strong>0.2.2</strong></td><td>Upgraded OpenTelemetry from <strong>0.152.0 to 0.156.0</strong> and enabled a much broader range of upstream Collector components.</td></tr></tbody></table>

## New in 0.2.0: MosaicOA PE observability

The `mosaicoapereceiver` brings MosaicOA PE status data directly into an OpenTelemetry metrics pipeline.

Instead of wrapping the `/status` endpoint with external scripts, the Collector can now poll it natively, parse both topic and summary rows, and emit structured telemetry.

Highlights include:

-   Topic record and poll counts.
-   xPath, update, Dataview, MODS, CIMP, GC, heap, and non-heap metrics.
-   PE version and lifecycle timestamps preserved as bounded resource attributes.
-   Configurable endpoint, interval, timeout, and TLS settings.
-   Cardinality controls.
-   Graceful handling of malformed rows and failed scrapes.
-   Particle Horizon licence-seat enforcement.

**Available since: 0.2.0**

## New in 0.2.0: VisualEdge observability

The `visualedgereceiver` moves VisualEdge installation checks into the Collector itself.

It reads the local VisualEdge installation and exposes telemetry for:

-   Installation availability.
-   VisualEdge release version and release timestamp.
-   MosaicOAPI JAR version metadata.
-   Licence end date.
-   Licence days remaining.

The receiver reports bounded status values for missing paths/files and parsing failures, allowing a monitoring pipeline to distinguish an unavailable installation from a healthy one without a separate shell-script integration.

**Available since: 0.2.0**

## One licensing model for Particle Horizon receivers

The custom receivers integrate with the `pho_license` extension. The extension is enabled once in the Collector service and validates that the licence grants seats for the proprietary components being used.

Across the 0.2.x line, the Particle Horizon receiver set is:

-   `dacsreceiver`
-   `mosaicoapereceiver`
-   `visualedgereceiver`

This keeps proprietary receiver entitlement inside the Collector lifecycle rather than in external wrapper processes.

## Improved in 0.2.1: packaged Linux deployments

0.2.1 is deliberately a smaller corrective release.

The systemd service included with Linux packages was updated to use the actual Particle Horizon package layout:

```
/opt/particle_horizon/pho-collector
/opt/particle_horizon/local_config/pho-collector/config.yaml
```

It also removes a stale dependency on an `otelcol-contrib.conf` environment file that is not shipped with the Particle Horizon package.

For operators using `.deb` or `.rpm` installations, **0.2.1 is the first 0.2.x patch with the corrected service definition**.

## New in 0.2.2: a much broader Collector

0.2.2 refreshes the upstream OpenTelemetry base from **0.152.0 to 0.156.0** and moves the core configuration providers from **1.58.0 to 1.62.0**.

It also enables many contrib components that were present but disabled in the earlier OCB manifest. The resulting binary can address a wider range of telemetry sources and destinations without creating another custom distribution.

Examples of the expanded receiver coverage include Kubernetes, Kafka, PostgreSQL, Oracle Database, RabbitMQ, NetFlow, Splunk, vCenter, Zipkin, ZooKeeper, AWS services, and additional log/metrics protocols.

**Available since: 0.2.2**

## Which version should I use?

For a new deployment, start with **0.2.2**. It includes the Particle Horizon receiver functionality introduced in 0.2.0, the packaging corrections from 0.2.1, and the newer, broader OpenTelemetry distribution.

Choose an earlier patch only when you specifically need to remain on the OpenTelemetry 0.152.0 component baseline for compatibility testing.

## Minimum version by capability

<table><caption class="sr-only">Minimum version by capability</caption><thead><tr><th scope="col">I need…</th><th scope="col">Minimum version</th></tr></thead><tbody><tr><td>MosaicOA PE receiver</td><td><strong>0.2.0</strong></td></tr><tr><td>VisualEdge receiver</td><td><strong>0.2.0</strong></td></tr><tr><td>DACS + MosaicOA PE + VisualEdge in one distribution</td><td><strong>0.2.0</strong></td></tr><tr><td>Correct Linux package systemd paths</td><td><strong>0.2.1</strong></td></tr><tr><td>OpenTelemetry 0.156.0</td><td><strong>0.2.2</strong></td></tr><tr><td>Expanded upstream contrib component catalogue</td><td><strong>0.2.2</strong></td></tr></tbody></table>

For implementation-level detail, configuration examples, metric names, upgrade considerations, and exact patch provenance, see the **Particle Horizon Collector 0.2.x Release Notes**.