mastouille.fr est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastouille est une instance Mastodon durable, ouverte, et hébergée en France.

Administré par :

Statistiques du serveur :

589
comptes actifs

#tracing

0 message0 participant0 message aujourd’hui

I've just committed a new manual page to #FreeBSD: tracing(7), an introduction to #tracing and #performance #monitoring facilities.

It'll take a moment before it is available for readers on man.freebsd.org, so for the time being you can grab a copy from here (cgit.freebsd.org/src/plain/sha) and open it with man(1).

cgit.freebsd.orgMaking sure you're not a bot!
#DTrace#dwatch#ktrace
Suite du fil

The email said their duties were "identified as either unnecessary or virtually identical to duties being performed elsewhere in the agency." But the #genetic #tracing that the #CDC's lab performs is not conducted by any lab in the #UnitedStates or the #world….

While it remains shuttered, ongoing investigations of current #hepatitis #outbreaks have been stalled, not just in #Florida, but also in #Oregon, #Pennsylvania, #Massachusetts, #NewMexico, #Wisconsin, #WestVirginia & #Georgia….

i'm trying to add #tracing (like the crate called tracing) to my current #rust project. i'm using tracing-forest to get nested output for my spans, and i want to get that into all my 200+ tests, but i don't want to add a new line to every test. a single global initializer before all tests run would be great, or else a per-test initializer would be fine. i've found some partial solutions, but nothing that lets me use tracing-forest in a layer. any ideas what I could do?

Trace All the Things! 🌟

Ever wondered how to simplify observability in your environment? Check out our latest blog post where we dive into OpenTelemetry and Jaeger integration! Learn how to seamlessly trace and monitor your applications for better insights and performance.

🔗 Read more: atix.de/en/blog/trace-all-the-

ATIX AG · Trace All the Things | ATIX AGWhen planning infrastructure and architecture, we often ignore the idea of tracing until the first problem occurs. Let's solve it!

Dringende Sehempfehlung für alle, die ein #Handy haben: der Vortrag »Staatliche Überwachung: Erfahrungen und Beispiele aus der Praxis« von Marco B. bei den #Datenspuren2024.

media.ccc.de/v/ds24-467-staatl
Was ich noch gar nicht kannte, war notrace.how.
Weitere Tipps bekommt ihr auf dieser Instanz bei @smartphone.

Wenn Staatsanwaltschaften #Klimaaktivismus für Terrorismus und #Antifaschismus für staatsfeindlich halten, müssen sich auch rechtschaffene Bürger:innen gegen staatliche Überwachung wehren. Manche Polizist:innen geben jetzt schon eure Daten an Nazis weiter. Verschlüsselt alle Daten, sonst werden sie spätestens nach der nächsten NS-Machtergreifung gegen euch verwendet!

#Genetic #tracing of #market #wildlife and #viruses at #epicenter of #COVID19 #pandemic, Cell: cell.com/cell/fulltext/S0092-8

Common #ancestor of #SARS-CoV-2 linked to #Huanan market matches global common ancestor. Wildlife mitochondrial DNA identified in samples from stalls positive for SARS-CoV-2.
DNA from raccoon dogs, civets, & other wildlife species detected in market samples. Genotypes of potential hosts were reconstructed for retracing animal geographic origins.

Here's my [naive] attempt to consider tracing instead of logging.

The UI of everything just sucks. So much whitespace. So many clicks.

Grafana & tempo

It's free and opensource. It works. You can't seem to force the thing to order spans by timestamp so **sometimes** the top span isn't the latest one. The table view sucks because it has columns you never asked for, leaving less space for columns you asked for. The trace view requires A LOT of clicks to drill down. 16" window size minimum or things get weird.

Datadog

Very frontend-oriented. All the attributes are mixed up together so good luck finding the ones you care about in a modal window. I'd have to sell my horse to afford it, too.

openobserve.ai

Whatever that thing is. It's theoretically FOSS and runs on elastic. Data density is ok but it repeats itself, confuses things, and doesn't allow to drill down in any reasonable manner.

Sentry

It doesn't play nicely with otel spans, missing the events data completely. Meh.

Google Cloud

The "list of traces" UI is seemingly nonexistent, so you can't really use it as a logs replacement at all. The attributes are mixed together and sorted alphabetically, so once again the ones you care for will be interleaved with things like `process.runtime.description`.

AWS

Only shows you the attributes if you look at the raw JSON representation. Talk about UX.

Funnily enough, I started with grafana, looked over all this stuff and came back to grafana realizing that it's actually not that bad! Still, you can't easily work on a live application and rely on traces instead of logs because they aren't just presented in a way that's easy for a human to digest. And yes, I wrote a custom nodejs otel span processor that logs the traces in stdout in a way that looks like semantic logs now.

The more I read about tracing, the more I want to overhaul my applications I run to start emitting the #tracing events. The big question is, where do I send them?

Now I've gotta setup a #SigNoz cluster(?) to ingest and act on these data in a meaningful way, let alone worry about data retention... huh. #OTEL is cool and all, but I need a free, self-hosted option that's easy to work with in small scale to really get comfortable with it. I'm tired of investing energy into SaaS products (FOSS or not) only to have them disappoint later by being bought out, changing license/usage terms, or totally shuttering their doors.