-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setup lightstep open telemetry js snippet #260
Comments
I have two suggestions.
b. migrate from create-react-app to next js with open telemetry |
How will be serve this as static single page cdn if we use express?
Why? What is the motivation (in a single line) to migrate the entire codebase to next js? What is the the investment cost of it vs incentive of doing so? |
https://lightstep.com/opentelemetry/js I don't take a deep dive into the source of lightstep-opentelemetry-launcher-node. But if some stuffs related to require('lightstep-opentelemetry-launcher-node') can't be built as static file, or if npm install @opentelemetry/api @opentelemetry/web @opentelemetry/tracing --save => need time to survey
can't be fully static. But cdn can also be used to cache the specific pattern of url.
I think, if sth like express is needed or the project becomes more complicated, next.js may also be cool. |
Yes ofcourse this should be the way to go: https://opentelemetry.io/docs/instrumentation/js/getting-started/browser/
If you build it in the distribution that is served like provided in above links ☝️ , it will be static.
Changing frameworks does not automatically solve code complexity. Building with a clean design in mind solves for the complexity. We have different perspective screens in the website and they all run just fine. Just to introduce a telemetry package, changing the entire framework is an overkill. |
@tim08094495757 I've updated the description. |
UPDATED
We need a vendor-neutral open-source Observability framework for instrumenting, generating, collecting, and exporting telemetry data such as traces, metrics, logs.
The following code walkthrough is better suited for node driven service and is meant for reference.
A good browser based example is given here:
LS_ACCESS_TOKEN
andLS_SERVICE_NAME
then setup the code like so:
Reference:
The text was updated successfully, but these errors were encountered: