stanza VS zipkin

Been a while since I looked into fluentd and elasticsearch but I heard Stanza (soon to be moved to the OpenTelemetry Collector) is meant to be a modern replacement for it, but seems it's still in it's early days.

And then they contacted some famous log collection projects such as the Fluent Bit and also others like Stanza as well as Syslog, I guess. And I didn't read the whole thread of the conversation around log collection. But now, they set the Stanza as the first implementation of OpenTelemetry logs. And in Stanza, the observIQ with Stanza is merged under the OpenTelemetry log repository, so that's the status. And then, they try to standardize the format of logs based on the Stanza format, such as what kind of information should be included in log.

observIQ is a hosted log management platform that's powered by our FOSS log agent, Stanza: https://github.com/observIQ/stanza. Stanza is lightweight and robust (written in Go), and can be configured to act as a Syslog receiver in about a minute (guided configuration in our app).

observIQ is a simple, cost-effective hosted log management platform designed with small teams in-mind. Log collection is powered by Stanza: https://github.com/observIQ/stanza , our high-performance OSS log agent. Stanza was also recently adopted as the official log agent of the CNCF's OpenTelemetry project. observIQ offers guided-installation, pre-made dashboards, threshold-based alerts, live tail and more.

We're a new hosted log management platform with simple, native support for gathering logs from Openshift. Deployment typically takes a few minutes. We also automatically enrich Openshift logs metadata like node, namespace, pod, container - no additional configuration required. Logs are gathered with your high-performance OSS log agent, Stanza: https://github.com/observIQ/stanza

We offer a super simple, hosted log management platform that allows you to easily ingest any syslog traffic by setting up high-speed OSS agent as a syslog receiver in just a few click (setup takes about 30 seconds). You can find more about our log agent here: https://github.com/observIQ/stanza

Self-promotion alert, my apologies: Check us out at observIQ: https://observiq.com/ We provide a super-simple host log management platform powered our high-performance OSS Log Agent, Stanza (https://github.com/observIQ/stanza). Average setup time is about 5 minutes, end-to-end. Our platform is designed with start-ups and small businesses in-mind and are priced about half as much as our competitors. Lastly, we offer 14-day free trial, but also offer a completely free plan that provides 3 gigs of ingestion/day and 3 day retention - with access to the full feature set of the platform (Dashboards, Alerts, Live Tail). Shoot me a message or chat if you have any questions!

Similarly, our platform will be rolling out this feature soon, and will utilize our lightweight FOSS log agent Stanza - written in Go. The agent may work for your project https://github.com/observIQ/stanza

When choosing distributed tracing tools, considerations include your technology stack, business requirements, and monitoring complexity. Zipkin, SkyWalking, and OpenTelemetry are popular distributed tracing solutions, each with its unique features.

From the perspective of the realization of GraphQL infrastructure, the interesting direction is "Finding". How to find the problem? How to find the bottleneck of the system? Distributed Tracing System (DTS) will help answer this question. Distributed tracing is a method of observing requests as they propagate through distributed environments. In our scenario, we have dozens of subgraphs, gateway, and transport layer through which the request goes. We have several tools that can be used to detect the whole lifecycle of the request through the system, e.g. Jaeger, Zipkin or solutions that provided DTS as a part of the solution NewRelic.

Zipkin is a distributed tracing system used for tracking and analyzing how requests move through complex systems, especially in setups with many interconnected services, known as microservices.

Distributed Tracing: Middleware for distributed tracing like Jaeger and Zipkin helps monitor and trace requests as they flow through multiple microservices, aiding in debugging, performance optimization, and understanding the system's behavior.

For microservice tracing, you might want to look at Zipkin [0], or OpenTelemetry [1]

[0] https://zipkin.io/

I’ve not used a self-hosted solution before, but here’s one I found. https://zipkin.io/

> IMO the reason these vendors can and do charge so much is not because telemetry software is hard.

I always saw it as "they are charging for their polished UI/experience"

The UI of https://zipkin.io/ versus DataDog is kind of... not really in the same ballpark?

There are the zipkin https://zipkin.io/ and jaeger https://www.jaegertracing.io/ packages/components you can use both have quickstarts if you consider that to be a beginner's guide.

Zipkin, which was developed by Twitter, is an open source tool for distributed tracing that can also be used to troubleshoot latency issues in your application. While Zipkin is Java-based, py_zipkin is an implementation for Python.