Viewing Tyk Gateway data in Redis

Product FAQ
, ,
3

@Anup_Rai to provide a more concrete example for what Sedky suggested:

kubectl exec -it -n tykpro redis-db9784c88-2fn8v -- redis-cli
127.0.0.1:6379> keys *
 1) "tyk-admin-api-607582f6477fb5b377f59ab2"
 2) "tyk-node-prefix34b3d133-8bd6-45bd-77cd-b4a811c82311"
 3) "tyk-node-prefix697286bf-9b47-4a76-7215-e8370baca7a9"
 4) "redis-test-b05c27d5-2737-4d98-9e86-a6036daac446"
 5) "tyk-liveness-probe"
 6) "tyk-node-prefix373c1979-85f8-4edb-46a7-027a274100c9"
 7) "redis-test-2f492030-cd1b-49c0-8cc6-07d1495b6ddf"
 8) "redis-test-c0a2e085-6cd3-4621-a03b-e3739c54318e"
 9) "tyk-admin-api-444c9fbd-05aa-4d62-5fb4-f9a4d6da80cb"
10) "apikey-d631ef32221dd6b5d56890055411569c"
11) "tyk-nodeid-prefixnode-ids"
12) "tyk-admin-api-1660cea0b0b84a5e42344205f87ff6b2"
13) "tyk-node-prefix0fda95b7-329e-4c26-4fc1-3bf226e61905"
14) "host-checker:PollerActiveInstanceID"
15) "tyk-admin-api-f359d9b6-9a68-4d2f-719c-f3b691d70162"
16) "version-check-pump"

Please however be careful doing this in a production system. Consider KEYS as a command that should only be used in production environments with extreme care.

1 Like