|
| 1 | +// Copyright The OpenTelemetry Authors |
| 2 | +// SPDX-License-Identifier: Apache-2.0 |
| 3 | + |
| 4 | +// <auto-generated>This file has been auto generated from 'src\OpenTelemetry.SemanticConventions\scripts\templates\registry\SemanticConventionsAttributes.cs.j2' </auto-generated> |
| 5 | + |
| 6 | +#nullable enable |
| 7 | + |
| 8 | +#pragma warning disable CS1570 // XML comment has badly formed XML |
| 9 | + |
| 10 | +namespace OpenTelemetry.SemanticConventions; |
| 11 | + |
| 12 | +/// <summary> |
| 13 | +/// Constants for semantic attribute names outlined by the OpenTelemetry specifications. |
| 14 | +/// </summary> |
| 15 | +public static class CloudfoundryAttributes |
| 16 | +{ |
| 17 | + /// <summary> |
| 18 | + /// The guid of the application. |
| 19 | + /// </summary> |
| 20 | + /// <remarks> |
| 21 | + /// Application instrumentation should use the value from environment |
| 22 | + /// variable <c>VCAP_APPLICATION.application_id</c>. This is the same value as |
| 23 | + /// reported by <c>cf app <app-name> --guid</c>. |
| 24 | + /// </remarks> |
| 25 | + public const string AttributeCloudfoundryAppId = "cloudfoundry.app.id"; |
| 26 | + |
| 27 | + /// <summary> |
| 28 | + /// The index of the application instance. 0 when just one instance is active. |
| 29 | + /// </summary> |
| 30 | + /// <remarks> |
| 31 | + /// CloudFoundry defines the <c>instance_id</c> in the <a href="https://github.com/cloudfoundry/loggregator-api#v2-envelope">Loggegator v2 envelope</a>. |
| 32 | + /// It is used for logs and metrics emitted by CloudFoundry. It is |
| 33 | + /// supposed to contain the application instance index for applications |
| 34 | + /// deployed on the runtime. |
| 35 | + /// <p> |
| 36 | + /// Application instrumentation should use the value from environment |
| 37 | + /// variable <c>CF_INSTANCE_INDEX</c>. |
| 38 | + /// </remarks> |
| 39 | + public const string AttributeCloudfoundryAppInstanceId = "cloudfoundry.app.instance.id"; |
| 40 | + |
| 41 | + /// <summary> |
| 42 | + /// The name of the application. |
| 43 | + /// </summary> |
| 44 | + /// <remarks> |
| 45 | + /// Application instrumentation should use the value from environment |
| 46 | + /// variable <c>VCAP_APPLICATION.application_name</c>. This is the same value |
| 47 | + /// as reported by <c>cf apps</c>. |
| 48 | + /// </remarks> |
| 49 | + public const string AttributeCloudfoundryAppName = "cloudfoundry.app.name"; |
| 50 | + |
| 51 | + /// <summary> |
| 52 | + /// The guid of the CloudFoundry org the application is running in. |
| 53 | + /// </summary> |
| 54 | + /// <remarks> |
| 55 | + /// Application instrumentation should use the value from environment |
| 56 | + /// variable <c>VCAP_APPLICATION.org_id</c>. This is the same value as |
| 57 | + /// reported by <c>cf org <org-name> --guid</c>. |
| 58 | + /// </remarks> |
| 59 | + public const string AttributeCloudfoundryOrgId = "cloudfoundry.org.id"; |
| 60 | + |
| 61 | + /// <summary> |
| 62 | + /// The name of the CloudFoundry organization the app is running in. |
| 63 | + /// </summary> |
| 64 | + /// <remarks> |
| 65 | + /// Application instrumentation should use the value from environment |
| 66 | + /// variable <c>VCAP_APPLICATION.org_name</c>. This is the same value as |
| 67 | + /// reported by <c>cf orgs</c>. |
| 68 | + /// </remarks> |
| 69 | + public const string AttributeCloudfoundryOrgName = "cloudfoundry.org.name"; |
| 70 | + |
| 71 | + /// <summary> |
| 72 | + /// The UID identifying the process. |
| 73 | + /// </summary> |
| 74 | + /// <remarks> |
| 75 | + /// Application instrumentation should use the value from environment |
| 76 | + /// variable <c>VCAP_APPLICATION.process_id</c>. It is supposed to be equal to |
| 77 | + /// <c>VCAP_APPLICATION.app_id</c> for applications deployed to the runtime. |
| 78 | + /// For system components, this could be the actual PID. |
| 79 | + /// </remarks> |
| 80 | + public const string AttributeCloudfoundryProcessId = "cloudfoundry.process.id"; |
| 81 | + |
| 82 | + /// <summary> |
| 83 | + /// The type of process. |
| 84 | + /// </summary> |
| 85 | + /// <remarks> |
| 86 | + /// CloudFoundry applications can consist of multiple jobs. Usually the |
| 87 | + /// main process will be of type <c>web</c>. There can be additional background |
| 88 | + /// tasks or side-cars with different process types. |
| 89 | + /// </remarks> |
| 90 | + public const string AttributeCloudfoundryProcessType = "cloudfoundry.process.type"; |
| 91 | + |
| 92 | + /// <summary> |
| 93 | + /// The guid of the CloudFoundry space the application is running in. |
| 94 | + /// </summary> |
| 95 | + /// <remarks> |
| 96 | + /// Application instrumentation should use the value from environment |
| 97 | + /// variable <c>VCAP_APPLICATION.space_id</c>. This is the same value as |
| 98 | + /// reported by <c>cf space <space-name> --guid</c>. |
| 99 | + /// </remarks> |
| 100 | + public const string AttributeCloudfoundrySpaceId = "cloudfoundry.space.id"; |
| 101 | + |
| 102 | + /// <summary> |
| 103 | + /// The name of the CloudFoundry space the application is running in. |
| 104 | + /// </summary> |
| 105 | + /// <remarks> |
| 106 | + /// Application instrumentation should use the value from environment |
| 107 | + /// variable <c>VCAP_APPLICATION.space_name</c>. This is the same value as |
| 108 | + /// reported by <c>cf spaces</c>. |
| 109 | + /// </remarks> |
| 110 | + public const string AttributeCloudfoundrySpaceName = "cloudfoundry.space.name"; |
| 111 | + |
| 112 | + /// <summary> |
| 113 | + /// A guid or another name describing the event source. |
| 114 | + /// </summary> |
| 115 | + /// <remarks> |
| 116 | + /// CloudFoundry defines the <c>source_id</c> in the <a href="https://github.com/cloudfoundry/loggregator-api#v2-envelope">Loggregator v2 envelope</a>. |
| 117 | + /// It is used for logs and metrics emitted by CloudFoundry. It is |
| 118 | + /// supposed to contain the component name, e.g. "gorouter", for |
| 119 | + /// CloudFoundry components. |
| 120 | + /// <p> |
| 121 | + /// When system components are instrumented, values from the |
| 122 | + /// <a href="https://bosh.io/docs/jobs/#properties-spec">Bosh spec</a> |
| 123 | + /// should be used. The <c>system.id</c> should be set to |
| 124 | + /// <c>spec.deployment/spec.name</c>. |
| 125 | + /// </remarks> |
| 126 | + public const string AttributeCloudfoundrySystemId = "cloudfoundry.system.id"; |
| 127 | + |
| 128 | + /// <summary> |
| 129 | + /// A guid describing the concrete instance of the event source. |
| 130 | + /// </summary> |
| 131 | + /// <remarks> |
| 132 | + /// CloudFoundry defines the <c>instance_id</c> in the <a href="https://github.com/cloudfoundry/loggregator-api#v2-envelope">Loggregator v2 envelope</a>. |
| 133 | + /// It is used for logs and metrics emitted by CloudFoundry. It is |
| 134 | + /// supposed to contain the vm id for CloudFoundry components. |
| 135 | + /// <p> |
| 136 | + /// When system components are instrumented, values from the |
| 137 | + /// <a href="https://bosh.io/docs/jobs/#properties-spec">Bosh spec</a> |
| 138 | + /// should be used. The <c>system.instance.id</c> should be set to <c>spec.id</c>. |
| 139 | + /// </remarks> |
| 140 | + public const string AttributeCloudfoundrySystemInstanceId = "cloudfoundry.system.instance.id"; |
| 141 | +} |
0 commit comments