open-telemetry
/
semantic-conventions
mirror of https://github.com/open-telemetry/semantic-conventions.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add link from FaaS trace to resource attributes (#2256)

This commit is contained in:
Armin Ruech 2022-01-10 19:00:53 +01:00 committed by GitHub
parent 6ecce73b9b
commit 5799c847fb
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specification/trace/semantic_conventions/faas.md
View File

@ -77,7 +77,7 @@ For performance reasons (e.g. [AWS lambda], or [Azure functions]), FaaS provider
Developers exploit this fact to solve the **cold start** issue, caching expensive resource computations between different function executions. Developers exploit this fact to solve the **cold start** issue, caching expensive resource computations between different function executions.
Furthermore, FaaS providers encourage this behavior, e.g. [Google functions]. Furthermore, FaaS providers encourage this behavior, e.g. [Google functions].
This field MAY be set to help correlate function executions that belong to the same execution environment. This field MAY be set to help correlate function executions that belong to the same execution environment.
The span attribute `faas.execution` differs from the resource attribute `faas.instance` in the following: The span attribute `faas.execution` differs from the [resource attribute][FaaS resource attributes] `faas.instance` in the following:
- `faas.execution` refers to the current request ID handled by the function; - `faas.execution` refers to the current request ID handled by the function;
- `faas.instance` refers to the execution environment ID of the function. - `faas.instance` refers to the execution environment ID of the function.