<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://docs.crowdsec.net/blog</id>
    <title>CrowdSec Blog</title>
    <updated>2024-06-11T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://docs.crowdsec.net/blog"/>
    <subtitle>CrowdSec Blog</subtitle>
    <icon>https://docs.crowdsec.net/img/crowdsec_no_txt.png</icon>
    <entry>
        <title type="html"><![CDATA[Cscli dashboard deprecation]]></title>
        <id>https://docs.crowdsec.net/blog/cscli_dashboard_deprecation</id>
        <link href="https://docs.crowdsec.net/blog/cscli_dashboard_deprecation"/>
        <updated>2024-06-11T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[This blog article will outline the steps being taken to deprecate the cscli dashboard command out of the cscli binary. The cscli dashboard command was used to setup a containerized Metabase dashboard.]]></summary>
        <content type="html"><![CDATA[<p>This blog article will outline the steps being taken to deprecate the <code>cscli dashboard</code> command out of the <code>cscli</code> binary. The <code>cscli dashboard</code> command was used to setup a containerized Metabase dashboard.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-deprecate-cscli-dashboard-">Why deprecate <code>cscli dashboard</code> ?<a href="https://docs.crowdsec.net/blog/cscli_dashboard_deprecation#why-deprecate-cscli-dashboard-" class="hash-link" aria-label="Direct link to why-deprecate-cscli-dashboard-" title="Direct link to why-deprecate-cscli-dashboard-" translate="no">​</a></h2>
<p>There were multiple factors which led to the decision to deprecate the <code>cscli dashboard</code> command:</p>
<p>The <code>cscli dashboard</code> command was initially offered a way to visualize the data collected by your local CrowdSec instance. However, we found the tools to be too limited and not user-friendly enough. So we started working on the <a href="https://app.crowdsec.net/" target="_blank" rel="noopener noreferrer" class="">CrowdSec Console</a> which is a more powerful and user-friendly tool to visualize your data.</p>
<p>Some users using <code>cscli dashboard</code> command did not understand what was happening "under the hood" and were not proactively maintaining or securing their dashboards. This led to recent <a href="https://www.cvedetails.com/vulnerability-list/vendor_id-19475/product_id-51231/Metabase-Metabase.html?page=1&amp;order=1&amp;trc=16&amp;sha=d16c0f1d7c9eb6761cdc711c7e1caee1e2a2c079" target="_blank" rel="noopener noreferrer" class="">CVE's</a> not being patched in a timely manner since the version was tied to the <code>cscli</code> binary and users were publicly exposing their dashboards.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-will-happen-to-the-cscli-dashboard-command-">What will happen to the <code>cscli dashboard</code> command ?<a href="https://docs.crowdsec.net/blog/cscli_dashboard_deprecation#what-will-happen-to-the-cscli-dashboard-command-" class="hash-link" aria-label="Direct link to what-will-happen-to-the-cscli-dashboard-command-" title="Direct link to what-will-happen-to-the-cscli-dashboard-command-" translate="no">​</a></h2>
<p>The <code>cscli dashboard</code> command will be deprecated starting from version <code>1.7.0</code> of the CrowdSec package. Moving forward, users will have the following alternatives for viewing metrics and insights:</p>
<ul>
<li class="">CrowdSec Console (officially supported)</li>
<li class="">Prometheus with Grafana</li>
<li class="">VictoriaMetrics with Grafana</li>
</ul>
<p>Please note that <strong>only the CrowdSec Console is officially supported by the CrowdSec team</strong>. The other options are provided for flexibility but are community-driven and require self-management.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-should-i-do-now">What should I do now?<a href="https://docs.crowdsec.net/blog/cscli_dashboard_deprecation#what-should-i-do-now" class="hash-link" aria-label="Direct link to What should I do now?" title="Direct link to What should I do now?" translate="no">​</a></h2>
<p>Currently we recommend that you firstly check which version of Metabase that is currently deployed on your system to ensure that you are not vulnerable to any CVE's. You can do this by running the following command:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#9CDCFE;--prism-background-color:#1E1E1E"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#9CDCFE;background-color:#1E1E1E"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#9CDCFE"><span class="token function" style="color:rgb(220, 220, 170)">docker</span><span class="token plain"> </span><span class="token function" style="color:rgb(220, 220, 170)">ps</span><span class="token plain"> </span><span class="token parameter variable" style="color:rgb(156, 220, 254)">-a</span><br></span></code></pre></div></div>
<p>This will show you the running containers on your system. Look for the Metabase container and check its version. If you are running a version of Metabase that is vulnerable to a CVE, we recommend updating to the latest version of CrowdSec and re-running the <code>cscli dashboard</code> command to refresh the Metabase dashboard.</p>
<p><strong>If you are already on version <code>1.7.0</code>, you will need to manually remove the container, as the <code>cscli dashboard</code> command is no longer available.</strong></p>]]></content>
        <author>
            <name>Crowdsec Team</name>
            <uri>https://github.com/crowdsecurity</uri>
        </author>
        <category label="dashboard" term="dashboard"/>
        <category label="Metabase" term="Metabase"/>
    </entry>
</feed>