number101010

Joined 7 years ago

Karma

Submissions

Member since

Jul 12

Creator of Tempo, Jaeger maintainer, technical lead for distributed tracing at Grafana.

View on Hacker News

Recent submissions

Comment · 3 years ago

> It's easy to add Jaeger to your local dev stack so you can have tracing while developing.

Tempo can be spun up with docker compose using a local disk for ephemeral storage/querying: https://github.com/grafana/tempo/blob/main/example/docker-co...

Maybe this meets your needs?

> Jaeger is easier to setup/manage and has a better interface than Grafana/Tempo

What do you enjoy about the Jaeger interface? Perhaps it's a gap in Tempo we can improve.

Comment · 3 years ago

Most observability vendors support OTEL at this point. To plug the OSS project I work on that supports OTEL ingestion:

https://github.com/grafana/tempo/

Comment · 3 years ago

Nice! RedHat built the Tempo operator and I have not had a chance to use it yet. We are looking to collaborate more closely on it soon.

Comment · 3 years ago

I work on Grafana Tempo and this is not at all how I see things. I'm sorry if you've had a bad experience, but we work quite hard to field questions, PRs, and suggestions.

Every day I wake up and spend at least an hour reading and responding to issues and PRs in the Tempo repo.

Comment · 4 years ago

We are definitely investigating columnar formats in Tempo to store traces. We expect it to drastically accelerate search as well as open up more complex querying and eventually metrics from distributed tracing data.

However, we are currently primarily targeting Parquet as our columnar format in object storage.

Expect an announcement soon!

Comment · 6 years ago

We batch up traces in a block and write a block at a time. Internally we are currently configured to write 100k traces in one batch.

Comment · 6 years ago

The headline would be:

Jaeger supports native search, but requires Elastic or Cassandra.

Tempo relies on discovery from logs/exemplars, but puts everything in object storage (s3/gcs).

Tempo is cheaper and easier to operate but lacks native search.

Comment · 6 years ago

We are ingesting 170k+ with Tempo. It is 100% of our read/query path.

Disclaimer: I am using Tempo :) (and from Grafana)

Comment · 6 years ago

it depends on your needs. if a single log line is sufficient to log all the information you need to do your debugging then Loki is a great choice.

if you need to see the full request as it passed through your system then distributed tracing/Tempo is a great fit!

Comment · 6 years ago

Hey everyone, I am the creator of Tempo and would be glad to answer any questions you may have.

Comment · 6 years ago

I think it's fair to say that:

3. This information is worth an enormous amount of money.

Comment · 6 years ago

Hey Tom!

Can you outline how Cortex differs from some of the other available Prometheus backends?

Comment · 7 years ago

The randomizers I have followed (Link to the Past, Final Fantasy) only choose viable randomizations.

They are aware of the items that are required to progress and make sure they are available appropriately.

Comment · 7 years ago

I have noticed this effect in myself while watching streamers on Twitch. You start to feel like you're sitting on a couch with your buddy playing a game.