Hey folks! We just dropped a fresh blog on the basics of OpenTelemetry: a go-to guide for anyone starting their observability journey. It covers: • What is OpenTelemetry (OTel) • What OTel is not • OpenTelemetry Specifications & why they matter • How OTel works under the hood • Why it's gaining massive adoption • Whether you're new to observability or just tired of fragmented tooling, this guide will help you understand the "why" and "how" of OTel. 👉 Give it a read: https://signoz.io/blog/what-is-opentelemetry/ Perfect for beginners, curious engineers, or teams considering standardising on OTel!

<!here> 👋 We made a fun wordle game to help you learn terms in DevOps, observability and monitoring. There will be a 5 letter word and you have 5 guesses. Score is based on the time taken to crack it. How fast can you crack it? Play and challenge your friends. 🥳 I just played and got a score of 5334 in 0:27 minutes. Can you beat me 😉? Here's my game: 🟥🟥🟨🟨🟥 🟦🟥🟥🟨🟨 🟦🟦🟦🟦🟦 Try it out at https://signoz.io/todaysdevopswordle.

Helloo! Read my latest blog on how you can use OpenTelemetry to observe your kafka systems and get deep insights. Kafka has become almost a staple in all our systems, but its asynchronous nature makes it notoriously hard to monitor. If this sounds like a pain-point you’ve come across, this will be worth a read! https://signoz.io/blog/shedding-light-on-kafkas-black-box-problem/ If you have any interesting ways of observing your kafka systems today! Do share :))

<!here> 👋 Big News for our open source users - our open source community edition is now available with SSO (Google OAuth) and API keys 🚀 For a long time, the ask for these features in our Community Edition has been persistent. We've been listening, and we're incredibly proud to deliver on these requests, empowering more users to experience a seamless, secure, and integrated observability experience with SigNoz. With SSO, our open source users will be able to streamline the login process and also enhance security by centralising authentication. We're currently enabling this for Google OAuth, with plans to support additional OAuth providers soon. With API keys now accessible in our open source version, you will be able to programmatically: - Create and Manage Alerts - Create Scheduled Downtimes - Manage Dashboards/Alerts with Terraform This opens up scope for building powerful observability workflows based on your specific needs. These new additions to our open source version deliver on our promise of democratising observability for all 💪 Looking forward to any feedback and comments 🙌 🚨* Release notes* 🔊 Announcement Post

Folks, if we ship something like this where you can see all the logs/traces/metrics from the timestamp when your alerts were fired, would that be a good quality of life improvement or more of a meh, just a good-to-have thing?

<!here> 👋 I’m excited to share a big update with you all! Starting today, SigNoz Cloud is available from $49/month (previously $199), with all the features intact to support your observability needs: unified logs, metrics, traces, and more. 🥳 (SigNoz pricing) We know many of you run SigNoz self-hosted and contribute to our open-source project. But for those who want the convenience of a fully managed experience, we hope this new pricing makes it even easier to access powerful observability without any operational overhead. More details: https://signoz.io/blog/cloud-teams-plan-now-at-49usd/ Thank you for being a part of our journey ❤️ Onwards 🚀

🚨 We are live now with Day 5 sesh, concluding the Launch Week 4.0! Come see how SigNoz brings product analytics-style funnels to observability, an industry first. • Build funnels between any spans in your distributed traces • Instantly measure conversion, drop-offs, and latency across backend flows • Get actionable insights to debug and optimize complex systems All in classic SigNoz fashion- one platform, powered by OpenTelemetry. Join us here: LinkedIn Event

<!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. ❤️

This signoz image is being used in signoz statefull-set in k8 as per the documentation docker.io/signoz/signoz:v0.82.1, The is no inforation in the documentation or anywhere in the internet that How i can build this image using this git repo "git clone -b v0.82.1 https://github.com/SigNoz/signoz.git" I have tried multiple ways but no luck Example: git clone -b v0.82.1 https://github.com/SigNoz/signoz.git cd signoz/frontend yarn install yarn build # Build Docker image docker build -t your-repo/signoz-frontend:custom -f Dockerfile . docker push your-repo/signoz-frontend:custom Need guidance here i can build the signoz image which can run after i replace in this container : containers: - name: signoz image: docker.io/signoz/signoz:v0.82.1 args: - '--cluster' - $(CLICKHOUSE_CLUSTER) ports: - name: http containerPort: 8080 protocol: TCP - name: http-internal containerPort: 8085 protocol: TCP - name: opamp-internal containerPort: 4320 protocol: TCP env: - name: CLICKHOUSE_HOST value: signoz-clickhouse - name: CLICKHOUSE_PORT value: '9000' - name: CLICKHOUSE_HTTP_PORT value: '8123' - name: CLICKHOUSE_CLUSTER value: cluster - name: CLICKHOUSE_USER value: admin - name: CLICKHOUSE_PASSWORD value: 27ff0399-0d3a-4bd8-919d-17c2181e6fb9 - name: CLICKHOUSE_SECURE value: 'false' - name: STORAGE value: clickhouse - name: ClickHouseUrl value: >- tcp://signoz-clickhouse:9000/?username=admin&amp;password=27ff0399-0d3a-4bd8-919d-17c2181e6fb9 - name: GODEBUG value: netdns=go - name: TELEMETRY_ENABLED value: 'true' - name: DEPLOYMENT_TYPE value: kubernetes-helm - name: SIGNOZ_ALERTMANAGER_PROVIDER value: signoz resources: requests: cpu: 100m memory: 100Mi

HI

🚀 We are live now! Come see how SigNoz’s new CI/CD Observability Dashboard gives you real-time visibility into your entire software delivery pipeline. Instantly monitor build durations, test pass rates, deployment frequency, DORA metrics, and spot flaky tests or bottlenecks. All in classic SigNoz's way - one dashboard, powered by OpenTelemetry. Join us here: LinkedIn Event

Hey guys, collector is responding with

405 Method Not Allowed

when the browser sends OPTIONS preflight requests. how can i fix this?

Hola a todos, espero se encuentren bien, me ayudan por favor con lo siguiente, recientemente tengo signoz localmente desplegado en docker, estoy tratando de configurar el SMTP, monte las variables a mi .yaml, aplicamos estas configuraciones adicionales pero sigue sin funcionar. unknown send STARTTLS command: tls: failed to verify certificate: x509: cannot validate certificate for 172.18.115.54 because it doesn't contain any IP SANs SIGNOZ_ALERTMANAGER_SIGNOZ_GLOBAL_SMTP__REQUIRE__TLS=falseSIGNOZ_ALERTMANAGER_SIGNOZ_GLOBAL_SMTP__TLS__INSECURE__SKIP__VERIFY=true

Launch Week Day 3: Third-Party API Monitoring is Live! 🚦 Yesterday was all about metrics. Today, we’re thrilled to launch something you’ve been asking for: real-time visibility into every third-party API your app depends on! Ever wondered: • “Is a vendor API slowing us down?” • “Which internal service is actually impacted?” • “How can I catch errors and latency from external calls instantly?” Now you can: • Track every external API call-errors, latency, and volumes-in one place. • Instantly see which service is affected when a vendor hiccups. • Troubleshoot faster, with zero guesswork. We’re demoing it live and answering all your questions-join us now: https://www.linkedin.com/events/thirdpartyapimonitoringpoweredb7325856959461576705/theater/ As always, drop your feedback and questions here or ping us directly!

Hey guys! WE are BACK with another blog! ❤️ This one would be useful if you are thinking of ways to optimise your OpenTelemetry Collector in an attempt to reduce noise and costs as well! We've covered some solid methods including, • Filtering of traces • Sampling - with an example of tail-based sampler • Dropping logs based on sev level • And our own ingestion guard If you guys are hooked take a look at this! If you would like a part two (mainly around what you can do at an SDK level) give us some reactions!

Hi, can someone please help here? Thanks

Traces + Aggregate Every—Why does changing aggregate every to less than 60 seconds not work? What if I need to see aggregate per second?

Launch Week Day 2: Metrics Explorer is Live! 🌟 Yesterday, we tackled deep temporal observability. Today we’re excited to roll out something many of you have asked for: Metrics Explorer. If you’ve ever wondered: • “What metrics are actually being sent to SigNoz?” • “Which ones are eating up my ingestion quota?” • “How do I quickly find, filter, and analyze metrics before building dashboards or alerts?” Metrics Explorer is built for you. You can now: • Instantly see all metrics being ingested-types, counts, cardinality, and labels-in one place. • Search, filter, and query metrics directly, without hunting through dashboards. • Spot high-cardinality or noisy metrics, optimize what you send, and build dashboards/alerts right from exploration. We are demoing how it works, how to use it to troubleshoot faster, and what’s coming next. Join the live session now: LinkedIn | As always, would love your feedback and questions-drop them here or ping us directly!

<!channel> 👋 🚀 SigNoz Launch Week 4.0 Day 1 is Live! Today we’re excited to roll out Deep Temporal Observability, a feature built from your requests for better visibility into Temporal workflows. If you’ve ever struggled to debug async workflows or wanted to jump straight from a workflow metric spike to the exact logs and traces for that execution, this is for you. With our new integration, you can: • Correlate metrics, logs, and traces for Temporal in one place • Break down workflow latency by type, activity, or task queue • Instantly pivot from metrics to traces or logs for root cause analysis • Set up smarter alerts and dashboards for workflow health and worker performance Join us as @Pranay and @Ankit Nayan discuss the feature live on below links: • LinkedIn • You can also read more about it here: https://signoz.io/blog/deep-temporal-observability/ Would love your feedback and questions. Let us know what you think or what you’d like to see next in this feature.

CloudWatch is good especially if you live entirely in the AWS ecosystem. But is it time to take a step back and ask if it is still enough for modern observability needs? Well, we did the homework for you. After digging through user reviews, benchmarks, pricing docs, and some hands-on testing, we’ve detailed 6 silent traps in CloudWatch that could be hurting your observability. 🚩 Here’s what we covered: • Metrics API limits • Log query concurrency bottlenecks • Cost unpredictability • Fragmented signals • Trace performance at high volume • User experience and dashboard friction We’ve compared CloudWatch head-to-head with modern observability platforms with data, not fluff, so you don’t have to! 📖 Read the blog here Also curious, anyone here who churned out of CloudWatch? 👀

Hi team, after upgrade signoz from 0.79.1 to 0.82.1, in Light theme, span visualization become very difficult to see in trace explorer. is this a bug?

Hi team, I am using a dashboard

Panel Type: Number

with

Unit: Percent (0.0-1.0)

with the

Formula: A/(A+B)

and the number value is pretty much always 100%. The following recent example displays as 100%: A/(A+B) where: A = 3996357 B = 434 3996357 / (3996357+434) = 0.999891413 Is it possible to display 99.98% ?

<!channel> 👋 5 days to go for SigNoz Launch Week 4.0 🚀 From May 12 - 16 (9:00 AM PDT), we will be going live with 5 new features recently shipped in SigNoz and the story behind them. On day 1, we go live with Deep Temporal Observability. 🙌 We’ve stitched together metrics, logs, and traces for Temporal workflows so you can jump from a workflow metric spike straight to the exact logs and traces for that run, and finally see how everything played out across your system. Other features planned for the launch week: • Metrics Explorer - Search, Query, and Analyze all your Metrics at one place • Third party API Monitoring using OpenTelemetry semantics • CI/CD Observability Powered by OpenTelemetry • Tracing Funnels - Define funnels b/w spans in your distributed system Would love to have you join us for our live sessions and interact with developers behind these features. Register: https://lu.ma/0jqni8b0 See you at Launch Week 4.0 ❤️

Awareness around using OpenTelemetry for infra monitoring is still surprisingly low. Most folks associate it with traces and application-level instrumentation. But today, OpenTelemetry makes it super easy to monitor Kubernetes clusters, nodes, and individual hosts. With receivers like

kubeletstats

,

kubernetes_cluster

, and

k8sobjects

, you can collect detailed metrics like pod resource usage, node health, and more directly from the Kubernetes API. 👉 No separate Prometheus setup needed. Just plug into the OTel pipeline. If you're already using OTel for traces, or just exploring better ways to observe your infra, we wrote a blog that covers: 1. How to monitor VMs, K8s clusters, and pods with OTel 2. Whether OTel is ready to replace traditional infra monitoring 3. How to switch from Prometheus to OpenTelemetry If you are hooked, check out our latest blog!🌤️

Any plans to bump k8s-infra helm chart to include a slightly newer version of the otelcol than version 0.109.0?

Are the services back? @Nagarajan

We are experiencing issues accessing the SigNoz login and registration pages when accessing the application via an NGINX Ingress setup. The UI loads partially or fails during login/register attempts. However, when accessing SigNoz via

kubectl port-forward

directly to the service, all functionality—including login and registration—works as expected. Environment Details: • Ingress Controller: NGINX • Load Balancer: AWS NLB (with TLS via cert-manager and external-dns) • Service Type: ClusterIP • SigNoz Version: v0.81.0 • Access Method That Works:

kubectl port-forward

• Access Method That Fails: Public URL via Ingress (e.g., https://signoz.test.com) Observed Logs: • Successful 200 responses for

/api/v1/hosts/list

,

/api/v1/loginPrecheck

• 501 error for

/api/v3/licenses/active

(

"not implemented"

) • 500 error for

/api/v1/user/{id}

(

"user not found"

) via Ingress This behavior suggests an issue with Ingress forwarding or session handling. Request: Could you please help identify what might be misconfigured in our Ingress setup or suggest changes needed to ensure login/register works correctly through NGINX Ingress? Happy to provide Ingress and service YAMLs if needed.

suggestion: https://github.com/SigNoz/signoz/releases is very technical and hard to understand, there are also very frequent releases. some blog posts that talk about the new features would be appreciated. I like how gitlab does that with monthly releases and blog posts about it (doesn't need to be that extensive obvously)

How do I find the version in github that is the latest stable version? I see a difference between release branches and tags. This is important as I will need to pull of the respective docker images into my company separately via a review process and I would like to get all of the respective images mentioned in a particular release signoz/deploy/docker/docker-compose.yaml

I have some questions regarding Signoz We are planning to procure a VM on which I will be installing Signoz. For that purpose I need some specifications: 1. What is the minimum hardware requirement for signoz to run 2. What type of application signoz is : memory based/ cpu based 3. What is the type of database that signoz uses and also is it RDBMS or non-RDBMS 4. Is the database standard edition or enterprise edition Thank you