> 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:…
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/
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.
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…
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.…
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.
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…
Hey everyone, I am the creator of Tempo and would be glad to answer any questions you may have.
I think it's fair to say that: 3. This information is worth an enormous amount of money.
Hey Tom! Can you outline how Cortex differs from some of the other available Prometheus backends?
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.
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.
> 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:…
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/
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.
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…
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.…
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.
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…
Hey everyone, I am the creator of Tempo and would be glad to answer any questions you may have.
I think it's fair to say that: 3. This information is worth an enormous amount of money.
Hey Tom! Can you outline how Cortex differs from some of the other available Prometheus backends?
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.
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.