Hi Team, I haven't received any feedback on this PR for a couple of days, if anyone is free then please reply to the comments that I have added. https://github.com/SigNoz/signoz/pull/1414

@Palash Gupta have added a query here, in this PR. Please take a look if you get some time. https://github.com/SigNoz/signoz/pull/1426#discussion_r928296415

@Ankit Nayan here created this issue as a successor of Issue 1353 https://github.com/SigNoz/signoz/issues/1464 Please assign it to me.

Pushed a PR that makes the NestJS example work well with NestJS's ES imports: https://github.com/SigNoz/sample-NestJs-app/pull/3

Hey 👋, just found out that Signoz has preview support for logs now - one step closer to a unified observability solution! I drove some projects in observability and developer experience in my past companies, so looking forward to contribute to signoz.

Created a PR to allow running SigNoz from source without editing / creating any files. Now contributors just need to do

run-local

/

down-local

for their changes. Please review: https://github.com/SigNoz/signoz/pull/1528

It took me 40 minutes to setup SigNoz and run it from source, but with this - should be no more than a minute. 👆

This should also solve the issue here: https://signoz-community.slack.com/archives/C01LWQ8KS7M/p1660463653270139

Does SigNoz have support for dogfooding all the it's internal signals on SigNoz? I think this would be a great way to identify gaps in existing implementation and how the product works for end-users.

Hello all, I am looking forward to contributing. I am a frontend web engineer. can someone share the test environment URL and what are the other rules of the road to get started?

Hello Everyone, I am a frontend web engineer, I want to contribute, can anyone guide me on how to start, I am new to open source.

This might be helpful : https://github.com/SigNoz/signoz/blob/develop/CONTRIBUTING.md

Looking forward to seeing this feature implemented! Search by plain text #1397

Hello folks, I would like to contribute to this project, currently I am setting up the environment for frontend. Can I get the

test-environment-url

?

Hello folks, I had a few ideas that I wanted to share with the team to see if this discussion can be taken forward. One of it was around having a contributor roadmap for the first time contributors. The high level idea being https://aviyel.com/post/3369. However, I noticed that a detailed roadmap is already in place. The alternate idea that I wanted to share was around an informal AMA session with our open source community. We would love to host somebody from the project on our platform where you can talk about the upcoming features or any recent release to get more eyes on it and take direct feedback from the community. Sharing a link below for your reference: We are working on a few more ideas that might help in tracking the engagement of the community folks with the project. Would be great if we can get on a call to discuss this further.🚀

Hey everyone, I actually came here after seeing SigNoz on Hacker News! My background is in backend and database development. Stack is C#, Python, Go, and SQL. Excited to start contributing!

Hello

@Prashant Shahi

, I want to make a FE contribution on an issue, in order to do that I need

<test environment URL>

to access the frontend. Can you please dm me the same?

👋 Hello, team!

i need test environment URL please

Hello guys, I'm Rohith a final year student from Bengaluru who loves contributing to open source. Here's my Linkedin. I come here in search of knowledge to help me grow and make contributions. 😄

Hi everyone, I’m a software engineer at Postman living in Gujarat, India. I just found out about you guys from an email thread. I’m looking at the codebase and willing to contribute to front-end in the beginning and then more on to backend too

Hi there 👋 , can I get <test environment URL> for contributing in frontend

hi there, I am setting up the environment for Backend from the guidance when I tried to run

ClickHouseUrl=<tcp://localhost:9001> STORAGE=clickhouse build/query-service

to test on local, I got this error:

clickhouseReader/reader.go:114	failed to initialize ClickHouse: error connecting to primary db: dial tcp 127.0.0.1:9001: connect: connection refused

do I need to install clickhouse locally?

Hello, doc contribution. Alerting for versions that redis auto instrumentation for nodejs - Ioredis works. Supported Versions •

>=2.0.0 <5

https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-ioredis#supported-versions So in this doc maybe have appointment or write who versions are supported by auto instrumentation can help others, because on testing you commonly just use last version. https://signoz.io/docs/instrumentation/express/#redis-instrumentation Thanks

Setting up Backend local development: Hello, quick question--why should query-service be commented out in the YAML manifest? Is it because I’m later supposed to manually pull the latest docker images of query-services?

hello myself nishant mishra here an aspiring devops engineer !

I want to contribute to backend

where do I begin?

Hi Together, i’m new with signoz i install it on a server with docker compose. and in the Front i have a Proxy server with nginx now i have the Pronblem that i don’t get the port 4318 if i call it over domain

any idea?