You can enable the OpenEdge Command Center agent to collect performance metrics of a PAS for OpenEdge instance by specifying details in the otagentpasoe.yaml file. The file is present in the conf folder of the OpenEdge Command Center agent installation.

Follow these steps to enable the agent to collect performance metrics of a PAS for OpenEdge instance:

  1. Open the otagentpasoe.yaml file in an editor.
  2. In the exporter node of the otagentpasoe.yaml file, provide values for the following properties of the OpenEdge Command Center agent connection to the OTel Collector:
    • name—A name for the OpenTelemetry exporter. Ensure that the value is set to otlp.
    • endpoint—The target URL to which the exporter sends the performance metrics data. The OTel Collector receives the metrics data at this endpoint. Make sure to use the same endpoint when you configure the OTel Collector.
    • protocol—The transport protocol used to export the metrics data. Use grpc as the value for this property.
    • timeout—The maximum time the OTLP exporter waits for each batch export.
    • connectionretry—The number of times the OpenEdge Command Center agent tries to connect to the OTel Collector in case of a connection failure. To know more about the impact of connection failure and how the connection is restored, see Performance impact and resilience of collecting performance metrics.
  3. Under the pasInstances node of the YAML file, provide values for the following properties of the PAS for OpenEdge instances to be monitored:
    • pasdir—The location of the PAS for OpenEdge instance.
      Note: Make sure that a PAS for OpenEdge already exists at the specified location before you provide the value for the pasdir property.
    • passchedule—The time interval at which the agent must capture the metrics data. This property works in conjunction with the pasduration property. OpenTelemetry limits the frequency for posting data to a maximum of two times per minute or once every 30 seconds. Progress recommends sending metrics data once per minute.
    • pasduration—The unit of time interval at which the agent must capture the metrics data. The possible values can be seconds, minutes, hours, or days. This property works in conjunction with the passchedule property.
    • metricsregex—A regular expression (regex) to ensure that only the specified PAS for OpenEdge instance performance metrics whose names match the pattern you have configured are collected. When left blank, the agent captures all the defined metrics.
      Note: You can use only the * quantifier to create a regular expression.
  4. Save the changes made to the otagentpasoe.yaml file.

Here is a sample otagentpasoe.yaml file with details of two PAS for OpenEdge instances:

exporter:
 name: "otlp"
 endpoint: "http://localhost:4317"
 protocol: "grpc"
 timeout: 10
 connectionretry: 20
 

pasInstances:
 -  pasdir: "C:/OpenEdge/WRK/oepas5"
    passchedule: 30
    pasduration: SECONDS
    metricsregex:  
 -  pasdir: "C:/OpenEdge/WRK/oepas2"
    passchedule: 30
    pasduration: SECONDS
    metricsregex:

After updating the otagentpasoe.yaml file, restart the OpenEdge Command Center agent.