diff --git a/.gitbook/assets/image (26).png b/.gitbook/assets/image (26).png new file mode 100644 index 0000000..3671922 Binary files /dev/null and b/.gitbook/assets/image (26).png differ diff --git a/SUMMARY.md b/SUMMARY.md index 24921a8..52320d3 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -1,6 +1,7 @@ # Table of contents * [Welcome to the Digma Docs!](README.md) +* [What is a Continuous Feedback platform?](what-is-a-continuous-feedback-platform.md) ## Installation diff --git a/what-is-a-continuous-feedback-platform.md b/what-is-a-continuous-feedback-platform.md new file mode 100644 index 0000000..d220323 --- /dev/null +++ b/what-is-a-continuous-feedback-platform.md @@ -0,0 +1,7 @@ +# What is a Continuous Feedback platform? + +Digma's focus is analyzing observability. The basic premise is that there is a lot of useful information in logs traces and metrics - they just require a lot more processing to glean any insights you can actually use as a developer. You can think of Digma as a data pipeline. Its main concern is not storing a lot of raw data but aggregating and processing it continuously, looking for anomalies, changes, and useful analytics. + +Digma ingests observability based on the [OTEL standard](https://opentelemetry.io/) (which it can also automatically collect using the IDE), processes the data, and then exposes insights to the IDE plugin which can map and connect it with the code. + +