You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Redis Receiver and the Kafka Receiver offer different functionalities with the Redis receiver pulling metrics about the specific Redis instance and the Kafka receiver receiving metrics, logs & traces from a Kafka topic.
Redis (and Valkey) support Streams, an optionally persistent append-only log that can be used for event sourcing.
We (and I assume others) already use Redis internally and are examining the possibility to use Streams as a lightweight Kafka alternative. This would also include acting as a queue for our OTel data.
Having the option to use Redis/Valkey Streams as a receiver would be great.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently the
Redis Receiver
and theKafka Receiver
offer different functionalities with the Redis receiver pulling metrics about the specific Redis instance and the Kafka receiver receiving metrics, logs & traces from a Kafka topic.Redis (and Valkey) support Streams, an optionally persistent append-only log that can be used for event sourcing.
We (and I assume others) already use Redis internally and are examining the possibility to use Streams as a lightweight Kafka alternative. This would also include acting as a queue for our OTel data.
Having the option to use Redis/Valkey Streams as a receiver would be great.
Beta Was this translation helpful? Give feedback.
All reactions