Monitoring of services and transactions for C++ and other applications

OneAgent SDK for C/C++

You must have access to the program’s source code you wish to monitor to utilize the OneAgent SDK. The SDK allows you to instrument your application manually. The OneAgent SDK now supports remote call tracing and SQL database request tracing for C/C++ and will expand these features in the following months.

Check out our GitHub repository for an excellent place to start. The essential SDK documentation, including the hosted API documentation, can be found here.

Once you’ve compiled your application against the OneAgent SDK for C/C++, you can deploy it as usual. Your application will not be harmed by instrumentation.

​​

Automatic detection and deep monitoring of native applications

Deploy your native application on any monitoring system. If your program was operating at the OneAgent installation, you need to restart it. OneAgent identifies that your application has been instrumented with the SDK and begins monitoring it on a request-by-request basis, much like it does with Java and Node.js.

While you must access the source code of your native application to receive the whole OneAgent experience on a monitored machine, once OneAgent is installed, you only need to restart the application to begin scanning.

Examples of programs
​
The samples that come with the SDK include the following native programs.

This simple example software receives a remote call, connects to another component, and connects to a database. When service on a monitored host starts, it will appear on the Transactions & services page (see example below).

OneAgent is fully compatible with the OneAgent SDK. Remote calls that have been instrumented with the SDK are displayed as RPC service services, which function like any other service. All analysis and monitoring features, including auto-baselining and AI-based root cause analysis, are available.

It’s worth noting that this service, as predicted, calls another service and a database. To get a sense of what’s going on, let’s look at the Service flow and Smartscape.

OneAgent captured six queries to the service sample1.input processor, as you can see. In the PurePaths view, we can examine the individual requests from here.

The process technique takes up most of the time. However, the transform remote method on another service is also used.

The schematic structure of the recorded PurePath and any relevant timings may be seen at the code level.

I logged in to some database calls. The newly discovered database service tracked using the SDK may be seen.

Extend AI-based root cause analysis

OneAgent SDK C/C++ delivers visibility into your C programs and throughout your whole application ecosystem. All detected services and databases are monitored at the same degree of granularity. All queries to the sample1 sample application and any SQL statements from the newly discovered database are baselined.

What about Python, Ruby, Perl, and Erlang?

Language bindings allow Python, Ruby, Perl, and Erlang to make calls to C. We don’t intend to create language bindings for all four languages, but we hope to have something for Python later this year.

We’d love to hear what you think of the OneAgent SDK for C/C++. The most straightforward approach is to use the issue tracker in our GitHub repository. You can also leave a remark on our AnswerHub roadmap topic.

About Enteros

Enteros offers a patented database performance management SaaS platform. It proactively identifies root causes of complex business-impacting database scalability and performance issues across a growing number of RDBMS, NoSQL, and machine learning database platforms.