Skip to content
This repository has been archived by the owner on Jun 17, 2021. It is now read-only.

Node JS Skywalking support #112

Open
mailyathish opened this issue May 25, 2020 · 1 comment
Open

Node JS Skywalking support #112

mailyathish opened this issue May 25, 2020 · 1 comment

Comments

@mailyathish
Copy link

We are evaluating the Node JS implementation on Skywalking. During the Evaluation we had observed certain issue. Just checking is there any alternative methods of retrieving them.

We have node js application deployed on the Docker. We can see the Node js container getting connected to Skywalk successfully, Don't see any performance metrics.

  1. CPU
  2. Memory
  3. Heap
  4. Event loops

image

On tracing we don't see may metrics.

image

Is there way it's possibilities adding these metrics and profiling in depth.

@kezhenxu94
Copy link
Member

kezhenxu94 commented May 25, 2020

image

The fact that most of the charts are empty is expected, they are either not implemented or other language specific, (like JVM specific), if you're using docker, make sure the time zone is correct, i.e. the time zones in the UI and SkyWalking backend are the same

On tracing we don't see may metrics.

The trace page is not for metrics, it's for traces, the number of spans depends on your application and your services dependencies, if you have only one endpoint /rewards that is instrumented by NodeJS agent, it's expected too, if not, please provide a reproducible repo to help diagnose the problem, or try and fix yourself :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants