Evan Reinaldo (Customer) asked a question.

June 3, 2024 at 12:10 AM
OpenEdge Command Center Agent not sending any data to Open Telemetry Collector

I am experiencing an issue with the OECC Agent and need some assistance.

 

Here's the setup:

  • I have installed the OpenTelemetry Collector and OpenEdge Command Center Server on one linux machine.
  • I have three different machines, each installed with the OpenEdge Command Center Agent installed in windows.

The Command Center is working fine, and both the database and PAS are detected. However, the OECC Agent is not sending any data to OpenTelemetry, despite modifying the configuration files

otagentoedb.yaml and otagentpasoe.yaml.

 

Here are the details of the issue:

  • The config.yaml file for the Otel Collector has been configured as attached.
  • The metrics.json files from the file exporters are empty (0 bytes), indicating that nothing is being collected from the agents.
  • I also tried installing the Otel Collector on the same machine as one of the agents, but it also received no data.

 

Does anyone have any guidance on how to resolve this issue?

 

Thank you for your assistance.

  • 7 answers
  • 510 views

  • Yeshwant Sai Kandubothu (Progress Software)

    Hi Evan,

     

    I could see that you were using 1.3v of agent. We have certain known issues in 1.3 version out of which few were fixed in 1.4v of agent (which is yet to be released).

     

    1. In OEDB configuration file, you configured 2 databases with first one not having any username and password which are expected to be mandatory values for metric collection. Even if you configured them, it might not work in your case 'Coz of a known issue which is when we are configuring multiple databases in configuration file, metrics is being collected for only the first one in the list. This is the known issue that got fixed in 1.4v.
    2. When it comes to PASOE configuration file, in collector config file, grpc endpoint is having "localhost" but the pasoe and oedb configuration files are having endpoints with "IP". In both the places it should be either localhost or IP/hostname. Else, metrics won't be exported. This is a known issue which is yet to be fixed. I would suggest, If resources and collector are running on same machine please use localhost in all the configuration files. Otherwise use the IP/Host.

     

    And yeah, please restart the agent after you change config files or OE resources and collector after changing the config.yaml file

    Selected as Best

  • Ruben Droge (Progress Software)

    The Command Center agent logs (find the logs directory in the OECC agent install directory) should show a notion of those OpenTelemetry config files, could you share those as well?

    Have you restarted the OECC Agent after changing the configuration files?

    • Evan Reinaldo (Customer)

      Hi Ruben, I did restart the agent and I got this similar log files on every agent that I restarted after I change the config files as attached.

      This is the only info I got mentioning the collector on the log

       

      [INFO ] 2024-06-05 09:10:37.115 [OECC Thread Pool-1] DataCollectionService - Starting Data Collection Service

      [INFO ] 2024-06-05 09:10:37.115 [OECC Thread Pool-2] ServerConnectionService - run() :: Starting Server Connect service...

      [INFO ] 2024-06-05 09:10:37.115 [OECC Thread Pool-1] AgentResources - initialize() :: OpenEdge installation count 2

      [INFO ] 2024-06-05 09:10:37.115 [OECC Thread Pool-2] WebSocketConnector - connect() :: trying to connect to server with url ws://192.168.132.4:8000

      [INFO ] 2024-06-05 09:10:37.116 [main] FileWatchService - Successfully registered directory D:\Progress\OECC_Agent\conf with file monitoring service

      [INFO ] 2024-06-05 09:10:37.210 [ForkJoinPool.commonPool-worker-2] WebSocketListener - Agent successfully connected to OpenEdge Command Center Server

      Context Event Listener is getting executed

      Context Event Listener is getting executed

      Calling OT exporter API to collector

      Using collector config path: D:\Progress\OECC_Agent\conf\otagentpasoe.yaml

      Application Ready Event is successfully Started

      Application Ready Event is successfully Started

       

       

       

  • Yeshwant Sai Kandubothu (Progress Software)

    Hi Evan,

     

    1. For PASOE case - We need to mention the "pasDir" properly in otagentpasoe configuration file. If windows, path should be having either '\\' or '/'.
    2. For OEDB case - We need to mention the username and password in otagentoedb.yaml file for user who should be a 'DBA'. Below is the example for how to grant DBA permissions to a user using sqlexp.

     

    //Grant DBA to user

    grant dba to 'otuser1';

    commit;

     

    //Verify the permissions

    select * from sysprogress.sysdbauth;

    quit;

     

    Please let us know if you are still facing the issue

     

    • Evan Reinaldo (Customer)

      Hi Yeshwant,

      Thanks for correcting the PASOE case.

      For the OEDB, the user as attached has the permission as DBA

      ODBC loginoecc user querying the sysprogress.sysdbauthBut still have no data collected into the Open Telemetry collector from either PASOE or OEDB

  • Yeshwant Sai Kandubothu (Progress Software)

    Hi Evan,

     

    I could see that you were using 1.3v of agent. We have certain known issues in 1.3 version out of which few were fixed in 1.4v of agent (which is yet to be released).

     

    1. In OEDB configuration file, you configured 2 databases with first one not having any username and password which are expected to be mandatory values for metric collection. Even if you configured them, it might not work in your case 'Coz of a known issue which is when we are configuring multiple databases in configuration file, metrics is being collected for only the first one in the list. This is the known issue that got fixed in 1.4v.
    2. When it comes to PASOE configuration file, in collector config file, grpc endpoint is having "localhost" but the pasoe and oedb configuration files are having endpoints with "IP". In both the places it should be either localhost or IP/hostname. Else, metrics won't be exported. This is a known issue which is yet to be fixed. I would suggest, If resources and collector are running on same machine please use localhost in all the configuration files. Otherwise use the IP/Host.

     

    And yeah, please restart the agent after you change config files or OE resources and collector after changing the config.yaml file

    Selected as Best

  • Evan Reinaldo (Customer)

    Hi Yeshwant,

     

    Thanks so much for the reply.

     

    I'm happy to report that your solution worked perfectly! Instead of using localhost:4317, I changed it to my actual IP address. The default 0.0.0.0:4317 also didn't work, but once I updated it to my actual IP endpoint:

     

    192.168.132.4:4317

     

    and restarted both the collector and the agent, it started to collect the metrics.

    I've deleted the first database as you mention as well as it was a default database anyway.

     

    I also appreciate you informing me about the known issues. I'll look forward to the refined 1.4 version as well.

     

    Thanks again for your help!