From 39d57b49c41695cf6eae655fb3e571ff1cdb227c Mon Sep 17 00:00:00 2001 From: Roni Dover Date: Mon, 18 Mar 2024 05:41:47 +0000 Subject: [PATCH] GITBOOK-34: No subject --- SUMMARY.md | 2 +- digma-core-concepts/environments.md | 11 ++++++++++- .../instrumenting-your-code-from-terminal.md | 2 -- ...menting-your-code-in-ci-staging-or-the-terminal.md | 3 +++ 4 files changed, 14 insertions(+), 4 deletions(-) delete mode 100644 instrumentation/instrumenting-your-code-from-terminal.md create mode 100644 instrumentation/instrumenting-your-code-in-ci-staging-or-the-terminal.md diff --git a/SUMMARY.md b/SUMMARY.md index cdedb68..8372803 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -12,7 +12,7 @@ * [Automatic Instrumentation in the IDE](instrumentation/automatic-instrumentation-in-the-ide/README.md) * [Spring, Spring Boot, Dropwizard and default](instrumentation/automatic-instrumentation-in-the-ide/spring-spring-boot-dropwizard-and-default.md) * [Quarkus, Micronaut](instrumentation/automatic-instrumentation-in-the-ide/quarkus-micronaut.md) -* [Instrumenting your code from terminal](instrumentation/instrumenting-your-code-from-terminal.md) +* [Instrumenting your code in CI/Staging or the terminal](instrumentation/instrumenting-your-code-in-ci-staging-or-the-terminal.md) ## Digma Core Concepts diff --git a/digma-core-concepts/environments.md b/digma-core-concepts/environments.md index 9a78812..0e65a9c 100644 --- a/digma-core-concepts/environments.md +++ b/digma-core-concepts/environments.md @@ -7,4 +7,13 @@ description: >- # Environments -In order to better compare and aggregate data, it is +### Why it's important to have more than one environment + +Digma excels in analyzing observability data, detecting changes, and measuring baselines. Lumping together data from dev, test, load testing, and production would create a huge mess with many strange statistical artifacts. Each time you run a load test you'll notice huge performance degradations while running in debug mode would manifest bugs in code that hasn't yet been checked in. + +To bring some order into this chaos, Digma uses environments as an abstraction to measure data from different deployment stages and use cases separately. + +### How to create environments + +Private environments are easy to create in your local deployment. + diff --git a/instrumentation/instrumenting-your-code-from-terminal.md b/instrumentation/instrumenting-your-code-from-terminal.md deleted file mode 100644 index 8f65814..0000000 --- a/instrumentation/instrumenting-your-code-from-terminal.md +++ /dev/null @@ -1,2 +0,0 @@ -# Instrumenting your code from terminal - diff --git a/instrumentation/instrumenting-your-code-in-ci-staging-or-the-terminal.md b/instrumentation/instrumenting-your-code-in-ci-staging-or-the-terminal.md new file mode 100644 index 0000000..1f81ba2 --- /dev/null +++ b/instrumentation/instrumenting-your-code-in-ci-staging-or-the-terminal.md @@ -0,0 +1,3 @@ +# Instrumenting your code in CI/Staging or the terminal + +If you're running