|
24 | 24 | | Other | [`cloudfoundry.app.id`](/docs/registry/attributes/cloudfoundry.md) |  | `Recommended` | string | The guid of the application. [1] | `218fc5a9-a5f1-4b54-aa05-46717d0ab26d` | |
25 | 25 | | Other | [`cloudfoundry.app.name`](/docs/registry/attributes/cloudfoundry.md) |  | `Recommended` | string | The name of the application. [2] | `my-app-name` | |
26 | 26 |
|
27 | | - |
28 | 27 | **[1] `cloudfoundry.app.id`:** Application instrumentation should use the value from environment |
29 | 28 | variable `VCAP_APPLICATION.application_id`. This is the same value as |
30 | 29 | reported by `cf app <app-name> --guid`. |
@@ -52,7 +51,6 @@ as reported by `cf apps`. |
52 | 51 | | Other | [`cloudfoundry.org.id`](/docs/registry/attributes/cloudfoundry.md) |  | `Recommended` | string | The guid of the CloudFoundry org the application is running in. [3] | `218fc5a9-a5f1-4b54-aa05-46717d0ab26d` | |
53 | 52 | | Other | [`cloudfoundry.org.name`](/docs/registry/attributes/cloudfoundry.md) |  | `Recommended` | string | The name of the CloudFoundry organization the app is running in. [4] | `my-org-name` | |
54 | 53 |
|
55 | | - |
56 | 54 | **[3] `cloudfoundry.org.id`:** Application instrumentation should use the value from environment |
57 | 55 | variable `VCAP_APPLICATION.org_id`. This is the same value as |
58 | 56 | reported by `cf org <org-name> --guid`. |
@@ -80,7 +78,6 @@ reported by `cf orgs`. |
80 | 78 | | Other | [`cloudfoundry.process.id`](/docs/registry/attributes/cloudfoundry.md) |  | `Recommended` | string | The UID identifying the process. [5] | `218fc5a9-a5f1-4b54-aa05-46717d0ab26d` | |
81 | 79 | | Other | [`cloudfoundry.process.type`](/docs/registry/attributes/cloudfoundry.md) |  | `Recommended` | string | The type of process. [6] | `web` | |
82 | 80 |
|
83 | | - |
84 | 81 | **[5] `cloudfoundry.process.id`:** Application instrumentation should use the value from environment |
85 | 82 | variable `VCAP_APPLICATION.process_id`. It is supposed to be equal to |
86 | 83 | `VCAP_APPLICATION.app_id` for applications deployed to the runtime. |
@@ -109,7 +106,6 @@ tasks or side-cars with different process types. |
109 | 106 | | Other | [`cloudfoundry.space.id`](/docs/registry/attributes/cloudfoundry.md) |  | `Recommended` | string | The guid of the CloudFoundry space the application is running in. [7] | `218fc5a9-a5f1-4b54-aa05-46717d0ab26d` | |
110 | 107 | | Other | [`cloudfoundry.space.name`](/docs/registry/attributes/cloudfoundry.md) |  | `Recommended` | string | The name of the CloudFoundry space the application is running in. [8] | `my-space-name` | |
111 | 108 |
|
112 | | - |
113 | 109 | **[7] `cloudfoundry.space.id`:** Application instrumentation should use the value from environment |
114 | 110 | variable `VCAP_APPLICATION.space_id`. This is the same value as |
115 | 111 | reported by `cf space <space-name> --guid`. |
@@ -137,7 +133,6 @@ reported by `cf spaces`. |
137 | 133 | | Other | [`cloudfoundry.system.id`](/docs/registry/attributes/cloudfoundry.md) |  | `Recommended` | string | A guid or another name describing the event source. [9] | `cf/gorouter` | |
138 | 134 | | Other | [`cloudfoundry.system.instance.id`](/docs/registry/attributes/cloudfoundry.md) |  | `Recommended` | string | A guid describing the concrete instance of the event source. [10] | `218fc5a9-a5f1-4b54-aa05-46717d0ab26d` | |
139 | 135 |
|
140 | | - |
141 | 136 | **[9] `cloudfoundry.system.id`:** CloudFoundry defines the `source_id` in the [Loggregator v2 envelope](https://github.com/cloudfoundry/loggregator-api#v2-envelope). |
142 | 137 | It is used for logs and metrics emitted by CloudFoundry. It is |
143 | 138 | supposed to contain the component name, e.g. "gorouter", for |
|
0 commit comments