You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 17, 2021. It is now read-only.
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.
CPU
Memory
Heap
Event loops
On tracing we don't see may metrics.
Is there way it's possibilities adding these metrics and profiling in depth.
The text was updated successfully, but these errors were encountered:
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
On tracing we don't see may metrics.
Is there way it's possibilities adding these metrics and profiling in depth.
The text was updated successfully, but these errors were encountered: