Hi @User, I think your kubectl is not properly setup. The above issues seem relevant. 1. Did you run any previous project using kubectl? This does not seem to be SigNoz installation problem. Try getting a hello world k8s pod/deployment working first 2. Are you using docker-desktop or minikube?

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

@User Which type of backend work are you comfortable with? A few options I can think of: • Frontend bugs and features • Writing test cases • Development in Golang -> add more features • Adding support for anything that you feel is missing • Adding CI • Different cluster configs to test scalability of system • Refactor to support more queuing systems like AWS SQS, Kinesis, Redis • Add more deployment options to Heroku/Fargate + CloudFormation templates and more, Let me know which kind of work you would be most interested in? Would be happy to dig deeper.

You don't to install docker and all the other components of SigNoz to develop frontend. Follow the below steps for a much simpler process. We have hosted SigNoz on an ec2 instance and exposed the URL of the query-service which is the only thing that frontend needs to work. Steps for Frontend Contribution 1.

git clone <https://github.com/SigNoz/signoz.git> && cd signoz/frontend

2. change baseURL to

<http://ec2-18-191-251-86.us-east-2.compute.amazonaws.com:8080>

in file

src/constants/env.ts

3. yarn install 4. yarn dev UI should show up at http://localhost:3000

@User Is working on support for clickhouse - which should make it lighter

https://github.com/SigNoz/sample-golang-app I was checking the codebase here. anyway to see the emitted traces from here to signoz flattner-processor? 🤔

Congrats @User. You are now officially a contributor to SigNoz 🎉

Jaeger UI Traces vs Signoz Traces. Signoz UI is using flamegraph, but the spans are little confusing, also it is stacking up from left to right. So some spans are getting tightly accumulated towards the end, some not coming in screen either. Whereas as compared to Jaeger UI. It stacks up using a top to down approach. and the root end spans are visible.

Hi! I have added CI pipeline using github workflow for query-service, frontend and flattener. PTAL- https://github.com/SigNoz/signoz/pull/173 cc: @User @User

@User It's probable Kafka logs... I will drill down deeper very soon

Hey folks, hope you guys had a good experience working with and contributing to SigNoz. Thanks for your active participation I was thinking of doing a monthly community call for the project.. where we can discuss the project and highlight roadmap and work done by contributors and also take feedback on how we can make things better from a contribution perspective Would this be relevant? Would you be interested in attending such a zoom meeting What days and times will be most convenient? Please mention in comments

Opened the issue., https://github.com/SigNoz/signoz/issues/181 @User will raise a PR soon.

Hi @User @User I created an issue for ARM support of signoz components. Can I work on this issue? https://github.com/SigNoz/signoz/issues/194?

@User can you add me to the repo or I need to clone then open a PR which is they way to follow?

https://github.com/SigNoz/signoz/pull/199 @User @User opened the PR.

Is there any plans to bring https://gitlab.com/signoz-public/ packages to Github? Could not found any issue on Github which has mentioned this. It will help to reduce the dependency sprawl. Happy to file issue, if that helps.

Can someone review the pr

Hi Everyone, first of all thanks to the SigNoz team for building a great tool and creating a space for developers to contribute to the open source. I can contribute to the frontend part of the tool and trying to setup in my local. I’m following

### Contribute to Frontend without installing SigNoz backend

- this section from

contributing.md

- this doc. Can someone pls dm me

<test environment URL>

- this url?

@User Your PR ( https://github.com/SigNoz/signoz/pull/202 ) is merged now 🙂 You are now a contributor 🎉

Hi All, Shared few ideas here for improvements https://github.com/SigNoz/signoz/discussions/207

Hey folks, is someone fixing the theme switcher button position, maybe placing it just above sidenav collapse button and center align will look better

Hi, Can someone assign me https://github.com/SigNoz/signoz/issues/200. I am happy to take that on unless someone is working on it.

Hi @User, Can you review this PR- https://github.com/SigNoz/signoz/pull/243? Changes:

Removing unused frontend and backend pkgs

Adding checks for unused pkg and code format of backend and frontend

I see it. Yup, the size is increasing slowly. Running for 9hours. Storage used by

druid-kafka-setup_kafka_1

moved from 1.32 to 1.62. Would be logs. I'm gonna keep it running for 3 days(retention period) and see. Locally as of now but if you have a spare VM, maybe I could use it.

https://github.com/open-telemetry/wg-ebpf Hope to see something here soon. Post which it would easy to add ebpf tracing

@User You might want to look into https://github.com/SigNoz/signoz/actions/workflows/codeql.yaml

Hello Everyone, My name is Nipun Agarwal and I am currently working as a SDE @Browserstack. I have worked as an SRE previously @CRED and I must say the problem that you guys are trying to solve is very interesting. I love contributing to open-source and primarily interested in backend projects. Looking forward to having a good time here. Setting up the project locally to get started 🙂

@User should have lots of interesting problems for you to work on 🙂

@User Can you look into an issue? build-and-push-query-service is failing. A couple of changes that were done: 1.

CGO_ENABLED=1

here 2. Build command was changed here The error might be a syntax mistake due to use of quotes

""

. Though I mostly suspect this to be due to makefile as the command to build docker image work fine when run via command line. Let me know if you got some bandwidth in the next few days