@signoz, I’ve found your service to be quite disap...
# support
a
@signoz, I’ve found your service to be quite disappointing. I raised an issue "https://github.com/SigNoz/signoz/issues/8145" but never received any response from your team. Upon checking, I noticed that there are numerous open bugs that haven’t been addressed at all. This raises serious concerns and if someone gets stuck, and there’s no support, how can clients rely on your product? It seems like either the system is being deployed without proper testing or there’s no automation process in place, which is something that really should be there. For your information, I’ve managed to fix the issue on my own branch. My only request is that you work on improving your support and development processes. Please make sure that raised bugs are acknowledged and responded to, so users know someone is actively working on them. This would leave a much more positive impression on clients.
@Nagesh Bansal, I’m currently setting up SigNoz for Docker container and log monitoring, but I noticed a message stating that infra monitoring is not fully released yet. Because of this, I’m not able to see my container-level metrics or logs. Could you please confirm: 1. Has full infra monitoring (for Docker containers and related logs) been officially released? 2. If not, what steps should I follow to at least view container metrics and logs for now? This will help me proceed with the setup and also update my client accordingly. Please find the attached screenshots for your reference.
are you using community edition? @Asad K
or enterprise?
a
Community edition
a
Community edition is not a service - it's an open source project. If you need SLAs in issue resolution, please opt for the enterprise edition: https://signoz.io/pricing/
a
But why am I getting this message? And won't I get this in the community edition?
a
It's mentioned it's in active development. It's not released
a
I don't understand can you tell me about it in some details?
@Ashu
v
Hi @Asad K, Thanks for the feedback. I checked issue #8145 and see it was actually resolved with a patch release within a few hours of being reported. Sometimes quick fixes don't get explicit comments before closure, which can create confusion - we'll work on improving that communication. Our open source community version operates on a collaborative model where users contribute fixes and features through PRs. We appreciate that you found a solution - would you consider submitting it as a PR to help other users facing similar issues? For guaranteed response times and dedicated support, our Cloud and Enterprise plans include formal SLAs. The community version is maintained by volunteers and prioritized based on overall impact and available bandwidth. We're always working to improve our processes, and your feedback is noted. If you're interested in faster feature development for specific needs, we'd be happy to discuss our paid plans which include priority support and feature requests.
I don't understand can you tell me about it in some details?
Container/Process monitoring is still in development and would be available on all versions soon. Until then use dashboards and logs module to monitor containers https://signoz.io/docs/metrics-management/docker-container-metrics/ https://signoz.io/docs/userguide/collect_docker_logs/