solarwinds/appoptics-bindings-node

Node.js native bindings for AppOptics APM

appoptics-bindings-node's Issues

Any plans to support native MacOS builds?

Right now the package (and therefore appoptics-apm-node) only support linux. This is mostly fine (our production env is all linux) but it would make testing easier if MacOS was supported. Are there any plans to support MacOS or is Linux a limitation of liboboe?

ARM64 support

Hello everyone!

I encountered problems when trying to install the appoptics-apm npm package on both a t4g AWS EC2 instance with ARM architecture and a Macbook M2. The error message was related to MODULE_NOT_FOUND, and upon further investigation, I discovered that the package was trying to load @appoptics/apm-bindings, but the required liboboe library was not present on the operating system. Further analysis showed that @appoptics/apm-bindings only includes x86 and alpine versions of the library, but an aarch64 version can be found on https://files.appoptics.com/c-lib/. I have submitted a PR to include the aarch64 version on systems with ARM64 architecture and it is working as expected on t4g EC2 instances.

PR: #127

the agent not working with .net core alpine images

Hi, we thought the agent supports Alpine images before the Alpine 3.14
Supported Platforms # Linux

When we test the .net core 3.1 Alpine and .net 6.0 Alpine, non of the images can collect any data. A list as below:

3.1-alpine3.16 not work
3.1-focal work
6.0-alpine3.15 not work
6.0-alpine3.14 not work
6.0-focal work
6.0 work

ASP.NET Core Runtime # Linux amd64 Tags

which package is required to make it work in Alpine?

Can't install on Mac after 6.0.0

This isn't about supporting Mac as a hosting platform, just a development one.

In the previous version, if I yarn install on a mac then the bindings fail to compile silently, but now I get a warning, it exits with a process.exit(1) and I can't go any further. I could move the bindings to the optionalDependencies but this would complicate our build process for boring reasons.

Any chance of making the install part of this log a warning but allow the install to continue on unsupported platforms?

Reporter.sendMetric is sending the keys name as the value

Problem

I'm using appoptics-apm-node to send my metrics, but when I used the TAGs I realized that the values ​​of the keys are coming with the value of the TAGs.

To reproduce the problem, I created a simple application and attached below, you need to run specifying your appoptics service key

appoptics-bindings-node-tags-bug.zip

npm install
APPOPTICS_SERVICE_KEY={YOUR-SERVICE-KEY} npm start

Solution

Looking for at the code I realized that in the assignment of the TAGs the same object, the values ​​of the TAGs, was being passed to key and value, probably error by CTRL+C and CTRL+V

The hotfix is here, but I could not run the tests 😞

mac support

Is mac support anywhere on the roadmap?

many developers use mac locally and if appoptics has an error they don't know till its deployed to a testing env.

linux vm is an option, but not a preferred one.

thanks again