From 0b5a92c4a95427c43f0e17f7cc2dd9d70da23dd1 Mon Sep 17 00:00:00 2001 From: mercybassey Date: Tue, 15 Oct 2024 16:25:46 +0100 Subject: [PATCH] created a new zero-code folder with and zero code svg image --- .../instrumentation/zero-code/_index.md | 54 +++++++++++++++++++ .../instrumentation/zero-code/zero-code.svg | 1 + 2 files changed, 55 insertions(+) create mode 100644 content/en/docs/concepts/instrumentation/zero-code/_index.md create mode 100644 content/en/docs/concepts/instrumentation/zero-code/zero-code.svg diff --git a/content/en/docs/concepts/instrumentation/zero-code/_index.md b/content/en/docs/concepts/instrumentation/zero-code/_index.md new file mode 100644 index 000000000000..035bf2952cda --- /dev/null +++ b/content/en/docs/concepts/instrumentation/zero-code/_index.md @@ -0,0 +1,54 @@ +--- +title: Zero-code +description: >- + Learn how to add observability to an application without the need to write + code +weight: 10 +aliases: [automatic] +--- + +As [ops](/docs/getting-started/ops/) you might want to add observability to one +or more applications without having to edit the source. OpenTelemetry lets you +quickly gain some observability for a service without having to use the +OpenTelemetry API & SDK for +[code-based instrumentation](/docs/concepts/instrumentation/code-based). + +![Zero Code](./zero-code.svg) + +Zero-code instrumentation adds the OpenTelemetry API and SDK capabilities to +your application typically as an agent or agent-like installation. The specific +mechanisms involved may differ by language, ranging from bytecode manipulation, +monkey patching, or eBPF to inject calls to the OpenTelemetry API and SDK into +your application. + +Typically, zero-code instrumentation adds instrumentation for the libraries +you're using. This means that requests and responses, database calls, message +queue calls, and so forth are what are instrumented. Your application's code, +however, is not typically instrumented. To instrument your code, you'll need to +use [code-based instrumentation](/docs/concepts/instrumentation/code-based). + +Additionally, zero-code instrumentation lets you configure the +[Instrumentation Libraries](/docs/concepts/instrumentation/libraries) and +[exporters](/docs/concepts/components/#exporters) loaded. + +You can configure zero-code instrumentation through environment variables and +other language-specific mechanisms, such as system properties or arguments +passed to initialization methods. To get started, you only need a service name +configured so that you can identify the service in the observability backend of +your choice. + +Other configuration options are available, including: + +- Data source specific configuration +- Exporter configuration +- Propagator configuration +- Resource configuration + +Automatic instrumentation is available for the following languages: + +- [.NET](/docs/zero-code/net/) +- [Go](/docs/zero-code/go) +- [Java](/docs/zero-code/java/) +- [JavaScript](/docs/zero-code/js/) +- [PHP](/docs/zero-code/php/) +- [Python](/docs/zero-code/python/) diff --git a/content/en/docs/concepts/instrumentation/zero-code/zero-code.svg b/content/en/docs/concepts/instrumentation/zero-code/zero-code.svg new file mode 100644 index 000000000000..4c3f7498fe19 --- /dev/null +++ b/content/en/docs/concepts/instrumentation/zero-code/zero-code.svg @@ -0,0 +1 @@ + \ No newline at end of file