I was able to run both helm charts and using `./in...
# contributing
a
I was able to run both helm charts and using
./install.sh
(uses docker-compose). Mind you,
./install.sh
needs lower memory compared to
helm
installation
a
tried with the docker approach. got the thing up and running. exploring telemetry examples.
thanks šŸ™‚ šŸ‘
a
Cool
Let us know which area would you be able to help us. It varies from frontend, backend, docs, more deployment options, and more
a
create-supervisor /bin/sh -c curl -X POST -H ... Exit 0 flattener-processor ./flattener Exit 2 I just saw this two errors.
these services are not getting up I guess. are these relevant for now?
a
oh is it so...try rerunning
./install.sh
. flattener-processor has to be up for anything to work further down
Exit 0
means successful exit. create-supervisor is a job and hence this is correct
p
@User šŸ‘†
šŸ‘ 1
a
https://signoz.io/docs/instrumentation/nodejs was trying to run from the docs here.
OTEL_EXPORTER_OTLP_SPAN_ENDPOINT=ā€œhttp://<IP of SigNoz Backend>:55681/v1/traceā€ LS_SERVICE_NAME=<service name> node server_init.js
LS_SERVICE_NAME=<service name>
what will be the service name here?
OTEL_EXPORTER_OTLP_SPAN_ENDPOINT=ā€œhttp://localhost:55681/v1/traceā€ LS_SERVICE_NAME=node-telemetry node server_init.js
tried with something like above. didnā€™t work tho
@User
a
what will be the service name here?
service name can be anything
tried with something like above. didnā€™t work tho
Is SigNoz up and running with demo services?
@User
a
Anweshs-MacBook-Air:signoz-telemetry anweshnayak$ OTEL_EXPORTER_OTLP_SPAN_ENDPOINT=ā€œhttp://localhost:55681/v1/traceā€ LS_SERVICE_NAME=node-telemetry node server_init.js
collector exporter failed to create http agent. err: Invalid URL: ā€œhttp://localhost:55681/v1/traceā€
@User yes. signoz iz up with demo services. UI is accessible as well
maybe the endpoint here .
OTEL_EXPORTER_OTLP_SPAN_ENDPOINT=ā€œhttp://localhost:55681/v1/traceā€
is this correct?
is this correct?
Yes, it's correct if localhost:8888 is accessible
If you are using Maac, you can also try using
<http://docker.for.mac.localhost:55681/v1/trace>
and see if this works.
a
OTEL_EXPORTER_OTLP_SPAN_ENDPOINT=ā€œhttp://localhost:55681/v1/traceā€
this issue was with the double quote format which I copied from the docs. It was giving error. so edited it to the mac style.
OTEL_EXPORTER_OTLP_SPAN_ENDPOINT=ā€œhttp://localhost:55681/v1/traceā€ LS_SERVICE_NAME=node-telemetry node server_init.js
now the command has no errors
a
oh...interesting
let me know if you able to see the data from nodejs app
a
I checked the docs for open-telemetry. https://github.com/lightstep/otel-launcher-node I am not able to see any data though šŸ˜
I think that OTEL command should open up a launcher or something? not sure.
a
Let me also check with a sample service...
I am able to send data using the steps
did you hit any request to the application so that the library generates data?
a
http://localhost:9000/hello
as mentioned in server_init.js
sdk.start().then(() => {
require(ā€˜./serverā€™);
});
I am not able to hit that endpoint. http://localhost:9000/hello
Copy code
404 page not found
a
is it? I am sending my repo after adding a readme
a
yes. cool. let me know šŸ™‚
a
check this out
a
this is working. thanks
OTEL_EXPORTER_OTLP_SPAN_ENDPOINT=ā€œhttp://docker.for.mac.localhost:55681/v1/traceā€ LS_SERVICE_NAME=node-telemetry node server_init.js
PluginLoader#load: trying to load http@14.7.0
PluginLoader#load: trying to load express@4.17.1
{ā€œstackā€ā€œError getaddrinfo ENOTFOUND docker.for.mac.localhost\nĀ Ā at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js6626)\nĀ Ā at GetAddrInfoReqWrap.callbackTrampoline (internal/async_hooks.js12914)ā€œ,ā€messageā€:ā€œgetaddrinfo ENOTFOUND docker.for.mac.localhostā€,ā€œerrnoā€ā€œ 3008ā€,ā€œcodeā€ā€œENOTFOUNDā€,ā€œsyscallā€ā€œgetaddrinfoā€,ā€œhostnameā€ā€œdocker.for.mac.localhostā€,ā€œnameā€:ā€œErrorā€}
tried with
OTEL_EXPORTER_OTLP_SPAN_ENDPOINT=ā€œhttp://docker.for.mac.localhost:55681/v1/traceā€
and
OTEL_EXPORTER_OTLP_SPAN_ENDPOINT=ā€œhttp://localhost:55681/v1/traceā€
im checking though. docker localhost. issue must be lying around there
https://github.com/SigNoz/signoz/blob/main/deploy/docker/docker-compose.yaml#L213 otel collector service is not coming up I guess. I checked in docker console for mac. otel container is not there at all. checked with the latest pull here. from master.
a
oh...
sudo docker ps | wc -l
this should give you 15 as output
@User Is this working now?
a
16:19 $ sudo docker ps | wc -l Password: Ā Ā Ā 15 @User
a
flattener-processor
and
otel-collector
are not running
Can you send me screenshot of Docker Desktop -> Preferences -> Resources?
a
should I increase memory?
a
Yes keep it 4-5GB for now to get it up correctly
reinstall signoz by
docker-compose -f docker/docker-compose-tiny.yaml down -v
./install.sh
a
still those two services are not coming. I increased memory to 4.75GB
++++++++++++++++++ SUCCESS ++++++++++++++++++++++ Your installation is complete! Your frontend is running on ā€˜http://localhost:3000ā€™. +++++++++++++++++++++++++++++++++++++++++++++++++
it got up now. I think increasing memory helped
btw arenā€™t those services open sourced yet? just curios to explore
a
šŸŽ‰ šŸ™Œ
arenā€™t those services open sourced yet?
which services? We use everything opensourced
a
flatten-processor
I think its inside pkg/processors/flattener
yes
a
thanks šŸ™‚ will try to understand those services. https://signoz.io/docs/architecture . I got some idea from here. and intro section is šŸ’Æ .
a
šŸ‘
Hi @User, I have pinned some of the areas in need of contribution. Is there anything that you would be interested there? Or feel free to suggest something of your own šŸ™‚
a
hey @User I saw that list. currently I was picking up GO. as I have less expertise. I think post that I can pick something. let me try one tomorrow.
šŸ‘ 2
p
Awesome @User just drop a note here if a you have a question or get stuck anywhere
a
A good way to learn Golang would be to go through the codebase of openTelemetry-collector once you are done with the basics. There you will learn about Factories, Interfaces and Implementations
a
thanks will surely check out today. šŸ™‚