-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
created a new zero-code folder with and zero code svg image
- Loading branch information
1 parent
ede1b99
commit 0b5a92c
Showing
2 changed files
with
55 additions
and
0 deletions.
There are no files selected for viewing
54 changes: 54 additions & 0 deletions
54
content/en/docs/concepts/instrumentation/zero-code/_index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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/) |
1 change: 1 addition & 0 deletions
1
content/en/docs/concepts/instrumentation/zero-code/zero-code.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.