Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

CONNECT flows

Logging

  • Last UpdatedNov 02, 2026
  • 2 minute read

Flow runtime logs contain information about activities and events and are created for both the host and individual flows. Some events are also sent to Flow manager for centralized monitoring.

Logs are rotated once per day unless a log file reaches the 10 MB size limit. When a log file reaches 10 MB, a new log file is created. Each subsequent log file is labeled with a timestamp and a sequential number.

One set of log files is created for each process running on a device. By default, logs are stored on the local hard drive in the following directories:

  • All logs: ./data/logs

  • Log files for each flow runtime host: ./data/logs/host

  • Separate log files for each flow: ./data/logs/runtime/<flow ID>

  • Log files for flow runtimes initiated in remote sessions: ./data/logs/runtime/remotesession/<flow ID>

    Note: In addition to flow runtime logs, you can access information about events through the HTTP admin API and the internal MQTT broker (typic: $aveva/#). See Monitor flow activity from an external system for more information.

Logging parameter settings

The following table describes the parameter settings in the appsettings.json file, which control the information captured in flow runtime logs.

Parameter

Description

Default

LogLevel

The level of details in the logs, by order of decreasing details: Debug | Verbose | Information | Warnings | Errors

Information

LogAllExceptions

Include all exceptions in the logs (independent of log level)

false

Send logs to external monitoring systems

Logs can also be sent to external monitoring systems using Open Telemetry (OTEL).

Note: By default, flows have write access to flow runtime logs. If log integrity is important (for example, to prevent repudiation), we recommend using OTEL to ship logs to an external system.

External logging is configured in the observability.json file. The following table lists the available parameters settings.

Parameter

Description

Default

PrometheusEnabled

Enables the Prometheus metrics exporter, exposed at /metrics.

false

OtlpEndpoint

Shared OTLP collector endpoint. Used when a signal-specific endpoint is not set.

null

OtlpProtocol

Shared OTLP transport protocol: grpc or http/protobuf. Used when a signal-specific protocol is not set; if unset, the OpenTelemetry exporter default applies.

null

MetricsOtlpEndpoint

OTLP endpoint for metrics; falls back to OtlpEndpoint.

null

MetricsOtlpProtocol

OTLP protocol for metrics; falls back to OtlpProtocol, then the exporter default.

null

LogsOtlpEndpoint

OTLP endpoint for logs; falls back to OtlpEndpoint.

null

LogsOtlpProtocol

OTLP protocol for logs; falls back to OtlpProtocol, then the exporter default.

null

TracesOtlpEndpoint

OTLP endpoint for traces; falls back to OtlpEndpoint.

null

TracesOtlpProtocol

OTLP protocol for traces; falls back to OtlpProtocol, then the exporter default.

null

TracesSampleRatio

Trace sampling ratio from 0.0 (sample none) to 1.0 (sample all eligible traces).

1

ExportIntervalSeconds

Delay in seconds between scheduled OTLP metrics batch exports.

60

ExcludeMetricPatterns

Metric-name substrings to exclude from Prometheus/OTLP export. Matching is case-insensitive; excluded metrics remain available through IPC and the local UI.

[ ]

In This Topic