The OpenEdge Command Center agent runs on the same machine as the monitored OpenEdge resource and regularly interacts with the resource for collecting the performance metrics data. However, this action has a negligible impact on the performance of the OpenEdge resource.

Installing OTel Collector on the same machine as the OpenEdge Command Center agent and the monitored OpenEdge resource can impact the performance of the OpenEdge resource. So, it is recommended to install OTel Collector on a different machine.

You can further reduce the performance impact by increasing the time interval at which the agent scrapes the metrics data. To increase the time interval:
  • When monitoring an OpenEdge database, increase the value of the dbschedule property in the otagentoedb.yaml file.
  • When monitoring a PAS for OpenEdge instance, increase the value of the paschedule property in the otagentpasoe.yaml file.
Contact Progress Technical Support if you have any queries on the performance impact.

When the monitored OpenEdge resources are running, the OpenEdge Command Center agent continues to collect metrics data and sends it to the OTel Collector. The collection of metrics data ceases when the OpenEdge Command Center agent stops. If the monitored OpenEdge resource stops and then restarts, the collection of metrics data resumes if both the OpenEdge Command Center agent and OTel Collector are running.

If the OTel Collector stops or the connection between the OpenEdge Command Center agent and the OTel Collector is disrupted, the Command Center agent tries to reconnect as per the value configured for the connectionretry property in the otagentoedb.yaml or otagentpasoe.yaml file.
  • If the connection is restored within the configured retry attempts, the Command Center agent sends the performance data to the OTel Collector.
  • If the connection is not restored within the configured retry attempts, the Command Center agent stops sending the performance data to the OTel Collector and ceases collecting the data from the OpenEdge resource. You must restart both the OpenEdge Command Center agent and the OTel Collector to resume monitoring of the OpenEdge resource.

If the connection between the OpenEdge Command Center agent and the OTel Collector is disrupted due to an incorrectly configured YAML file on the Command Center agent, update the configuration file and restart the Command Center agent.