DACS Receiver

The DACS Receiver collects operational metrics from DACS environments and sends them through an OpenTelemetry metrics pipeline.

Capabilities

• DACS operational information stored in PostgreSQL.
• Host-local monitoring of the DACS Server, Station daemon, ESP, Service Control Point, Sink daemon, and local and remote WAN daemons.
• Independent collection intervals and timeouts for each source.
• Metric-group and individual-metric selection.
• OpenTelemetry-compatible output for downstream processing and export.

SOAP collection is not offered as a supported customer capability in the current release and should remain disabled.

Prerequisites

• A PHO Collector distribution containing dacsreceiver.
• A PHO licence with one dacsreceiver entitlement per configured receiver instance.
• For PostgreSQL monitoring, network access and valid database credentials.
• For host-local monitoring, the Collector must run on a host containing the relevant DACS process.
• The Collector service account must be permitted to use the installed DACS statistics utility.

The Sink daemon commonly runs on an ADS host and may require a separate Collector deployment.

Configuration

At least one source must be enabled.

PostgreSQL settings

Host-local source settings

Each block accepts:

Example

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

receivers:
  dacsreceiver:
    postgres:
      enabled: true
      endpoint: postgresql://dacs-db.example.com:5432/dacs
      username: ${env:DACS_DB_USER}
      password: ${env:DACS_DB_PASSWORD}
      collection_interval: 30s
      timeout: 10s
    soap:
      enabled: false
    dacs_svr:
      enabled: true
      tool_path: /reuters/dacs/tools/set_debug
      collection_interval: 60s
      timeout: 15s
      groups:
        ping_status:
          enabled: true
      metrics:
        dacs.svr.load.position.count:
          enabled: false

processors:
  batch: {}

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

service:
  extensions: [pho_license]
  pipelines:
    metrics:
      receivers: [dacsreceiver]
      processors: [batch]
      exporters: [otlp]

Use environment variables or an approved secrets manager for credentials.

Metric groups

An individual metric setting takes precedence over its group setting. Unknown group and metric names are rejected during configuration validation.

PostgreSQL telemetry

Common attributes include dacs.source, dacs.component, dacs.site, dacs.db, dacs.vendor, and dacs.status_class.

Operational behaviour

• A failed collection does not report a misleading healthy or zero value.
• Other enabled sources continue operating when one source fails.
• Collection resumes automatically when the source becomes available.
• Monitoring should alert on both unhealthy values and missing data.

Troubleshooting