From 1577088b4fa3f310d26912e4083e3878bcf771fd Mon Sep 17 00:00:00 2001 From: gnunn1 Date: Fri, 5 Jan 2024 19:32:48 +0000 Subject: [PATCH] =?UTF-8?q?[CI]=20Publish=20Documentation=20for=20f2af83c0?= =?UTF-8?q?3bcbef70ea77bf22d87d385f08ada9c9=20-=20f2af83c03bcbef70ea77bf22?= =?UTF-8?q?d87d385f08ada9c9=20=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- argo-rollouts-workshop/main/04-analysis.html | 11 +++++------ sitemap.xml | 14 +++++++------- 2 files changed, 12 insertions(+), 13 deletions(-) diff --git a/argo-rollouts-workshop/main/04-analysis.html b/argo-rollouts-workshop/main/04-analysis.html index a5f7095..dcaa2c0 100644 --- a/argo-rollouts-workshop/main/04-analysis.html +++ b/argo-rollouts-workshop/main/04-analysis.html @@ -347,12 +347,12 @@

A
-

In the metrics provider section we can see we have two providers defined, one that uses the web metric provider to pull +

In the metrics provider section we can see we have two providers defined, one that uses the prometheus metric provider to pull metrics from Thanos, an aggregator for Prometheus data, and a job that runs Apache Siege to drive some load on the application.

-

The count and interval fields in the success-rate metric powered by the web provider indicate that the metric will be checked four times +

The count and interval fields in the success-rate metric powered by the prometheus provider indicate that the metric will be checked four times with a thirty second interval between each check. The failureLimit determines how many failures are permitted for the rollout to be considered a success, here we set a failure limit of 0.

@@ -363,16 +363,15 @@

A

In the arguments we are taking three arguments, route-name, route-url and namespace, which will be passed from the -Rollout. These are used to parameterize the AnalysisTemplate to improve reusability. These arguments are then referenced in -the AnalysisTemplate using a syntax of {{args.<argument-name>}}.

+Rollout.

The route-name and namespace arguments are used in the prometheus metrics provider in the query field to specify -the route to fetch the status of the HTTP return codes. This query returns the increased rate of HTTP error codes (5xx) +the specific route to fetch the status of the HTTP return codes. This query returns the increased rate of HTTP error codes (5xx) over a 1 minute interval.

-

The route-url parameter is being used in the second provider, the job, where we will be creating load against. This +

The route-url parameter is being used in the second provider, the job, where we will be creating load against the route. This parameter is used to specify the OpenShift route URL where we want to drive the load, i.e the URL that siege will be hitting when it generates load.

diff --git a/sitemap.xml b/sitemap.xml index 3c5552a..74993bb 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2,30 +2,30 @@ https://openshiftdemos.github.io/argo-rollouts-workshop/argo-rollouts-workshop/main/01-getting-started.html -2024-01-05T16:51:45.253Z +2024-01-05T19:32:22.312Z https://openshiftdemos.github.io/argo-rollouts-workshop/argo-rollouts-workshop/main/02-workshop-overview.html -2024-01-05T16:51:45.253Z +2024-01-05T19:32:22.312Z https://openshiftdemos.github.io/argo-rollouts-workshop/argo-rollouts-workshop/main/03-bluegreen-rollout.html -2024-01-05T16:51:45.253Z +2024-01-05T19:32:22.312Z https://openshiftdemos.github.io/argo-rollouts-workshop/argo-rollouts-workshop/main/04-analysis.html -2024-01-05T16:51:45.253Z +2024-01-05T19:32:22.312Z https://openshiftdemos.github.io/argo-rollouts-workshop/argo-rollouts-workshop/main/05-canary-rollout.html -2024-01-05T16:51:45.253Z +2024-01-05T19:32:22.312Z https://openshiftdemos.github.io/argo-rollouts-workshop/argo-rollouts-workshop/main/06-conclusion.html -2024-01-05T16:51:45.253Z +2024-01-05T19:32:22.312Z https://openshiftdemos.github.io/argo-rollouts-workshop/argo-rollouts-workshop/main/index.html -2024-01-05T16:51:45.253Z +2024-01-05T19:32:22.312Z