Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Documentation Grafana Alloy Reference Components otelcol otelcol.receiver.solace

otelcol.receiver.solace

otelcol.receiver.solace accepts traces from a Solace PubSub+ Event Broker and forwards it to other otelcol.* components.

You can specify multiple otelcol.receiver.solace components by giving them different labels.

Usage

Alloy Copy

otelcol.receiver.solace "LABEL" {
  queue = "QUEUE"
  auth {
    // sasl_plain or sasl_xauth2 or sasl_external block
  }
  output {
    traces  = [...]
  }
}

Arguments

The following arguments are supported:

queue must have the format queue://#telemetry-myTelemetryProfile.

Blocks

The following blocks are supported inside the definition of otelcol.receiver.solace:

One SASL authentication block is required in the authentication block.

sasl_external must be used together with the tls block.

The > symbol indicates deeper levels of nesting. For example, authentication > tls refers to a tls block defined inside an authentication block.

authentication block

The authentication block configures how to authenticate for connecting to the Solace broker. It doesn’t support any arguments and is configured fully through inner blocks.

sasl_plain block

The sasl_plain block configures how to authenticate to the Solace broker with SASL PLAIN.

The following arguments are supported:

sasl_xauth2 block

The sasl_xauth2 block configures how to authenticate to the Solace broker with SASL XOauth2.

The following arguments are supported:

sasl_external block

The sasl_xauth2 block configures how to authenticate to the Solace broker with SASL External. It doesn’t support any arguments or blocks. It must be used with the tls block.

flow block

The flow block configures the behaviour to use when temporary errors are encountered from the next component. It doesn’t support any arguments and is configured fully through inner blocks.

delayed_retry block

The delayed_retry block sets the flow control strategy to delayed retry which will wait before trying to push the message to the next component again.

The following arguments are supported:

tls block

debug_metrics block

output block

Exported fields

otelcol.receiver.solace does not export any fields.

Component health

otelcol.receiver.solace is only reported as unhealthy if given an invalid configuration.

Debug information

otelcol.receiver.solace does not expose any component-specific debug information.

Example

This example forwards read telemetry data through a batch processor before finally sending it to an OTLP-capable endpoint:

Alloy Copy

otelcol.receiver.solace "default" {
  queue = "queue://#telemetry-testprofile"
  broker = "localhost:5672"
  auth {
    sasl_plain {
      username = "alloy"
      password = "password"
    }
  }
  tls {
    insecure             = true
    insecure_skip_verify = true
  }
  output {
    traces = [otelcol.processor.batch.default.input]
  }
}

otelcol.processor.batch "default" {
  output {
    traces  = [otelcol.exporter.otlp.default.input]
  }
}

otelcol.exporter.otlp "default" {
  client {
    endpoint = sys.env("OTLP_ENDPOINT")
  }
}

Compatible components

otelcol.receiver.solace can accept arguments from the following components:

• Components that export OpenTelemetry otelcol.Consumer