<!channel> 👋 This is for all our active open source users. We are planning a 2-week sprint prioritising all issues related to the community edition of SigNoz. We especially want to focus on issues related to ease of running and maintaining open source SigNoz at scale. Please help us identify and prioritize issues based on your experience of using SigNoz. Here's how you can help us: • Create github issues and mark with the label

community feedback

. Please explain your issue in detail and provide error message or screenshots if applicable • Reply on this thread with your feedback if you don't want to create an issue • If you are running SigNoz at serious scale, please book a quick zoom call with our devrel @Nagesh Bansal and share your experience. Here's the calendly link. We're excited to take this up and take OSS SigNoz experience to the next level. Let's make SigNoz the best open source observavility tool out there, appreciate all kinds of feedback. ❤️

Here are a few things we’re especially curious about: • Have you run into any issues or rough edges while using SigNoz? • How’s the maintenance experience been over time? • Are there parts of the setup or usage that feel more complex than they should? • How well is SigNoz scaling with your current workloads? • Anything you feel is missing or that could be better?

• Ability to pin legends to right/left instead of bottom of graphs • Option to define colours of graphs to make them more visible (auto generated colours are something hard to see)

Security is lacking for k8s deployment, it will be great if we can add some focus here • network policies for all signoz pods • pod security admissions ◦ currently we can edit these, but volumes are not exposed, so there is not much choice to add proper security context in some cases • proper secret management for signoz helm deployment

The possiblity to create API keys to manage dashboards/alerts with Terraform in self-hosted edition

I'd like to take this opportunity to pass on some feedback on what might be missing from Signoz after using it and discussing with many teams 👀 In terms of deploying Signoz (using the helm chart) we encountered several frustrations: • No possibility to create the first admin (at least) within the chart • Edit retention periods for each signal within the chart • Maintaining dashboards as infra resources (I saw you started adding dashboards to the terraform provider so maybe this is on the way 🥳) We feel that these features are mandatory to operate Signoz in a mature gitops infrastructure. In terms of functionality, Signoz is getting better and better so thank you guys 🙌 However, we feel that it lacks some essential features: • No possibility to affect user permissions on specific resources (restricting access of some services/dashboards to a limited group of users) • Monitor data ingestion precisely to understand sources of costs and/or latency (which will be highly covered by the new metrics explorer I guess) Those 2 points are the biggest things that stop teams from trying Signoz in bigger structures in our opinion. Some "nice to have" I thought about: • Better customization of graphs legends and colors for better visibility. • Be able to attach external resources to some attributes. For example, when exploring a Temporal workflow trace, I would love to be able to click on the "worlfowId" span attribute to be redirected on my temporal admin dashboard containing this workflow. • Generating some view-only dashboard links that can be accessible without authentication to easily send specific views to partners. When speaking with interested actors, we often end up discussing about the workload Signoz can handle so I think the documentation would benefit of a more precise load test resource to help people better understand and plan the scalability they'll need depending on their ingestion volume 🤔

Thank you to the SigNoz team for their hard work as always. 🙇‍♂️ There are a few things I would like to see improved or added. 1. Color differentiation for external communication in the Root Span of Traces - Color differentiation by item instead of the same color in the bar form by dividing into App Code, Database Calls, and External Calls, and change it to a non-leaf icon (e.g. Database Icon) 2. Infra Monitoring at that time in the Root Span of Traces - Add metrics so that you can see the Infra situation at that time on one screen when there was a delay in Traces (a big reason to use observability) - Same in Message Queue, API Monitoring, and Exception. 3. Inability to sort List View items or Traces items in the Traces menu 4. Function to filter by service_name in Service Map 5. When using the light theme, when you mouse over the graph in the Service menu, the sub-window appears in black, and the text color there seems to be a specific fluorescent color that makes it difficult to read. It seems like it should be processed in Bold or a different color. 6. It would be nice if the Metrics menu could change the Proportion View to Line instead of Heat Map, or optionally change it. The Metrics menu is too hard to see. 7. When displaying graphs in various menus, it would be nice to also be able to show what the graph looked like the day before. 8. Customizing Home Menu 9. SSO is a paid plan, but supports LDAP 10. Support for embedding the signoz dashboard elsewhere(ex: External Metrics in Services Manu)

Couldn't find how to add labels but had some pre-existing issues open here - Regarding Dashboards and here inside the same issue - regarding duplicates want to make sure these aren't forgotten

Hello 🙂 I hope this issue will be taken in consideration for this sprint: https://github.com/SigNoz/signoz/issues/7388 (Docker Images: add tag to track latest stable release #7388)