Set up OpenTelemetry (OTel) Collector to collect, process, and export performance metrics data of OpenEdge resources from the OpenEdge Command Center agent to various destinations, such Application Performance Monitoring (APM) tool.

To set up OTel Collector, perform the following steps:

  1. Download and install the appropriate version of OTel Collector for your platform. The minimum supported version is 0.31 and the last certified version is 0.129.1. For more information about installing OTel Collector, see OpenTelemetry Collector documentation.
    Note: You can install OTel Collector on any system, but Progress recommends installing it on a different system from the one hosting the OpenEdge Command Center agent for optimal performance. You can also configure multiple agents to share performance metrics data with the same OTel Collector.
  2. Open the config.yaml file of the OTel Collector installation directory in an editor.
    The config.yaml file contains the following sections:
    • receivers—Provide details about how OTel Collector can get data from the OpenEdge Command Center agent.
    • processors—Provide details about what OTel Collector does with the received data.
    • exporters—Provide details about where OTel Collector sends data for the Application Performance Monitoring (APM) tools.
  3. In the receivers node, ensure that the value of the endpoint property is the same as specified for the exporter.endpoint property in the otagentoedb.yaml or otagentpasoe.yaml files.
  4. Edit the config.yaml file and provide information for the following properties in the exporters node:
    • Set debug: verbosity to detailed.
    • Set file: path to ./export.json. This is the JSON file where OTel Collector saves metrics data for the APM tool.
    • Set otlp/elastic: endpoint to the location of the APM tool. For example, you may set the value to localhost:8200.
  5. Edit other properties listed in the config.yaml file per your requirements. To know more about these properties, see the OpenTelemetry Collector documentation.
  6. Save the changes made to the config.yaml file.
    Here is a sample config.yaml file:
    receivers:
  otlp:
    protocols:
      grpc:
      http:
  otlp/withendpoint:
    protocols:
      grpc:
        endpoint: localhost:4317


exporters:
  debug:
    verbosity: detailed
  file:
    path: ./export.json
  otlp/elastic: 
    endpoint: localhost:8200
    insecure: true
    

processors:
  batch:
service:
  pipelines:
    traces:
      receivers: [otlp, otlp/withendpoint]
      exporters: [debug, otlp/elastic]
    metrics:
      receivers: [otlp, otlp/withendpoint]
      exporters: [debug, file, otlp/elastic]
  7. Start OTel Collector after updating the config.yaml file by completing the following steps:
    1. Open a Command window and browse to the OTel Collector installation folder.
    2. Start OTel Collector by specifying the config.yaml file you updated. Use the following command: 
      <OTel Collector executable> --config config.yaml
      For example on the Windows platform, use the following command:
      otelcontribcol-0.129.1-windows_amd64.exe --config config.yaml