Just instrument your meter implementation so each observation produces a span. Boom, free metric-derived traces.
56 karma · joined April 21, 2019
Just instrument your meter implementation so each observation produces a span. Boom, free metric-derived traces.
I've used tree-sitter for a few projects, but I never touched the tree-reuse stuff. The value of tree-sitter came from the fact that grammars compile to a .so and can be easily distributed through package managers. Adding support for a new grammar in ast-grep might just mean pointing to the .so at runtime (idk, I haven't checked). So this optimization might make sense for this project.
I don't think it's fair to say "no one wants to invest in proper instrumentation" - the OpenTelemetry community has built a massive amount of instrumentation in a relatively short period of time. Yes, OpenTelemetry is still young and unstable, but it's getting better every day.
As the article notes, the OpenTelemetry Collector has plugins can convert nearly any telemetry format to OTLP and back. Many of the plugins are "official" and maintained by employees of Splunk, Datadog, Snowflake, etc. Not only does it break the lock-in, but it allows you to reuse all the great instrumentation that's been built up over the years.
> The core issue is that, with otel, observability platforms become just a UI layer over a database.
I think this is a good thing - when everyone is on the same playing field (I can use Datadog instrumentation, convert it to OTel, then export it to Grafana Cloud/Prometheus), vendors will have to compete on performance and UX instead of their ability to lock us in with "golden handcuffs" instrumentation libraries.
fn(x=,y=,z=)
https://peps.python.org/pep-0736/edit: nevermind, that PEP was rejected :/
Is the pattern matching API not sufficiently high level? In my experience, it's a huge improvement over implementing visitors for everything.
https://tree-sitter.github.io/tree-sitter/using-parsers#patt...
https://github.com/OpenLoco/OpenLoco/blob/master/src/Interop...
So, Go?
I have also found this to be the case, even with engineers that have years of experience. It's both impressive and awful.
Bonus SO post to enhance your fury:
https://stackoverflow.com/questions/61762189/installing-gnu-...
Not in adults https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4195639/ https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9884156/ https://pubmed.ncbi.nlm.nih.gov/27553219/ https://pubmed.ncbi.nlm.nih.gov/25317367/
Reading it again now, it seems to advocate for going from one extreme to another without exercising judgement. A shell script might be fine in one context and irresponsible in another... but I guess nuance and circumstance don't make for interesting blog posts.
That seems unnecessary. Even a layman knows that in the context of a computer, space != physical space. Most people think of disk space, but it can also refer to memory usage [0]. The meaning of the name was obvious to me after reading the first half of the first sentence of the article. I thought it was clever :)
Find a place that gives free estimates. With SSDs the price was usually either low ($300) for "simple" repairs or very high ($2000+) for more intensive jobs. The price is always negotiable, especially for those simpler jobs. Oftentimes the data was already recovered and backed up by the time the repair quote was sent to the customer.
https://json-schema.org/understanding-json-schema/reference/...