From Redis to Valkey: pre-migration Reconnaissance — detect all apps & connections in realtime

Abstract Abraham Lincoln: "Give me six hours to chop down a tree and I will spend the first four sharpening the axe" Redis Valkey is getting more popular due to its performance increase compared to classic Redis version, I'm starting a seris of posts related to migration from one vendors' Redis implemnetation to AWS Valkey. To choose proper migration technics, the most important step is a reconnaissance of pre-migration. In this post I'll explain how native Redis features can help to identify all services that have connection to Redis (what is really hard in distributed environment of enterprise level infrastucture, that was created with periodically changed stack, languages, SDKs by multiple engineering generations). Valkey project bried history Redis first version release was in 2009, since that time it grown from cache key-value storage to PubSub, Stream, DB and used in a lot of projects. Thus cloud providers AWS, GCP, Azure, Oracle started providing Redis as a managed service - all