The OpenEdge 12.6 release introduced support for OpenTelemetry Metrics with OpenEdge Command Center 1.2.
OpenTelemetry is a vendor-neutral open-source observability framework for instrumenting, generating, collecting, and exporting telemetry data such as traces, metrics, logs. It standardizes the way telemetry data is collected and transmitted to backend observability platforms. Observability is the ability to measure the internal states of a system only using information from outputs, namely sensor data. for instrumenting, generating, collecting, and exporting telemetry data. As an industry-standard it is natively supported by a number of vendors.
Telemetry data is used to understand the performance and behavior of software.
Support for OpenTelemetry Metrics was introduced with OpenEdge Command Center 1.2 in the OpenEdge 12.6 release. The OpenEdge Command Center agents can collect performance metrics from the OpenEdge database and PAS for OpenEdge.To know more about monitoring OpenEdge resources and the deployment architecture, please refer to the OpenEdge article Monitor OpenEdge Resources using the OpenEdge Command Center agent.
In this blog, we outline the steps on how to create a test infrastructure to use the OpenTelemetry Metrics Support for OpenEdge on Azure.
The infrastructure uses multiple components. To simplify the deployment, the test infrastructure uses a single virtual machine. Some components are run at the OS level and others are run as a container.
The following files are required to create the infrastructure:
In this section, we create the virtual machine to run the components used for OpenTelemetry Metrics Support and launch the Bash Cloud Shell environment in Azure to connect to it.
1. Connect to the Azure Portal using your own credentials.
2. Create a new Resource Group.
3. Create a new Virtual Machine named "TestVM" using the Ubuntu Server 20.04 LTS image from Canonical. Go to the resource and take note of the Public IP Address.Notes:
4. Launch the Bash Cloud Shell environment on Azure. In this blog, we use the Cloud Shell environment on Azure to connect to the VM. Alternatively, you can use SSH on your local machine.
In this section, we upload the support files to the machine.
1. Launch the Bash Cloud Shell environment on Azure. In this blog, we use the Cloud Shell environment on Azure to connect to the VM. Alternatively, you can use SSH on your local machine.
2. Upload the following files to the Cloud Shell:
3. Change permissions of the TestVM_key.pem file:
4. Connect to the VM and create a /files folder:
On the VM run the following commands:
Alternatively, you can use:
5. Upload pre-requisite files to the VM:
The setup.sh script installs OpenEdge, OpenEdge Command Center and open source components used for the test infrastructure:
1. Connect to the VM and clone the OpenEdge Demos repo from GitHub:
On the VM run the following command:
2. Run setup.sh from the ~/openedge-demos/otlp folder:
3. Run test.sh from the ~/openedge-demos/otlp folder to confirm that the services are running:
In this section, we access the web interface for Grafana.
1. Add access to port 3000 on the VM in the Network Security Group (Virtual Machine / Networking).
2. Access Grafana at http://<Public IP Address>
3. Change the administrator password.
4. Add a Data Source for Prometheus using http://prometheus:9090 as the URL.
5. Click on Save & Test.
6. Click on Dashboards / Import on the sidebar.
7. Copy and paste the text of a sample OpenEdge Dashboard (https://github.com/progress/openedge-demos/blob/master/otlp/openedge-dashboard.json) into the “Import via panel json” editor.
8. Click on Load.
9. Click on Import.
10. The sample OpenEdge dashboard should now show:
In this post we have learned how to create the infrastructure to use OpenTelemetry Metrics Support in OpenEdge on Azure.
How was your experience setting up and using this environment?
Would you like to create this test infrastructure on other cloud or virtualization environments?
Please let us know in the comments.
Thank you for reading.
Edsel Garcia is a Software Architect in the Progress OpenEdge Engineering group. Edsel has a long history of first-hand experience using Progress products, starting as a customer and application developer more than 25 years ago. During his over 20-year tenure at Progress, Edsel has been a member of many teams, including Customer Support, Solution Engineering development, Tooling development, OpenEdge Architect product development and more. Edsel has recently been working on the Docker Container for PASOE project and CI/CD for OpenEdge with High Availability.
Let our experts teach you how to use Sitefinity's best-in-class features to deliver compelling digital experiences.Learn More
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
You can also ask us not to share your Personal Information to third parties here: Do Not Sell or Share My Info
We see that you have already chosen to receive marketing materials from us. If you wish to change this at any time you may do so by clicking here.
Thank you for your continued interest in Progress. Based on either your previous activity on our websites or our ongoing relationship, we will keep you updated on our products, solutions, services, company news and events. If you decide that you want to be removed from our mailing lists at any time, you can change your contact preferences by clicking here.