|
| 1 | +/* |
| 2 | + * Copyright The OpenTelemetry Authors |
| 3 | + * |
| 4 | + * Licensed under the Apache License, Version 2.0 (the "License"); |
| 5 | + * you may not use this file except in compliance with the License. |
| 6 | + * You may obtain a copy of the License at |
| 7 | + * |
| 8 | + * https://www.apache.org/licenses/LICENSE-2.0 |
| 9 | + * |
| 10 | + * Unless required by applicable law or agreed to in writing, software |
| 11 | + * distributed under the License is distributed on an "AS IS" BASIS, |
| 12 | + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| 13 | + * See the License for the specific language governing permissions and |
| 14 | + * limitations under the License. |
| 15 | + */ |
| 16 | + |
| 17 | +//----------------------------------------------------------------------------------------------------------------- |
| 18 | +// DO NOT EDIT, this is an Auto-generated file from scripts/semconv/templates/registry/ts-experimental/events.ts.j2 |
| 19 | +//----------------------------------------------------------------------------------------------------------------- |
| 20 | + |
| 21 | +/** |
| 22 | + * This event represents an instantaneous click on the screen of an application. |
| 23 | + * |
| 24 | + * @note The `app.screen.click` event can be used to indicate that a user has clicked or tapped on the screen portion of an application. Clicks outside of an application's active area **SHOULD NOT** generate this event. This event does not differentiate between touch/mouse down and touch/mouse up. Implementations **SHOULD** give preference to generating this event at the time the click is complete, typically on touch release or mouse up. The location of the click event **MUST** be provided in absolute screen pixels. |
| 25 | + * |
| 26 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 27 | + */ |
| 28 | +export const EVENT_APP_SCREEN_CLICK = 'app.screen.click' as const; |
| 29 | + |
| 30 | +/** |
| 31 | + * This event indicates that an application widget has been clicked. |
| 32 | + * |
| 33 | + * @note Use this event to indicate that visual application component has been clicked, typically through a user's manual interaction. |
| 34 | + * |
| 35 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 36 | + */ |
| 37 | +export const EVENT_APP_WIDGET_CLICK = 'app.widget.click' as const; |
| 38 | + |
| 39 | +/** |
| 40 | + * Deprecated. Use `azure.resource.log` instead. |
| 41 | + * |
| 42 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 43 | + * |
| 44 | + * @deprecated Replaced by `azure.resource.log`. |
| 45 | + */ |
| 46 | +export const EVENT_AZ_RESOURCE_LOG = 'az.resource.log' as const; |
| 47 | + |
| 48 | +/** |
| 49 | + * Describes Azure Resource Log event, see [Azure Resource Log Top-level Schema](https://learn.microsoft.com/azure/azure-monitor/essentials/resource-logs-schema#top-level-common-schema) for more details. |
| 50 | + * |
| 51 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 52 | + */ |
| 53 | +export const EVENT_AZURE_RESOURCE_LOG = 'azure.resource.log' as const; |
| 54 | + |
| 55 | +/** |
| 56 | + * This event describes the website performance metrics introduced by Google, See [web vitals](https://web.dev/vitals). |
| 57 | + * |
| 58 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 59 | + */ |
| 60 | +export const EVENT_BROWSER_WEB_VITAL = 'browser.web_vital' as const; |
| 61 | + |
| 62 | +/** |
| 63 | + * This event represents an occurrence of a lifecycle transition on Android or iOS platform. |
| 64 | + * |
| 65 | + * @note The event body fields **MUST** be used to describe the state of the application at the time of the event. |
| 66 | + * This event is meant to be used in conjunction with `os.name` [resource semantic convention](/docs/resource/os.md) to identify the mobile operating system (e.g. Android, iOS). |
| 67 | + * The `android.app.state` and `ios.app.state` fields are mutually exclusive and **MUST NOT** be used together, each field **MUST** be used with its corresponding `os.name` value. |
| 68 | + * |
| 69 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 70 | + */ |
| 71 | +export const EVENT_DEVICE_APP_LIFECYCLE = 'device.app.lifecycle' as const; |
| 72 | + |
| 73 | +/** |
| 74 | + * Defines feature flag evaluation as an event. |
| 75 | + * |
| 76 | + * @note A `feature_flag.evaluation` event **SHOULD** be emitted whenever a feature flag value is evaluated, which may happen many times over the course of an application lifecycle. For example, a website A/B testing different animations may evaluate a flag each time a button is clicked. A `feature_flag.evaluation` event is emitted on each evaluation even if the result is the same. |
| 77 | + * |
| 78 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 79 | + */ |
| 80 | +export const EVENT_FEATURE_FLAG_EVALUATION = 'feature_flag.evaluation' as const; |
| 81 | + |
| 82 | +/** |
| 83 | + * This event describes the assistant message passed to GenAI system. |
| 84 | + * |
| 85 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 86 | + */ |
| 87 | +export const EVENT_GEN_AI_ASSISTANT_MESSAGE = 'gen_ai.assistant.message' as const; |
| 88 | + |
| 89 | +/** |
| 90 | + * This event describes the Gen AI response message. |
| 91 | + * |
| 92 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 93 | + */ |
| 94 | +export const EVENT_GEN_AI_CHOICE = 'gen_ai.choice' as const; |
| 95 | + |
| 96 | +/** |
| 97 | + * This event describes the system instructions passed to the GenAI model. |
| 98 | + * |
| 99 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 100 | + */ |
| 101 | +export const EVENT_GEN_AI_SYSTEM_MESSAGE = 'gen_ai.system.message' as const; |
| 102 | + |
| 103 | +/** |
| 104 | + * This event describes the response from a tool or function call passed to the GenAI model. |
| 105 | + * |
| 106 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 107 | + */ |
| 108 | +export const EVENT_GEN_AI_TOOL_MESSAGE = 'gen_ai.tool.message' as const; |
| 109 | + |
| 110 | +/** |
| 111 | + * This event describes the user message passed to the GenAI model. |
| 112 | + * |
| 113 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 114 | + */ |
| 115 | +export const EVENT_GEN_AI_USER_MESSAGE = 'gen_ai.user.message' as const; |
| 116 | + |
| 117 | +/** |
| 118 | + * Describes a message sent or received within the context of an RPC call. |
| 119 | + * |
| 120 | + * @note In the lifetime of an RPC stream, an event for each message sent/received on client and server spans **SHOULD** be created. In case of unary calls only one sent and one received message will be recorded for both client and server spans. |
| 121 | + * |
| 122 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 123 | + */ |
| 124 | +export const EVENT_RPC_MESSAGE = 'rpc.message' as const; |
| 125 | + |
| 126 | +/** |
| 127 | + * Indicates that a session has ended. |
| 128 | + * |
| 129 | + * @note For instrumentation that tracks user behavior during user sessions, a `session.end` event **SHOULD** be emitted every time a session ends. When a session ends and continues as a new session, this event **SHOULD** be emitted prior to the `session.start` event. |
| 130 | + * |
| 131 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 132 | + */ |
| 133 | +export const EVENT_SESSION_END = 'session.end' as const; |
| 134 | + |
| 135 | +/** |
| 136 | + * Indicates that a new session has been started, optionally linking to the prior session. |
| 137 | + * |
| 138 | + * @note For instrumentation that tracks user behavior during user sessions, a `session.start` event **MUST** be emitted every time a session is created. When a new session is created as a continuation of a prior session, the `session.previous_id` **SHOULD** be included in the event. The values of `session.id` and `session.previous_id` **MUST** be different. |
| 139 | + * When the `session.start` event contains both `session.id` and `session.previous_id` fields, the event indicates that the previous session has ended. If the session ID in `session.previous_id` has not yet ended via explicit `session.end` event, then the consumer **SHOULD** treat this continuation event as semantically equivalent to `session.end(session.previous_id)` and `session.start(session.id)`. |
| 140 | + * |
| 141 | + * @experimental This event is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`. |
| 142 | + */ |
| 143 | +export const EVENT_SESSION_START = 'session.start' as const; |
| 144 | + |
0 commit comments