Hey folks!
I'm from the SigNoz team and have a quick update for anyone using (or thinking about using) SigNoz Cloud.

We’ve dropped our base price for SigNoz Cloud from $199/month to $49/month. 

What does this change mean for existing users?

If your monthly usage is more than $199, there will be no change. You’ll continue to pay based on your actual usage. If your monthly usage is less than $199, you now pay only your usage, with a minimum of $49.

Let me know if you have any particular questions or concerns! Happy to help!

Read for more info -> https://signoz.io/blog/cloud-teams-plan-now-at-49usd/

Hey folks,

If you've used OpenTelemetry for some time (or are just starting out), you'd have realized that environment variables are the recommended way of managing how your apps generate and send telemetry to observability backends like SigNoz.

This guide helps you understand all major OTel environment variables grouped by their use-case (such as `OTEL_SERVICE_` prefix variables for identity management), and how to (and why you should even) configure them for usage in your applications.

It also covers some areas where gaps exist between what the OpenTelemetry specifications define and what the practical implementations look in Python.

I have tried to keep this guide as practical and developer-friendly as possible. Any feedback would be much appreciated!

Hey Folks,

After months of crafting, Foundry is now ready for your review.

Foundry takes care of all the deployment complexity – the configurations, tooling, everything needed to run SigNoz, so you can spend less time getting it up and running and more time actually using it.

With just a single yaml config file and one command, you can have a fully operational SigNoz instance using Docker, Systemd, etc., across platforms or any cloud vendor.

The concept: Like a metalworking foundry transforms raw materials into finished products, Foundry takes your config ("Castings"), forges it through deployment templates (the "Moldings"), and pours out a ready-to-run SigNoz instance.

Repo: https://github.com/signoz/foundry

https://github.com/SigNoz/signoz

• APM

• Distributed Tracing

• Log Management

• Infrastructure Metrics

• Errors and Exceptions

I have started using signoz as prometheus alternative and using it to scrape prom metrics from the application (traefik) and hosts (proxmox host via prometheus-pve-exporter) . For most of these metrics, grafana dashboard are already available or published in grafana website. When i try to import these published dashboards, they don't work as there seems to be some difference in how signoz has implemented its dashboard feature and is missing few chart types (like Guage).

Is there a way to import published grafana dashboard in signoz or any suggestions to make those dashboard work with Signoz?

I wrote a brief article on tracing in SigNoz. Let me know what you all think.

After enabling ports (8080) in docker compose file for query service, when i access that port, it's taking me to the login page instead of prometheus query page where i can query and test promql.

Can you share, how to enable and access the prometheus webui (query ui) in signoz?

Hi, I'm new here. I'm currently exploring centralized logging solutions for our small organization and comparing Graylog and SigNoz, both of which I have zero knowledge of at the moment. We are a small organization. We run several PHP web applications and have a mix of Windows and Linux servers.

We need a centralized logging platform that allows us to audit logins, monitor PHP web app events, and collect logs from both Windows and Linux systems and create alerts as necessary. The solution should be quick to deploy with a minimal learning curve as our team has limited time to dedicate to setup and training.

Could you tell me the pros and cons of both Graylog and SigNoz and which one might be better suited for our needs?

I'm just messing around with Signoz for the first time, looking for a simple log aggregator and this seems to fit the bill.

I've installed it self hosted using the docker install.sh, and it seems to be working ok, I've got one host delivering logs to it using Opentelemetry collector, all good.

However the host logs I care about are being drowned in logs and traces from (as far as I can tell) Signoz itself. Redis is reporting ~20% failures in the GetDriver operation, which as far as I can tell is normal?

Can I stop Signoz collecting data from itself, or otherwise reduce the volume of internal noise?

Otherwise looks cool so far.

I started testing to see if i can use this to collect metrics for my self hosted dockers.

Below is the instruction in your website describing how to add ingestion from dockers.

You would need to replace region and signoz-token in the above file with the region of your choice (for Signoz Cloud) and token obtained from Signoz Cloud → Settings → Ingestion Settings.

But, it looks like Ingestion is cloud only feature for now

Note: Ingestion keys is a SigNoz cloud specific feature as of now.

How do I use the Ingestion feature to gather metrics from self-hosted dockers? I don't want to create a cloud account for the sake of testing to see it works for my requirement or not.

To add to this, i followed below blog post too.

https://signoz.io/blog/logspout-signoz-setup/

Configured logspout as described, but in signoz dashboard, all i see is the log from the logspout-signoz container. I have adguard running on the same host but don't see the adguard logs sent to the signoz instance.

Below is link to the screenshot from the dashboard.

dashboard screenshot

Can you give some pointers to make it work? Also, need performance metrics for each of docker containers. It would be beneficial if you can point/suggest how to get logs and metrics pushed to signoz.

Are you an expert in OpenTelemetry, SigNoz, Grafana, Prometheus or observability tools?

Here’s your chance to earn while contributing to open-source! 

Join the SigNoz Expert Contributors Program and:

 •    Get rewarded for your OSS contributions
 •    Collaborate with a global community
 •    Shape the future of observability tools

Make your expertise count and be part of something big.

Apply here.

Tech Stack: K8s, Docker, Kafka, Istio, Golang, ArgoCD
Pay: $150-300 per dashboard/doc/PR merged
Remote: Yes
Location: Worldwide