perf-tools VS zipkin

For execsnoop, people running systems with DTrace can find the same:

* https://github.com/jorgev/dtrace-scripts/blob/master/execsno...

On macOS Monterey+ you'll probably have to install the Kernel Debug Kit per:

* https://developer.apple.com/forums/thread/692444

The Linux variant was written Brendan Gregg (who previous did a lot of work on Solaris, where DTrace was created):

* https://github.com/brendangregg/perf-tools/blob/master/execs...

by https://github.com/brendangregg/perf-tools

It's not a library you can use but you might be able to take inspiration from something like opensnoop.

There are several tools that might go by the name 'perf', are you talking about this one? https://github.com/brendangregg/perf-tools

I have an application and I'd like to measure its page cache hit/miss numbers. I found this tool called cachestat by Brendan Gregg, which uses the ftrace tool to count the number of 4 specific functions (mark_page_accessed(), mark_buffer_dirty(), add_to_page_cache_lru(), and account_page_dirtied()) to find out the total number of page cache accesses and page cache misses. Detailed information can be found here, but basically, total number of page cache accesses and page cache misses can be calculated as below:

Program(Process) Tracing (ptrace) Tools: Establishes tracing operation during the execution of the application. Contains the traces of the index of instructions executed and the data referenced during execution. These are greatly used by developers for debugging purposes. Some examples of ptrace tools are, Strace, Ltrace, Opensnoop, and Valgrind Lackey.

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.