From b9089cae6d6ea1dc71d2c02e8df1f106f2b89132 Mon Sep 17 00:00:00 2001
From: "github-merge-queue[bot]"
For more advanced usage of keramik, please seeAdvanced Topi
Enabling Recon<
-
+
@@ -301,7 +301,7 @@
Enabling Recon<
-
+
diff --git a/analysis.html b/analysis.html
index 23be869f..8f67995a 100644
--- a/analysis.html
+++ b/analysis.html
@@ -82,7 +82,7 @@
diff --git a/create_cluster.html b/create_cluster.html
index 2d5ef0ee..98d1cb04 100644
--- a/create_cluster.html
+++ b/create_cluster.html
@@ -82,7 +82,7 @@
diff --git a/datadog.html b/datadog.html
index 41a939d2..9e27cb66 100644
--- a/datadog.html
+++ b/datadog.html
@@ -82,7 +82,7 @@
diff --git a/deploy_keramik.html b/deploy_keramik.html
index 2285b577..bcb7eab8 100644
--- a/deploy_keramik.html
+++ b/deploy_keramik.html
@@ -82,7 +82,7 @@
diff --git a/developing.html b/developing.html
index e58c7502..3e6f0e44 100644
--- a/developing.html
+++ b/developing.html
@@ -82,7 +82,7 @@
diff --git a/developing_operator.html b/developing_operator.html
index e40f892c..925fe914 100644
--- a/developing_operator.html
+++ b/developing_operator.html
@@ -82,7 +82,7 @@
diff --git a/developing_runner.html b/developing_runner.html
index 4aff76d8..57f12e13 100644
--- a/developing_runner.html
+++ b/developing_runner.html
@@ -82,7 +82,7 @@
diff --git a/environment.html b/environment.html
index adf31583..aadd2313 100644
--- a/environment.html
+++ b/environment.html
@@ -82,7 +82,7 @@
diff --git a/index.html b/index.html
index ef3d1c90..a941b3af 100644
--- a/index.html
+++ b/index.html
@@ -82,7 +82,7 @@
diff --git a/ipfs.html b/ipfs.html
index f9d347dc..2b48a2ea 100644
--- a/ipfs.html
+++ b/ipfs.html
@@ -82,7 +82,7 @@
@@ -282,7 +282,7 @@
CAS
Before running the simulation make sure the network
is ready.
Before running the simulation make sure the network
is ready and has monitoring enabled.
kubectl describe network <unique-name>-small
You should see that the number of Ready Replicas
is the same as the Replicas
.
@@ -303,6 +306,8 @@
You can enable monitoring on a network to deploy jaeger, prometheus and an opentelemetry collector into the network namespace. +This is not the only way to monitor network resources but it is built in.
+Metrics from all pods in the network will be collected.
+Sample network resource with monitoring enabled.
+# basic.yaml
+---
+apiVersion: "keramik.3box.io/v1alpha1"
+kind: Network
+metadata:
+ name: network-with-monitoring
+spec:
+ replicas: 2
+ monitoring:
+ namespaced: true
+
To view the metrics and traces port-forward the services:
kubectl port-forward prometheus-0 9090
kubectl port-forward jaeger-0 16686
Then navigate to http://localhost:9090 for metrics and http://localhost:16686 for traces.
+The opentelemetry collector exposes metrics on two different ports under the otel
service:
Simulations will publish specific summary metrics about the simulation run. +This is typically a collection of metrics per simulation run and is much lighter weight than all metrics from all pods in the network.
+Scrape the otel:9465
endpoint if you want on the simulation metrics.
+NOTE: The prometheus-0 pod will scrape all metrics so you can easily inspect all activity on the network.
+
The IPFS behavior used by CAS and Ceramic can be customized using the same IPFS spec.