OpenTelemetry log streaming
- Last Updated: May 12, 2026
- 3 minute read
- Progress Data Cloud
- Documentation
Progress Data Cloud streams service logs using an OpenTelemetry (OTel)-compliant feed. You can receive these logs with any OTel-compatible collector. The feed includes all log files generated by all hosted services and stdout output.
You can connect one collector endpoint to receive logs from Progress Data Cloud. If you need to send logs to multiple destinations, then configure your collector to forward them to additional downstream systems.
The feed supports two transport protocols:
- OTLP (
otlp) — Sends log data over gRPC, a high-performance binary protocol. - OTLP HTTP (
otlphttp) — Sends log data over HTTP, which is easier to route through firewalls and proxies.
Set up log streaming
To enable the telemetry feed, provide the following details to the Progress Data Cloud Operations Team:
1. Exporter type
Choose the transport protocol that matches your collector:
otlp— Use this if your collector accepts gRPC connections.otlphttp— Use this if your collector accepts HTTP connections.
2. Collector endpoint
Provide the URL where Progress Data Cloud sends the log data. The endpoint must meet these requirements:
- Uses a secure TLS connection (HTTPS).
- Is accessible from the Progress Data Cloud infrastructure.
Example: https://example.com/otel-collector/v1/logs
3. Authentication token
Provide a bearer token that Progress Data Cloud uses to authenticate when sending logs to your collector. The token should be a secure, randomly generated value, and your collector should be configured to accept only authorized sources.
Log attributes
Each log entry contains the following attributes:
| Attribute | Description |
|---|---|
| timestamp | The time the log entry was generated. |
| resource.attributes.ServiceType | The cloud-hosted service that produced the log entry. See Service types for possible values. |
| resource.attributes.SeverityText | The severity level of the log entry (for example, INFO, WARN, ERROR). Possible values vary by service — refer to the relevant service documentation for details. |
| attributes.FileName | The path and name of the source log file on the server. |
| body | The log message content. |
Service types
The ServiceType attribute identifies which service produced a log entry.
| Service Type | Service |
|---|---|
| CONS | Concepts Server |
| SES | Semantic Integration Service |
| CS | Classification Language Service |
| PR | Classification Precision and Recall Service |
| RS | Reconciliation Server |
| STUDIO | Semaphore Studio |
| MARKLOGIC | MarkLogic Server |
| DATAHUB-CENTRAL | Data Hub Central |
| FLUXBOX | FluxBox Service |
| OPENEDGEMCP | OpenEdge MCP ABL Service |
| DS | Data Symphony Service |
Troubleshooting
After the Operations Team enables your feed, logs should begin arriving at your collector endpoint. If you do not receive log data:
- Verify that your collector endpoint is accessible over HTTPS.
- Confirm that the bearer token configured on your collector matches the token you provided.
- Check your collector's own logs for authentication or connection errors.
- Contact the Progress Data Cloud Operations Team if you need assistance with the configuration.
For questions about telemetry feed configuration or to request setup, contact the Progress Data Cloud Operations Team with your collector requirements.
