{"id":21049,"date":"2017-02-13T10:30:58","date_gmt":"2017-02-13T09:30:58","guid":{"rendered":"https:\/\/www.inovex.de\/blog\/?p=2756"},"modified":"2026-03-17T08:57:58","modified_gmt":"2026-03-17T07:57:58","slug":"redis-cli","status":"publish","type":"post","link":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/","title":{"rendered":"Using the command line to check redis health"},"content":{"rendered":"<p>In the forth entry of our series on redis we&#8217;ll have a look at its CLI tools. The central question for today: How can we check that redis is working as expected using the command line?<!--more--><\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_83 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\"><p class=\"ez-toc-title\" style=\"cursor:inherit\"><\/p>\n<\/div><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#redis-CLI-basics\" >redis-CLI basics<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#List-of-commands\" >List of commands<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#Integrated-latency-monitoring-reporting-slow-logs\" >Integrated latency monitoring, reporting, slow-logs<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#How-to-enable-latency-monitoring\" >How to enable latency monitoring?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#What-should-I-do-when-redis-experiences-latency-spikes\" >What should I do when redis experiences latency spikes?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#More-on-redis\" >More on redis<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#Read-on\" >Read on<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#Join-us\" >Join us!<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"redis-CLI-basics\"><\/span>redis-CLI basics<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Using redis-cli to check database health sounds easy and, in fact, it is: A simple <span class=\"lang:sh decode:true crayon-inline \">redis-cli PING<\/span> on the Redis host returns a <span class=\"lang:sh decode:true crayon-inline \">PONG<\/span>. This does not look very reliable, but it is. A redis that returns a <span class=\"lang:sh decode:true crayon-inline \">PONG<\/span> is fully functional and works as expected.<\/p>\n<p>To go a bit more into detail: it means that the dataset is completely loaded, and Redis is ready for connections. If something does not work fine, it will display error messages such as \u201c(error) LOADING Redis is loading the dataset in memory\u201c. This will return while loading the rdb\/aof file or waiting for replication to be completed.<\/p>\n<p>By using the redis-CLI you can easily use the <span class=\"lang:sh decode:true crayon-inline \">info<\/span> command and sub-commands to get some more stats and information.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"List-of-commands\"><\/span>List of commands<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n<table id=\"tablepress-16\" class=\"tablepress tablepress-id-16\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">redis-cli info<\/th><th class=\"column-2\">Complete info about the redis-instance<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">redis-cli info server<\/td><td class=\"column-2\">Server Information, cersions, configs, binary<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">redis-cli info clients<\/td><td class=\"column-2\">Connected clients<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">redis-cli info memory<\/td><td class=\"column-2\">Statistics about memory usage and limits<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">redis-cli info persistence<\/td><td class=\"column-2\">Info about RDB and AOF<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">redis-cli info stats<\/td><td class=\"column-2\">Connection, network, keyspace statistics<\/td>\n<\/tr>\n<tr class=\"row-7\">\n\t<td class=\"column-1\">redis-cli info replication<\/td><td class=\"column-2\">Replication settings and status<\/td>\n<\/tr>\n<tr class=\"row-8\">\n\t<td class=\"column-1\">redis-cli info cpu<\/td><td class=\"column-2\">CPU utilization<\/td>\n<\/tr>\n<tr class=\"row-9\">\n\t<td class=\"column-1\">redis-cli info cluster<\/td><td class=\"column-2\">Cluster settings and status<\/td>\n<\/tr>\n<tr class=\"row-10\">\n\t<td class=\"column-1\">redis-cli info keyspace<\/td><td class=\"column-2\">Display dbs and number of keys<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<p>To repeat commands you can easily use two options for monitoring: <span class=\"lang:sh decode:true crayon-inline \">redis-cli -r 5 -i 2 &lt;command&gt;<\/span> will execute the <span class=\"lang:sh decode:true crayon-inline \">&lt;command&gt;<\/span> five times with an interval of two seconds.<\/p>\n<p>With these commands you can easily integrate redis in your monitoring. Just add the redis-CLI commands as custom parameters, e.g. to Zabbix or Nagios. You can also use <a href=\"https:\/\/prometheus.io\/docs\/instrumenting\/exporters\/\" target=\"_blank\" rel=\"noopener\">prometheus exporters<\/a> to get metrics out of your redis.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Integrated-latency-monitoring-reporting-slow-logs\"><\/span>Integrated latency monitoring, reporting, slow-logs<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Maybe some of you ask yourselves why we need monitoring in the first place, as redis is so incredibly fast. The answer is: you\u2019re right, redis is designed to serve a large amount of queries per second per instance. But unfortunately in most applications there is a strict requirement for the average response time and for a worst case latency.<\/p>\n<p>Nevertheless redis has a huge amount of commands, some commands are fast and run in constant or logarithmic time, other commands are slower, possibly causing latency spikes. Other reasons for this way of monitoring are interaction with the operating system (e.g. disk persistence) and the single-thread architecture of redis.<\/p>\n<p>Since version 2.8.13 latency monitoring helps to troubleshoot possible latency problems. The following mechanics are part of this framework:<\/p>\n<ul>\n<li>Latency hooks that sample different latency sensitive code paths.<\/li>\n<li>Time series recording of latency spikes split by another event.<\/li>\n<li>Reporting engine to fetch raw data from the time series.<\/li>\n<li>Analysis engine to provide human readable reports and hints according to the measurements.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"How-to-enable-latency-monitoring\"><\/span>How to enable latency monitoring?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>During runtime of redis latency monitoring can be easily enabled by <span class=\"lang:sh decode:true crayon-inline \">config set latency-monitor-threshold 100<\/span>. The tailing number defines a time in milliseconds. In our example, every event that will take more then 100ms will be logged as a latency spike. Here are some commands to display and reset logged events:<\/p>\n\n<table id=\"tablepress-17\" class=\"tablepress tablepress-id-17\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">latency latest<\/th><th class=\"column-2\">display the latest latency events logged<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">latency history event-name<\/td><td class=\"column-2\">display up to 160 elements for the given event name, you get timestamp and latency value<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">latency reset<\/td><td class=\"column-2\">reset all events at the time-series<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">latency reset event-name<\/td><td class=\"column-2\">reset only the given event-name<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">latency graph event-name<\/td><td class=\"column-2\">ascii-art style graph for the event<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">latency doctor<\/td><td class=\"column-2\">gives details information about latency spikes and advices<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<h2><span class=\"ez-toc-section\" id=\"What-should-I-do-when-redis-experiences-latency-spikes\"><\/span>What should I do when redis experiences latency spikes?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The next step could be to enable the slow-log. With <span class=\"lang:sh decode:true crayon-inline \">config set slowlog-log-slower-than 1000<\/span> you can log every event that lasts longer then 1000ms. More commands:<\/p>\n\n<table id=\"tablepress-18\" class=\"tablepress tablepress-id-18\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">slowlog-log-slower-than -1<\/th><th class=\"column-2\">disable slow log<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">slowlog-log-slower-than 0<\/td><td class=\"column-2\">log every command<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">slowlog-max-len N<\/td><td class=\"column-2\">maximum length of the logfile (ringbuffer-style)<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">slowlog get N<\/td><td class=\"column-2\">will display the last N events in the log<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">slowlog len<\/td><td class=\"column-2\">length of the current logfile<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">slowlog reset<\/td><td class=\"column-2\">delete all information at the log<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<h2><span class=\"ez-toc-section\" id=\"More-on-redis\"><\/span>More on redis<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>We&#8217;ve already published various articles on redis. If you&#8217;re new to the subject you best start with our <a href=\"https:\/\/www.inovex.de\/blog\/redis-more-than-caching\/\" target=\"_blank\" rel=\"noopener\">introduction<\/a>. Have your redis up and running? Learn how to <a href=\"https:\/\/www.inovex.de\/blog\/redis-backup\/\" target=\"_blank\" rel=\"noopener\">back its data up and save snapshots<\/a>. Finally, we show you how to <a href=\"https:\/\/www.inovex.de\/blog\/redis-sentinel-make-your-dataset-highly-available\/\" target=\"_blank\" rel=\"noopener\">make your data highly available<\/a> with redis.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Read-on\"><\/span>Read on<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Want to find out more about the services we offer in Data Center Automation? Have a <a href=\"https:\/\/www.inovex.de\/en\/our-services\/data-centre-automation\/\" target=\"_blank\" rel=\"noopener\">look at our website<\/a>, write an email to <a href=\"mailto:info@inovex.de\" target=\"_blank\" rel=\"noopener\">info@inovex.de<\/a> or call <a href=\"tel:+497216190210\">+49 721 619 021-0<\/a><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Join-us\"><\/span>Join us!<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Looking for a job where you can work with cutting edge technology on a daily basis? We&#8217;re currently hiring Linux Systems Engineers in Karlsruhe, Pforzheim, Munich, Cologne and Hamburg!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the forth entry of our series on redis we&#8217;ll have a look at its CLI tools. The central question for today: How can we check that redis is working as expected using the command line?<\/p>\n","protected":false},"author":47,"featured_media":13462,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"ep_exclude_from_search":false,"footnotes":""},"tags":[71],"service":[414],"coauthors":[{"id":47,"display_name":"Christoph Stich","user_nicename":"cstich"}],"class_list":["post-21049","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","tag-cloud","service-cloud"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Using the command line to check redis health - inovex GmbH<\/title>\n<meta name=\"description\" content=\"In the forth entry of our series on redis we&#039;ll have a look at its CLI tools and how we can check that redis is working as expected.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Using the command line to check redis health - inovex GmbH\" \/>\n<meta property=\"og:description\" content=\"In the forth entry of our series on redis we&#039;ll have a look at its CLI tools and how we can check that redis is working as expected.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/\" \/>\n<meta property=\"og:site_name\" content=\"inovex GmbH\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/inovexde\" \/>\n<meta property=\"article:published_time\" content=\"2017-02-13T09:30:58+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-17T07:57:58+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-primer-hero-image.png\" \/>\n\t<meta property=\"og:image:width\" content=\"960\" \/>\n\t<meta property=\"og:image:height\" content=\"540\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Christoph Stich\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-primer-hero-image.png\" \/>\n<meta name=\"twitter:creator\" content=\"@inovexgmbh\" \/>\n<meta name=\"twitter:site\" content=\"@inovexgmbh\" \/>\n<meta name=\"twitter:label1\" content=\"Verfasst von\" \/>\n\t<meta name=\"twitter:data1\" content=\"Christoph Stich\" \/>\n\t<meta name=\"twitter:label2\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data2\" content=\"3\u00a0Minuten\" \/>\n\t<meta name=\"twitter:label3\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data3\" content=\"Christoph Stich\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/\"},\"author\":{\"name\":\"Christoph Stich\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#\\\/schema\\\/person\\\/683665a7244d27a96c0d5e561c777c11\"},\"headline\":\"Using the command line to check redis health\",\"datePublished\":\"2017-02-13T09:30:58+00:00\",\"dateModified\":\"2026-03-17T07:57:58+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/\"},\"wordCount\":632,\"commentCount\":2,\"publisher\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2016\\\/07\\\/redis-primer-hero-image.png\",\"keywords\":[\"Cloud\"],\"articleSection\":[\"English Content\",\"General\",\"Infrastructure\"],\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/\",\"name\":\"Using the command line to check redis health - inovex GmbH\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2016\\\/07\\\/redis-primer-hero-image.png\",\"datePublished\":\"2017-02-13T09:30:58+00:00\",\"dateModified\":\"2026-03-17T07:57:58+00:00\",\"description\":\"In the forth entry of our series on redis we'll have a look at its CLI tools and how we can check that redis is working as expected.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2016\\\/07\\\/redis-primer-hero-image.png\",\"contentUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2016\\\/07\\\/redis-primer-hero-image.png\",\"width\":960,\"height\":540,\"caption\":\"The redis logo on a gradient\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-cli\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Using the command line to check redis health\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#website\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/\",\"name\":\"inovex GmbH\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#organization\",\"name\":\"inovex GmbH\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2021\\\/03\\\/inovex-logo-16-9-1.png\",\"contentUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2021\\\/03\\\/inovex-logo-16-9-1.png\",\"width\":1921,\"height\":1081,\"caption\":\"inovex GmbH\"},\"image\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/inovexde\",\"https:\\\/\\\/x.com\\\/inovexgmbh\",\"https:\\\/\\\/www.instagram.com\\\/inovexlife\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/inovex\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UC7r66GT14hROB_RQsQBAQUQ\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#\\\/schema\\\/person\\\/683665a7244d27a96c0d5e561c777c11\",\"name\":\"Christoph Stich\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g57f6cb0c101a17628911877b9968c8c5\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g\",\"caption\":\"Christoph Stich\"},\"url\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/author\\\/cstich\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Using the command line to check redis health - inovex GmbH","description":"In the forth entry of our series on redis we'll have a look at its CLI tools and how we can check that redis is working as expected.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/","og_locale":"de_DE","og_type":"article","og_title":"Using the command line to check redis health - inovex GmbH","og_description":"In the forth entry of our series on redis we'll have a look at its CLI tools and how we can check that redis is working as expected.","og_url":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/","og_site_name":"inovex GmbH","article_publisher":"https:\/\/www.facebook.com\/inovexde","article_published_time":"2017-02-13T09:30:58+00:00","article_modified_time":"2026-03-17T07:57:58+00:00","og_image":[{"width":960,"height":540,"url":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-primer-hero-image.png","type":"image\/png"}],"author":"Christoph Stich","twitter_card":"summary_large_image","twitter_image":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-primer-hero-image.png","twitter_creator":"@inovexgmbh","twitter_site":"@inovexgmbh","twitter_misc":{"Verfasst von":"Christoph Stich","Gesch\u00e4tzte Lesezeit":"3\u00a0Minuten","Written by":"Christoph Stich"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#article","isPartOf":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/"},"author":{"name":"Christoph Stich","@id":"https:\/\/www.inovex.de\/de\/#\/schema\/person\/683665a7244d27a96c0d5e561c777c11"},"headline":"Using the command line to check redis health","datePublished":"2017-02-13T09:30:58+00:00","dateModified":"2026-03-17T07:57:58+00:00","mainEntityOfPage":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/"},"wordCount":632,"commentCount":2,"publisher":{"@id":"https:\/\/www.inovex.de\/de\/#organization"},"image":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#primaryimage"},"thumbnailUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-primer-hero-image.png","keywords":["Cloud"],"articleSection":["English Content","General","Infrastructure"],"inLanguage":"de","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/","url":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/","name":"Using the command line to check redis health - inovex GmbH","isPartOf":{"@id":"https:\/\/www.inovex.de\/de\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#primaryimage"},"image":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#primaryimage"},"thumbnailUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-primer-hero-image.png","datePublished":"2017-02-13T09:30:58+00:00","dateModified":"2026-03-17T07:57:58+00:00","description":"In the forth entry of our series on redis we'll have a look at its CLI tools and how we can check that redis is working as expected.","breadcrumb":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.inovex.de\/de\/blog\/redis-cli\/"]}]},{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#primaryimage","url":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-primer-hero-image.png","contentUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-primer-hero-image.png","width":960,"height":540,"caption":"The redis logo on a gradient"},{"@type":"BreadcrumbList","@id":"https:\/\/www.inovex.de\/de\/blog\/redis-cli\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.inovex.de\/de\/"},{"@type":"ListItem","position":2,"name":"Using the command line to check redis health"}]},{"@type":"WebSite","@id":"https:\/\/www.inovex.de\/de\/#website","url":"https:\/\/www.inovex.de\/de\/","name":"inovex GmbH","description":"","publisher":{"@id":"https:\/\/www.inovex.de\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.inovex.de\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/www.inovex.de\/de\/#organization","name":"inovex GmbH","url":"https:\/\/www.inovex.de\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/www.inovex.de\/de\/#\/schema\/logo\/image\/","url":"https:\/\/www.inovex.de\/wp-content\/uploads\/2021\/03\/inovex-logo-16-9-1.png","contentUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/2021\/03\/inovex-logo-16-9-1.png","width":1921,"height":1081,"caption":"inovex GmbH"},"image":{"@id":"https:\/\/www.inovex.de\/de\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/inovexde","https:\/\/x.com\/inovexgmbh","https:\/\/www.instagram.com\/inovexlife\/","https:\/\/www.linkedin.com\/company\/inovex","https:\/\/www.youtube.com\/channel\/UC7r66GT14hROB_RQsQBAQUQ"]},{"@type":"Person","@id":"https:\/\/www.inovex.de\/de\/#\/schema\/person\/683665a7244d27a96c0d5e561c777c11","name":"Christoph Stich","image":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/secure.gravatar.com\/avatar\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g57f6cb0c101a17628911877b9968c8c5","url":"https:\/\/secure.gravatar.com\/avatar\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g","caption":"Christoph Stich"},"url":"https:\/\/www.inovex.de\/de\/blog\/author\/cstich\/"}]}},"_links":{"self":[{"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/posts\/21049","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/users\/47"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/comments?post=21049"}],"version-history":[{"count":3,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/posts\/21049\/revisions"}],"predecessor-version":[{"id":66588,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/posts\/21049\/revisions\/66588"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/media\/13462"}],"wp:attachment":[{"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/media?parent=21049"}],"wp:term":[{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/tags?post=21049"},{"taxonomy":"service","embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/service?post=21049"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/coauthors?post=21049"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}