<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Phil Xu on Medium]]></title>
        <description><![CDATA[Stories by Phil Xu on Medium]]></description>
        <link>https://medium.com/@zippoobbiz?source=rss-172587373920------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CdbxPvSI9nMUVITsnho_jw.jpeg</url>
            <title>Stories by Phil Xu on Medium</title>
            <link>https://medium.com/@zippoobbiz?source=rss-172587373920------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:57:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zippoobbiz/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Get started with Hashicorp Vault]]></title>
            <link>https://medium.com/weareservian/get-started-with-hashicorp-vault-cc132dce627d?source=rss-172587373920------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc132dce627d</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[secrets]]></category>
            <category><![CDATA[hashicorp-vault]]></category>
            <category><![CDATA[consul]]></category>
            <category><![CDATA[hashicorp]]></category>
            <dc:creator><![CDATA[Phil Xu]]></dc:creator>
            <pubDate>Fri, 14 Aug 2020 04:35:04 GMT</pubDate>
            <atom:updated>2020-08-31T01:27:58.462Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*LfQo-9_4Vfvz2YSI" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BgzAIFs5Mge4AWqqS2LdFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*MeuxGDHc9xmzZLoQ1khXmA.png" /></figure><p>HashiCorp Vault — This product is currently running in many big enterprise companies. I have seen a lot of people complain about the complexity of it and the pain of setting it up. I think this product is great and would like to share my experience and knowledge to help you speed up the initial set up. You will find it’s not as difficult as you think.</p><p>In this tutorial, I will walk you through how to set up vault with different types of backends in your local environment, also give you the example code so you can begin with a single command. But first, let’s have a quick look at why this product is currently in high demand.</p><h4>What is Vault and Why?</h4><p>Vault is the one-stop-shop for all your sensitive data. It stores and tightly controls access to tokens, passwords, certificates, encryption keys for protecting secrets, and other sensitive data using a UI, CLI, or HTTP API.</p><p><strong>Centralized — </strong>Vault is a comprehensive solution in one box, no need to have additional products for a specific feature, it contains</p><ul><li>Key Management System</li><li>Encryption System</li><li>PKI System</li><li>…</li></ul><p><strong>Multi-cloud — </strong>Just like all the other HashiCorp products, Vault is multi-cloud friendly. Imagine that your company is running a multi-cloud solution, and your AWS application needs to have access to GCP projects, the AWS IAM doesn’t make sense to GCP, however, with Vault as a broker, it does.</p><p><strong>Run Anywhere — </strong>Vault is just a piece of software and can be run anywhere. To install it, use homebrew, yum and apt-get, or maybe just download directly from Hashi’s website.</p><p>Vault binary can be used in many modes</p><ul><li><strong>Server mode — </strong>this is the mode that allows Vault to host the API server, interact with your client, and persist your secret data.</li><li><strong>Client mode — </strong>the same binary can be used as a client, since vault is just an API server, in the client mode vault can send a request to the server (consider it as a wrapper for curl) you may use curl or any other tool to send requests as well.</li><li><strong>Agent mode — </strong>this is a slightly more advanced way of using vault, it will sit somewhere in your VM or Container, talk to the vault server and retrieve the secret on your behalf, and eventually injects the secrets somewhere in the VM for your application. Read my other post for more details.</li></ul><p><a href="https://medium.com/@zippoobbiz/inject-vault-secret-with-agent-3333c99c2ee9">Inject Vault Secret with Agent</a></p><p>Let’s have a quick look at how to run it with different backend storage.</p><h4>Run the test server in memory</h4><p>Have vault added in your environment PATH and run the following command, just as simple as that, you can start to use vault in dev mode against your localhost at port 8200.</p><pre>vault server -dev</pre><p>Or do it with docker</p><pre>docker run --cap-add=IPC_LOCK -e &#39;VAULT_DEV_ROOT_TOKEN_ID=myroot&#39; -e &#39;VAULT_DEV_LISTEN_ADDRESS=0.0.0.0:1234&#39; -p 8200:1234 vault</pre><p><strong>IPC_LOCK</strong> memory lock is required to prevent swapping sensitive data to disk</p><p><strong>VAULT_DEV_ROOT_TOKEN_ID</strong> (optional) the root id can be easily be set in dev with the environment variable, if not, Vault will generate a random root token during initialization and output it in the log. Once up in dev mode, Vault will be initialized and unsealed, i.e. ready to use.</p><p><strong>VAULT_DEV_LISTEN_ADDRESS </strong>(optional), it defines where the API endpoint is listening to, needs to be 0.0.0.0 if in a container.</p><p>Use the same binary as the client to login with the following command, and Vault server will return a token stored at ~/.vault-token, the vault client will use it to send any later commands.</p><pre>vault login &lt;your-password&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7EMdfnrIaC5-OtAv-4JHZA.png" /><figcaption>vault login with root token</figcaption></figure><h4>File storage backend</h4><p>Vault can the secret data in a local file. However, it does not support High Availability, so it’s not ideal for production, I personally use it as the local test environment, so you can keep the work environment from last time.</p><p>In order to make it work, we will need to create a config file and add the following code block. This block is telling vault where to persist the encrypted data and listen to any request at port 8200, you can also custom the storage settings and have multiple listener blocks.</p><pre>storage &quot;file&quot; {<br>  path = &quot;vault/data&quot;<br>}</pre><pre>listener &quot;tcp&quot; {<br>  address = &quot;127.0.0.1:8200&quot;<br>  tls_disable = 1<br>}</pre><pre>ui = true</pre><p>Run the following command to start Vault server.</p><pre>vault server -config=/path/to/your/config/file</pre><p>When running Vault in non-dev mode, you will need to init and unseal the Vault before using it.</p><pre>vault operator init</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jq0QqA7HviiYahOIp3rkiA.png" /></figure><pre>vault operator init<br>vault operator unseal &lt;shamir-key1&gt;<br>vault operator unseal &lt;shamir-key2&gt;<br>vault operator unseal &lt;shamir-key3&gt;<br>vault login &lt;initial-root-token&gt;</pre><p>Of course, you can do it in docker, it’s pretty much what people do these days, to keep things tidy and clean. Start fresh from downloading the latest version of Vault on alpine or simply use the latest Vault Docker image.</p><p>Since we have the ui=true specified in the config file, Vault is also available at localhost:8200, try it in the browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bab_DqUE75j6MZEkW4xikA.png" /><figcaption>Sealed Vault</figcaption></figure><h4>Use Consul as backend</h4><p>When talking about Consul we can easily expand this into another whole new article, but for now, all you need to know is we can use Consul as the storage, and it supports HA which is the recommended way of running vault for production by HashiCorp. The ideal structure is having multiple consul servers as the storage cluster and a few vault servers on top. A production-ready cluster diagram would look as follows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ps1Kj67FB-LDOCZe.png" /></figure><p>Here I will provide an example of a docker-compose running a single vault and consul together. Don’t worry if the code is not complete here, I have the repo at the very end of the page, with more operational instructions in the README.</p><pre>docker-compose up -d</pre><p>Clone the repo and run the above command in the consul-backend folder, after about 10 seconds, Vault and Consul should be alive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*toeDJKSi1BwbT-aG_TjJ5w.png" /></figure><h4>Kubernetes</h4><p>You may think using Vault is the most complex on k8s, but on the contrary, it’s actually the easiest, everything has been sorted out for you, you can get it installed using helm and it will work without any change to the default chart file.</p><p>Install Vault only</p><pre>helm repo add hashicorp <a href="https://helm.releases.hashicorp.com/">https://helm.releases.hashicorp.com</a><br>helm install vault hashicorp/vault</pre><p>Or use Consul as the backend</p><pre>helm repo add hashicorp <a href="https://helm.releases.hashicorp.com/">https://helm.releases.hashicorp.com</a><br>helm install consul hashicorp/consul --values helm-consul-values.yml<br>helm install vault hashicorp/vault --values helm-vault-values.yml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rths4PkBgr3lQ7TIR8ejOA.png" /></figure><p>That’s pretty much what you need to do to get Vault up and running to play with, see it’s not that hard right?</p><p>Here is the repo with all the script you need on this page. Thanks for reading.</p><p><a href="https://github.com/zippoobbiz/hashicorp-vault-quick-start">zippoobbiz/hashicorp-vault-quick-start</a></p><p>I hope you found this page useful so far. Follow me and watch this space as I will be posting more Vault related articles. Here is my personal blog, check it out and click the AD link if you like it. Cheers.</p><p><a href="https://www.philsblog.info/">Welcome to Phil&#39;s</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc132dce627d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/weareservian/get-started-with-hashicorp-vault-cc132dce627d">Get started with Hashicorp Vault</a> was originally published in <a href="https://medium.com/weareservian">Cognizant Servian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inject Vault Secret with Agent]]></title>
            <link>https://medium.com/@zippoobbiz/inject-vault-secret-with-agent-3333c99c2ee9?source=rss-172587373920------2</link>
            <guid isPermaLink="false">https://medium.com/p/3333c99c2ee9</guid>
            <category><![CDATA[hashicorp-vault]]></category>
            <category><![CDATA[vault]]></category>
            <category><![CDATA[hashicorp]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Phil Xu]]></dc:creator>
            <pubDate>Mon, 10 Aug 2020 02:50:39 GMT</pubDate>
            <atom:updated>2020-08-12T22:30:55.287Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*83cXpc8L1-mlkpPi.png" /></figure><p>Vault Agent is a client daemon that allows the host to automatically authenticate to vault server, retrieve secret using the template and save it in the format at the place you defined.</p><p>To make it work, you will need to create a config file with the following blocks.</p><p><strong>pid_file</strong> defines the path to the file where the agent’s Process ID (PID) should be stored.</p><p><strong>vault</strong> specifies the remote Vault server that the Agent connects to.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd2b0c219841f618dc5aa348b23cc7ef/href">https://medium.com/media/dd2b0c219841f618dc5aa348b23cc7ef/href</a></iframe><p>And run the following command to start vault agent</p><pre>vault agent -config=/vault/config/vault-config.hcl</pre><h4>Auto Authentication</h4><p>In order for this to work, an auto auth method is also needed. In this case, a pair of AppRole credential is used, they will need to be mounted/stored before the agent starts. The agent will authenticate using these credentials and save the returned client token in the file specified in the sink block.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/aa161597d19b4a9ff88878bb04aacb70/href">https://medium.com/media/aa161597d19b4a9ff88878bb04aacb70/href</a></iframe><p>Until this point, a client token should be ready at the sink path, any application or script on the VM can use it to interact with Vault.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/0*rulb_gmAeaI1iwi4.png" /></figure><h4>Template</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/0*NZ4GjJpa11t_8zrr.png" /></figure><p>Once authenticated, the agent can retrieve the secret based on the template file at the <strong>source</strong> and save the retrieved secret to the destination. Here is an example of retrieving the database credentials and saving it in the format of a DB connection string.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0958eb8c999d1f3e7d8ea2b4637c2f95/href">https://medium.com/media/0958eb8c999d1f3e7d8ea2b4637c2f95/href</a></iframe><p>In the template file, it will read the secret at path /kv/database-connect-string (the middle part <strong>data</strong> is required for K/V secret version2)</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/decdd4380ebb90ae8b477baac79bc122/href">https://medium.com/media/decdd4380ebb90ae8b477baac79bc122/href</a></iframe><p>The example K/V secret in Vault is as the following.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*oQPlLGl75SwuurIqnm27kg.png" /></figure><p>The example output is as follow</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FPlhJv2Kvg1g5dZdlRiZeg.png" /><figcaption>db.credential</figcaption></figure><p>It also provides more features like cache, listener, etc. Please read more for further details <a href="https://www.vaultproject.io/docs/agent">https://www.vaultproject.io/docs/agent</a></p><p>The agent can be implemented in containers, here is an example of running it in docker.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/58fe69455d3ae7a4e163df84f0f61f45/href">https://medium.com/media/58fe69455d3ae7a4e163df84f0f61f45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3333c99c2ee9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Retrieve Hashicorp Vault Secrets from Kubernetes without a sidecar]]></title>
            <link>https://medium.com/@zippoobbiz/retrieve-hashicorp-vault-secrets-from-kubernetes-without-a-sidecar-3fa339c6ea62?source=rss-172587373920------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fa339c6ea62</guid>
            <category><![CDATA[hashicorp-vault]]></category>
            <category><![CDATA[init-containers]]></category>
            <category><![CDATA[hashicorp]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[sidecar]]></category>
            <dc:creator><![CDATA[Phil Xu]]></dc:creator>
            <pubDate>Wed, 29 Jul 2020 04:01:22 GMT</pubDate>
            <atom:updated>2020-07-29T04:04:00.716Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ayJcF20pQXb0vT9maws9tQ.png" /></figure><p>Hashicorp provides an easy way of injecting secret to the container with a vault sidecar agent. However, this requires an additional injector running and it can only work with K/V secret engine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mh9le4YBncNbmMNtm66BUA.png" /></figure><p>To make it more flexiable in some use cases, an init script or an initContainer could come in handy. Here is a working example of initContainer in K8s.</p><p>Add the following block to your deployment’s spec section, it will:</p><ol><li>leverage an image that supports <strong>curl</strong> and <strong>jq</strong></li><li>mount a shared volume to sync the secret or credentials between the init container and the application container</li><li>Wrap the <strong>JWT</strong> token to JSON format</li><li>Use the <strong>JWT</strong> token in the pod to authenticate to vault, save the returned vault token.</li><li>Use the token to retrieve any secret, and put it anywhere you like.</li></ol><pre>initContainers:<br>  - name: vault-secret-inject<br>    image: alpine-curl-jq<br>    imagePullPolicy: Never<br>    volumeMounts:<br>      - name: shared-data<br>        mountPath: /vault/secret<br>    command:<br>      [<br>        &quot;sh&quot;,<br>        &quot;-c&quot;,<br>        &#39;cd $JWT_PATH; <br>         <br>         cat token | jq -Rn &#39;&#39;{&quot;jwt&quot;: inputs, &quot;role&quot;: &quot;webapp&quot;}&#39;&#39; &gt; /vault/secret/token.json; </pre><pre>         curl -s --request POST --data @/vault/secret/token.json $VAULT_ADDR/v1/auth/kubernetes/login | jq -r &quot;.auth.client_token&quot; &gt; /vault/secret/.vault-token; <br>        <br>         curl -H \&quot;X-Vault-Token: @/vault/secret/.vault-token\&quot; -X GET $VAULT_ADDR/v1/secret/data/webapp/config</pre><pre>&#39;,<br>      ]<br>    env:<br>      - name: JWT_PATH<br>        value: &quot;/var/run/secrets/kubernetes.io/serviceaccount/&quot;<br>      - name: VAULT_ADDR<br>        value: &quot;<a href="http://vault.default.svc.cluster.local:8200/">http://vault:8200</a>&quot;</pre><p>This is a very simple way to retrieve the secrets without changing the existing application and container, also helps to avoid the extra overhead of having to run the injector.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fa339c6ea62" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hashicorp Vault usage review & load test]]></title>
            <link>https://medium.com/@zippoobbiz/hashicorp-vault-usage-review-load-test-5c02e76de895?source=rss-172587373920------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c02e76de895</guid>
            <category><![CDATA[log-monitoring]]></category>
            <category><![CDATA[load-testing]]></category>
            <category><![CDATA[gatling]]></category>
            <category><![CDATA[hashicorp-vault]]></category>
            <dc:creator><![CDATA[Phil Xu]]></dc:creator>
            <pubDate>Wed, 29 Jul 2020 02:12:40 GMT</pubDate>
            <atom:updated>2020-07-29T02:12:40.116Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qGwIrgxJy2gKNQEmLKanLA.png" /></figure><p>Have you ever wondered what the most commonly used <strong>Secret Path(</strong>or<strong> API endpoint)</strong> are in your Vault cluster? And how well those path behave under load testing? Here is a quick and simple guide on how to find those path then use Gatling to do load test on them.</p><p>In this tutorial, we will go through the following steps:</p><ol><li>Find your company’s most popular path</li><li>Use gatling to load test against those path</li><li>Interpret the result to find your system limit</li></ol><h3>1. Find your most requested path</h3><p>First, you will need to have the audit log enabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*kto0A-Ag-YFEFw58PEPWxA.png" /></figure><p>If it’s enabled already, here is how to find the audit log location.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J4vLHwgDaolLzSZqm4n6aQ.png" /></figure><p>Grep requests from the log file.</p><pre>cat *.log | grep &quot;type\&quot;:\&quot;request&quot; | jq</pre><p>Or do it properly with <strong>jq</strong></p><pre>cat *.log | jq ‘.| select(.type == “request”)’</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*KPhRTGgF6m_4DcXPCmOTwQ.png" /></figure><p>Note what we want here is to find all the unique paths and rank them according to popularity.</p><pre>cat *.log | jq ‘.| select(.type == “request”)’ | jq -r .request | jq -r .path | sort | uniq -c | sort -r</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*B5Awc8irn_XrC7NzH_x44w.png" /></figure><p>In this case, kv engine is used most frequently, let’s do a load test against it. You can easily graph these result in a dashboard tool like sumo, splunk or elasticsearch</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*-JKzEwB3E8ZpHfCra_g7gA.png" /></figure><h3>2. Use gatling to load test your most popular path</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H-GEWChK7snic-XktiODpw.png" /></figure><p>Download the open-source pack from <a href="https://gatling.io/open-source">Gatling official website</a>.</p><p><a href="https://gatling.io/open-source">Open Source - Gatling Open-Source Load Testing</a></p><p>Please ensure you have Java installed as Gatling needs JVM to run. If you don’t have the admin access on some remote servers, do a <a href="https://www.oracle.com/technetwork/java/javase/install-linux-64-self-extracting-142068.html">self-extracting installation</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*1vZHzel1L2A7Ua2IOTWhjA.png" /></figure><p>Add a new scala file, copy the following code (you will need to make some minor changes for it to work), replace</p><ul><li>&lt;your-namespace&gt;</li><li>&lt;your-token&gt;</li><li>&lt;your-vault-server-address&gt;</li><li>&lt;number-of-concurrent-users&gt;</li></ul><p>with your own values then run the gatling.sh script.</p><pre>package computerdatabase.advanced</pre><pre>import io.gatling.core.Predef._<br>import io.gatling.http.Predef._<br>import scala.concurrent.duration._<br>import java.util.concurrent.ThreadLocalRandom</pre><pre>class MyTest extends Simulation {</pre><pre>object GetKV {<br>    val getKV = exec(<br>        http(&quot;get kv&quot;)<br>          .get(&quot;/v1/kv/data/my-secret&quot;)<br>          .header(&quot;X-Vault-Namespace&quot;, &quot;&lt;your-namespace&gt;&quot;)<br>      )<br>  }</pre><pre>object PutKV {<br>    val putKV = exec(<br>        http(&quot;put kv&quot;)<br>          .put(&quot;/v1/kv/data/new-secret&quot;)<br>          .header(&quot;X-Vault-Namespace&quot;, &quot;&lt;your-namespace&gt;&quot;)<br>          .body(StringBody(&quot;&quot;&quot;{&quot;data&quot;:{&quot;my-key&quot;:&quot;my-vaule&quot;},&quot;options&quot;:{}}&quot; }&quot;&quot;&quot;)).asJson<br>      ).pause(1)<br>  }</pre><pre>val httpProtocol = http<br>    .baseUrl(&quot;https://&lt;your-vault-server-address&gt;:8200&quot;)<br>    .header(&quot;X-Vault-Token&quot;, &quot;&lt;your-token&gt;&quot;)</pre><pre>val users = scenario(&quot;Users&quot;).exec(PutKV.putKV)<br>  // val users = scenario(&quot;Users&quot;).exec(GetKV.getKV)</pre><pre>setUp(<br>    users.inject(rampUsers(&lt;number-of-concurrent-users&gt;) during (1 seconds))<br>  ).protocols(httpProtocol)<br>}</pre><p>A bit explaination about the following code, it basically just send requests against the provided urls within the given peroid and record the response time, give you a summarized report as shown below. You will get a similar result to this, change the number of users to find your cluster’s limitation.</p><pre>---- Users ---------------------------------------------------------[###########################################################]100%           waiting: 0      / active: 0      / done: 260    ====================================================================  Simulation computerdatabase.advanced.MyTest completed in 8 seconds Parsing log file(s)... Parsing log file(s) done Generating reports...  ==================================================================== ---- Global Information -------------------------------------------- &gt; request count                            260 (OK=255    KO=5     ) &gt; min response time                          2 (OK=3100   KO=2     ) &gt; max response time                       6572 (OK=6572   KO=3079  ) &gt; mean response time                      3416 (OK=3457   KO=1304  ) &gt; std deviation                            549 (OK=438    KO=1161  ) &gt; response time 50th percentile           3394 (OK=3394   KO=1127  ) &gt; response time 75th percentile           3458 (OK=3460   KO=2110  ) &gt; response time 95th percentile           3547 (OK=3547   KO=2885  ) &gt; response time 99th percentile           6252 (OK=6253   KO=3040  ) &gt; mean requests/sec                     28.889 (OK=28.333 KO=0.556 ) ---- Response Time Distribution ------------------------------------ &gt; t &lt; 800 ms                                               0 (  0%) &gt; 800 ms &lt; t &lt; 1200 ms                                     0 (  0%) &gt; t &gt; 1200 ms                                            255 ( 98%) &gt; failed                                                   5 (  2%) ---- Errors -------------------------------------------------------- &gt; j.n.c.ClosedChannelException                            5 (100.0%) ====================================================================</pre><p>As we can see the mean number of requests per second is 28.889.</p><p>This example is currently tested against a test environment, will be implemented in prod once the CR is approved 😆.</p><p>The end.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c02e76de895" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>