### Example Usage of HOST_IMAGE_VERSION Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.HOST_IMAGE_VERSION.html An example value for the host.image.version attribute. ```text "0.1" ``` -------------------------------- ### Example APP_INSTALLATION_ID Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.APP_INSTALLATION_ID.html This is an example of a valid value for the APP_INSTALLATION_ID attribute. It represents a unique installation identifier. ```string "2ab2916d-a51f-4ac8-80ee-45ac31a28092" ``` -------------------------------- ### Example Usage of PROCESS_EXECUTABLE_PATH Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.PROCESS_EXECUTABLE_PATH.html Illustrates an example value for the process executable path. ```text "/usr/bin/cmd/otelcol" ``` -------------------------------- ### Example Oracle DB Instance Names Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.ORACLE_DB_INSTANCE_NAME.html Illustrates example values for the `oracle.db.instance.name` attribute. These represent unique instance names in an Oracle RAC setup. ```text "ORCL1" ``` ```text "ORCL2" ``` ```text "ORCL3" ``` -------------------------------- ### Example Filesystem Mount Point Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.SYSTEM_FILESYSTEM_MOUNTPOINT.html Provides an example value for the system.filesystem.mountpoint attribute. ```text "/mnt/data" ``` -------------------------------- ### Example Usage of TELEMETRY_DISTRO_NAME Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.TELEMETRY_DISTRO_NAME.html Illustrates an example value for the `telemetry.distro.name` attribute, which should be a string starting with 'opentelemetry-'. ```text "parts-unlimited-java" ``` -------------------------------- ### AWS DynamoDB Exclusive Start Table Example Source: https://docs.rs/opentelemetry-semantic-conventions/latest/src/opentelemetry_semantic_conventions/attribute.rs.html Demonstrates the format for specifying the starting table name for paginated AWS DynamoDB requests. ```json "Users" ``` ```json "CatsTable" ``` -------------------------------- ### Example Usage of BROWSER_DOCUMENT_URL_FULL Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.BROWSER_DOCUMENT_URL_FULL.html An example of a full browser document URL. ```text "https://www.example.com/search?q=OpenTelemetry#SemConv" ``` -------------------------------- ### Example DNS Question Names Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.DNS_QUESTION_NAME.html Illustrates example values for the dns.question.name attribute. ```text "www.example.com" ``` ```text "opentelemetry.io" ``` -------------------------------- ### Example Values for HOST_CPU_STEPPING Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.HOST_CPU_STEPPING.html Provides example string values for the host CPU stepping attribute. ```text "1" ``` ```text "r1p1" ``` -------------------------------- ### Example Label Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_PERSISTENTVOLUME_LABEL.html Provides example values for Kubernetes PersistentVolume labels. ```text "ssd" ``` ```text "" ``` -------------------------------- ### Example PROCESS_CREATION_TIME Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.PROCESS_CREATION_TIME.html An example of the expected ISO 8601 formatted string for process creation time. ```text "2023-11-21T09:25:34.853Z" ``` -------------------------------- ### Example URL Subdomain Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.URL_SUBDOMAIN.html Illustrates example values for the URL_SUBDOMAIN attribute. These examples show how subdomains are represented, including multi-level subdomains. ```text "east" ``` ```text "sub2.sub1" ``` -------------------------------- ### Example ARTIFACT_PURL Usage Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.ARTIFACT_PURL.html Illustrates example Package URLs for different artifact types. ```text "pkg:github/package-url/purl-spec@1209109710924" ``` ```text "pkg:npm/foo@12.12.3" ``` -------------------------------- ### Example ARTIFACT_VERSION Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.ARTIFACT_VERSION.html Examples of string values that can be used for ARTIFACT_VERSION. ```text "v0.1.0" ``` ```text "1.2.1" ``` ```text "122691-build" ``` -------------------------------- ### Example Value: 'in' Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.SYSTEM_PAGING_DIRECTION.html Illustrates an example value for the system paging direction. ```text "in" ``` -------------------------------- ### Example Annotation Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_CRONJOB_ANNOTATION.html Provides example values for CronJob annotations. ```text "4" ``` ```text "" ``` -------------------------------- ### Example DaemonSet Label Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_DAEMONSET_LABEL.html Provides example values for Kubernetes DaemonSet labels. ```text "guestbook" ``` ```text "" ``` -------------------------------- ### AWS DynamoDB Attributes to Get Example Source: https://docs.rs/opentelemetry-semantic-conventions/latest/src/opentelemetry_semantic_conventions/attribute.rs.html Shows the format for specifying attributes to retrieve in an AWS DynamoDB request. ```json [ "lives", "id", ] ``` -------------------------------- ### Example Usage of DEPLOYMENT_NAME Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.DEPLOYMENT_NAME.html Examples of string values that can be used for the deployment name. ```text "deploy my app" ``` ```text "deploy-frontend" ``` -------------------------------- ### Example Annotation Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_STATEFULSET_ANNOTATION.html Provides example values for StatefulSet annotations. ```text "1" ``` ```text "" ``` -------------------------------- ### Example HOST_ID Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.HOST_ID.html An example of a unique host ID value. ```text "fdbf79e8af94cb7f9e8df36789187052" ``` -------------------------------- ### Example Usage of PROCESS_RUNTIME_DESCRIPTION Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.PROCESS_RUNTIME_DESCRIPTION.html Illustrates an example value for the `process.runtime.description` attribute, indicating a specific runtime environment. ```text "Eclipse OpenJ9 Eclipse OpenJ9 VM openj9-0.21.0" ``` -------------------------------- ### Example VCS Reference Names Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.VCS_REF_BASE_NAME.html Illustrates example values for the VCS_REF_BASE_NAME, showing branch and tag names. ```text "my-feature-branch" ``` ```text "tag-1-test" ``` -------------------------------- ### Example Usage of CLOUDFOUNDRY_SPACE_NAME Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.CLOUDFOUNDRY_SPACE_NAME.html Provides an example of the expected value for the CloudFoundry space name. ```string "my-space-name" ``` -------------------------------- ### Example Usage of K8S_POD_START_TIME Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_POD_START_TIME.html An example of the expected string format for the K8S_POD_START_TIME attribute, which should be in ISO 8601 format. ```text "2025-12-04T08:41:03Z" ``` -------------------------------- ### Example Value for NETWORK_CONNECTION_STATE Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.NETWORK_CONNECTION_STATE.html Provides an example value for the network connection state. ```text "close_wait" ``` -------------------------------- ### Example OS Names Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.USER_AGENT_OS_NAME.html Illustrative examples of operating system names that can be used with the USER_AGENT_OS_NAME attribute. ```text "iOS" ``` ```text "Android" ``` ```text "Ubuntu" ``` -------------------------------- ### Example Annotation Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_PERSISTENTVOLUMECLAIM_ANNOTATION.html Provides example values for Kubernetes PersistentVolumeClaim annotations. ```text "kubernetes.io/aws-ebs" ``` ```text "" ``` -------------------------------- ### Example Values for DEPLOYMENT_ENVIRONMENT Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.DEPLOYMENT_ENVIRONMENT.html These are example string values that could be used for the deprecated `DEPLOYMENT_ENVIRONMENT` attribute. ```text "staging" ``` ```text "production" ``` -------------------------------- ### Example PDB Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.ORACLE_DB_PDB.html Illustrates example string values for the ORACLE_DB_PDB attribute. ```text "PDB1" ``` ```text "FREEPDB" ``` -------------------------------- ### Example Usage of TEST_SUITE_NAME Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.TEST_SUITE_NAME.html An example demonstrating the usage of the TEST_SUITE_NAME constant with a sample suite name. ```string "TestSuite1" ``` -------------------------------- ### Example Filesystem Type Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.SYSTEM_FILESYSTEM_TYPE.html An example value for the system.filesystem.type attribute, indicating the 'ext4' filesystem. ```text "ext4" ``` -------------------------------- ### Example FILE_MODE Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.FILE_MODE.html Illustrates an example value for file mode in octal representation. ```text "0640" ``` -------------------------------- ### Example Usage of K8S_CLUSTER_NAME Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_CLUSTER_NAME.html Illustrates an example value for the Kubernetes cluster name. ```string "opentelemetry-cluster" ``` -------------------------------- ### Example Usage of FILE_EXTENSION Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.FILE_EXTENSION.html Illustrates example values for the FILE_EXTENSION attribute, such as 'png' and 'gz'. ```text "png" ``` ```text "gz" ``` -------------------------------- ### Example Annotation Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_REPLICASET_ANNOTATION.html Provides example values for Kubernetes ReplicaSet annotations that can be recorded as attributes. ```text "0" ``` ```text "" ``` -------------------------------- ### Example Regions for GCP_GCE_INSTANCE_GROUP_MANAGER_REGION Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.GCP_GCE_INSTANCE_GROUP_MANAGER_REGION.html Examples of valid region values for the `gcp.gce.instance_group_manager.region` attribute. ```text "us-central1" ``` ```text "europe-west1" ``` -------------------------------- ### Example Values for CONTAINER_CPU_STATE Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.CONTAINER_CPU_STATE.html Provides example string values for the deprecated `container.cpu.state` attribute. ```text "user" ``` ```text "kernel" ``` -------------------------------- ### Example HOST_CPU_MODEL_ID Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.HOST_CPU_MODEL_ID.html Illustrates example values for the host.cpu.model.id attribute, which can be a numeric string or a more detailed identifier. ```text "6" ``` ```text "9000/778/B180L" ``` -------------------------------- ### Example OS Descriptions Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.OS_DESCRIPTION.html These examples illustrate the expected format for the 'os.description' attribute value. They are human-readable strings representing OS versions. ```text "Microsoft Windows [Version 10.0.18363.778]" ``` ```text "Ubuntu 18.04.1 LTS" ``` -------------------------------- ### Example Usage of PROCESS_COMMAND Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.PROCESS_COMMAND.html An example of how the PROCESS_COMMAND attribute might be used, showing a typical command string. ```text "cmd/otelcol" ``` -------------------------------- ### Example Deployment ID Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.DEPLOYMENT_ID.html An example value for the `deployment.id` attribute, representing a specific deployment. ```string "1208" ``` -------------------------------- ### Example GEN_AI_SYSTEM_INSTRUCTIONS (Multiple Instructions) Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.GEN_AI_SYSTEM_INSTRUCTIONS.html Illustrates the JSON string format for multiple system instructions. ```json [ { "type": "text", "content": "You are a language translator." }, { "type": "text", "content": "Your mission is to translate text in English to French." } ] ``` -------------------------------- ### Example CLOUDEVENTS_EVENT_ID Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.CLOUDEVENTS_EVENT_ID.html Provides example string values for the CLOUDEVENTS_EVENT_ID. These examples illustrate the expected format for unique event identifiers. ```text "123e4567-e89b-12d3-a456-426614174000" ``` ```text "0001" ``` -------------------------------- ### Example HTTP Route Templates Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.HTTP_ROUTE.html These examples illustrate the expected format for the HTTP_ROUTE attribute, showcasing static and dynamic path segments with optional parameters. ```text "/users/:userID?" ``` ```text "my-controller/my-action/{id?}" ``` -------------------------------- ### Example Usage of container.labels Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.CONTAINER_LABELS.html Example demonstrating the usage of the `container.labels` attribute. Note that this attribute is deprecated. ```text "nginx" ``` -------------------------------- ### JSONRPC_REQUEST_ID Examples Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.JSONRPC_REQUEST_ID.html Examples of string representations for the JSONRPC_REQUEST_ID attribute. ```text "10" ``` ```text "request-7" ``` -------------------------------- ### Example Usage of CICD_PIPELINE_RUN_URL_FULL Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.CICD_PIPELINE_RUN_URL_FULL.html An example of how the CICD_PIPELINE_RUN_URL_FULL attribute can be used with a GitHub Actions URL. ```text "https://github.com/open-telemetry/semantic-conventions/actions/runs/9753949763?pr=1075" ``` -------------------------------- ### Example Usage of SECURITY_RULE_RULESET_NAME Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.SECURITY_RULE_RULESET_NAME.html An example of a value that can be assigned to the security_rule.ruleset.name attribute. ```string "Standard_Protocol_Filters" ``` -------------------------------- ### Example Resource URIs Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.MCP_RESOURCE_URI.html Illustrates example values for the MCP_RESOURCE_URI, including a PostgreSQL database URI and a local file URI. ```text "postgres://database/customers/schema" ``` ```text "file:///home/user/documents/report.pdf" ``` -------------------------------- ### NET_PROTOCOL_NAME Examples Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.NET_PROTOCOL_NAME.html Examples of values that can be used with the deprecated NET_PROTOCOL_NAME attribute. ```text "amqp" ``` ```text "http" ``` ```text "mqtt" ``` -------------------------------- ### Example HTTP User-Agent Strings Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.HTTP_USER_AGENT.html Illustrates common formats for the HTTP User-Agent header. Use `user_agent.original` for new instrumentation. ```text "CERN-LineMode/2.15 libwww/2.17b3" ``` ```text "Mozilla/5.0 (iPhone; CPU iPhone OS 14_7_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.2 Mobile/15E148 Safari/604.1" ``` -------------------------------- ### Example GCP_GCE_INSTANCE_HOSTNAME Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.GCP_GCE_INSTANCE_HOSTNAME.html Illustrates example values for the GCP_GCE_INSTANCE_HOSTNAME attribute, representing different hostname formats. ```text "my-host1234.example.com" ``` ```text "sample-vm.us-west1-b.c.my-project.internal" ``` -------------------------------- ### Example Usage of CODE_FILE_PATH Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.CODE_FILE_PATH.html An example of how the CODE_FILE_PATH attribute can be used to specify a file path. ```string "/usr/local/MyApplication/content_root/app/index.php" ``` -------------------------------- ### Example Usage of CONTAINER_COMMAND_LINE Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.CONTAINER_COMMAND_LINE.html Illustrates the expected format for the container command line attribute. ```text "otelcontribcol --config config.yaml" ``` -------------------------------- ### Example Usage of GEO_POSTAL_CODE Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.GEO_POSTAL_CODE.html Illustrates an example value for the geo.postal_code attribute. ```string "94040" ``` -------------------------------- ### Example Parameter Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.DB_QUERY_PARAMETER.html Provides examples of string representations for database query parameter values. ```text "someval" ``` ```text "55" ``` -------------------------------- ### Example Usage of FEATURE_FLAG_CONTEXT_ID Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.FEATURE_FLAG_CONTEXT_ID.html Illustrates an example value for FEATURE_FLAG_CONTEXT_ID, which is a UUID. ```string "5157782b-2203-4c80-a857-dbbd5e7761db" ``` -------------------------------- ### Example User Agent Versions Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.USER_AGENT_VERSION.html Illustrates example values for the user agent version, typically extracted from original user-agent strings. ```text "14.1.2" ``` ```text "1.0.0" ``` -------------------------------- ### Example Usage of ZOS_SMF_ID Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.ZOS_SMF_ID.html Illustrates an example value for the ZOS_SMF_ID, representing a z/OS system identifier. ```text "SYS1" ``` -------------------------------- ### Example Usage of AWS_ECS_TASK_REVISION Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.AWS_ECS_TASK_REVISION.html Illustrates example values for the AWS_ECS_TASK_REVISION attribute. ```text "8" ``` ```text "26" ``` -------------------------------- ### Example Usage of RPC_CONNECT_RPC_REQUEST_METADATA Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.RPC_CONNECT_RPC_REQUEST_METADATA.html This example demonstrates the expected format for the `RPC_CONNECT_RPC_REQUEST_METADATA` attribute value, which is an array of strings. ```json [ "1.2.3.4", "1.2.3.5", ] ``` -------------------------------- ### Example ARTIFACT_HASH Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.ARTIFACT_HASH.html An example of a full hash value for an artifact. ```text "9ff4c52759e2c4ac70b7d517bc7fcdc1cda631ca0045271ddd1b192544f8a3e9" ``` -------------------------------- ### Example Usage of PROCESS_EXECUTABLE_BUILD_ID_GNU Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.PROCESS_EXECUTABLE_BUILD_ID_GNU.html An example value for the process.executable.build_id.gnu attribute, representing a typical GNU build ID. ```text "c89b11207f6479603b0d49bf291c092c2b719293" ``` -------------------------------- ### Example FAAS_CRON Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.FAAS_CRON.html Provides an example of a valid Cron Expression string that can be used with the FAAS_CRON attribute. This specific example represents a schedule that runs every 5 minutes. ```text "0/5 * * * ? *" ``` -------------------------------- ### Example Usage of HOST_NAME Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.HOST_NAME.html Illustrates how to use the HOST_NAME attribute with a sample value. ```text "opentelemetry-test" ``` -------------------------------- ### Example Attestation Filenames Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.ARTIFACT_ATTESTATION_FILENAME.html Illustrates various valid filename formats for artifact attestations, including those for Go binaries, Docker images, and generic tarballs. ```text "golang-binary-amd64-v0.1.0.attestation" ``` ```text "docker-image-amd64-v0.1.0.intoto.json1" ``` ```text "release-1.tar.gz.attestation" ``` ```text "file-name-package.tar.gz.intoto.json1" ``` -------------------------------- ### AWS DynamoDB Count Example Source: https://docs.rs/opentelemetry-semantic-conventions/latest/src/opentelemetry_semantic_conventions/attribute.rs.html An example of the 'Count' response parameter from an AWS DynamoDB operation. ```json 10 ``` -------------------------------- ### Example Usage of SECURITY_RULE_DESCRIPTION Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.SECURITY_RULE_DESCRIPTION.html An example string value for the security rule description. ```text "Block requests to public DNS over HTTPS / TLS protocols" ``` -------------------------------- ### Example GEN_AI_SYSTEM_INSTRUCTIONS (Single Instruction) Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.GEN_AI_SYSTEM_INSTRUCTIONS.html Illustrates the JSON string format for a single system instruction. ```json [ { "type": "text", "content": "You are an Agent that greet users, always use greetings tool to respond" } ] ``` -------------------------------- ### Example Network Protocol Versions Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.NETWORK_PROTOCOL_VERSION.html Illustrates common string values for the network.protocol.version attribute. ```text "1.1" ``` ```text "2" ``` -------------------------------- ### Example Usage of MESSAGING_MESSAGE_CONVERSATION_ID Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.MESSAGING_MESSAGE_CONVERSATION_ID.html Example of how to use the MESSAGING_MESSAGE_CONVERSATION_ID attribute with a string value. ```string "MyConversationId" ``` -------------------------------- ### AWS DynamoDB Consumed Capacity Example Source: https://docs.rs/opentelemetry-semantic-conventions/latest/src/opentelemetry_semantic_conventions/attribute.rs.html Provides an example of the JSON-serialized consumed capacity response from AWS DynamoDB. ```json [ "{ \"CapacityUnits\": number, \"GlobalSecondaryIndexes\": { \"string\" : { \"CapacityUnits\": number, \"ReadCapacityUnits\": number, \"WriteCapacityUnits\": number } }, \"LocalSecondaryIndexes\": { \"string\" : { \"CapacityUnits\": number, \"ReadCapacityUnits\": number, \"WriteCapacityUnits\": number } }, \"ReadCapacityUnits\": number, \"Table\": { \"CapacityUnits\": number, \"ReadCapacityUnits\": number, \"WriteCapacityUnits\": number }, \"TableName\": \"string\", \"WriteCapacityUnits\": number }" ] ``` -------------------------------- ### Application Installation ID Attribute Source: https://docs.rs/opentelemetry-semantic-conventions/latest/src/opentelemetry_semantic_conventions/attribute.rs.html A unique identifier for an application installation on a device. Should persist across launches and upgrades. ```rust #[cfg(feature = "semconv_experimental")] pub const APP_INSTALLATION_ID: &str = "app.installation.id"; ``` -------------------------------- ### Example Usage of K8S_SERVICE_NAME Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_SERVICE_NAME.html An example of how the K8S_SERVICE_NAME attribute can be used with a service name. ```text "my-service" ``` -------------------------------- ### AWS DynamoDB Attribute Definitions Example Source: https://docs.rs/opentelemetry-semantic-conventions/latest/src/opentelemetry_semantic_conventions/attribute.rs.html Illustrates the JSON-serialized format for attribute definitions in an AWS DynamoDB request. ```json [ {"AttributeName": "string", "AttributeType": "string"} ] ``` -------------------------------- ### AWS DynamoDB Global Secondary Indexes Example Source: https://docs.rs/opentelemetry-semantic-conventions/latest/src/opentelemetry_semantic_conventions/attribute.rs.html Illustrates the JSON-serialized format for global secondary indexes in an AWS DynamoDB request. ```json [ "{ \"IndexName\": \"string\", \"KeySchema\": [ { \"AttributeName\": \"string\", \"KeyType\": \"string\" } ], \"Projection\": { \"NonKeyAttributes\": [ \"string\" ], \"ProjectionType\": \"string\" }, \"ProvisionedThroughput\": { \"ReadCapacityUnits\": number, \"WriteCapacityUnits\": number } }" ] ``` -------------------------------- ### Example Usage of PPROF_PROFILE_DOC_URL Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.PPROF_PROFILE_DOC_URL.html This example demonstrates how to use the PPROF_PROFILE_DOC_URL attribute with an absolute URL. The URL should point to the documentation for the specific profile type. ```text "http://pprof.example.com/cpu-profile.html" ``` -------------------------------- ### AWS DynamoDB Local Secondary Indexes Example Source: https://docs.rs/opentelemetry-semantic-conventions/latest/src/opentelemetry_semantic_conventions/attribute.rs.html Illustrates the JSON-serialized format for local secondary indexes in an AWS DynamoDB request. ```json [ ``` -------------------------------- ### Example HTTP Request Methods Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.HTTP_REQUEST_METHOD.html Illustrates common string values for the http.request.method attribute. ```text "GET" ``` ```text "POST" ``` ```text "HEAD" ``` -------------------------------- ### AWS DynamoDB Global Secondary Index Updates Example Source: https://docs.rs/opentelemetry-semantic-conventions/latest/src/opentelemetry_semantic_conventions/attribute.rs.html Shows the JSON-serialized format for global secondary index updates in an AWS DynamoDB request. ```json [ "{ \"Create\": { \"IndexName\": \"string\", \"KeySchema\": [ { \"AttributeName\": \"string\", \"KeyType\": \"string\" } ], \"Projection\": { \"NonKeyAttributes\": [ \"string\" ], \"ProjectionType\": \"string\" }, \"ProvisionedThroughput\": { \"ReadCapacityUnits\": number, \"WriteCapacityUnits\": number } }" ] ``` -------------------------------- ### Example: Named Query Parameter Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.DB_QUERY_PARAMETER.html Illustrates how to capture a named query parameter when the query uses a named placeholder like `%(userName)s`. ```text db.query.parameter.userName SHOULD be set to "jdoe". ``` -------------------------------- ### Example Label Values Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_PERSISTENTVOLUMECLAIM_LABEL.html Illustrates example values for labels associated with PersistentVolumeClaims. ```text "my-app" ``` ```text "" ``` -------------------------------- ### Kubernetes Service Type Examples Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_SERVICE_TYPE.html Illustrates common values for the Kubernetes service type attribute. ```text "ClusterIP" ``` ```text "NodePort" ``` ```text "LoadBalancer" ``` -------------------------------- ### Example HW_NETWORK_PHYSICAL_ADDRESS Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.HW_NETWORK_PHYSICAL_ADDRESS.html Provides an example of a physical network address value. ```text "00-90-F5-E9-7B-36" ``` -------------------------------- ### Example Usage of GEO_COUNTRY_ISO_CODE Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.GEO_COUNTRY_ISO_CODE.html Provides an example of a valid value for the geo.country.iso_code attribute. ```text "CA" ``` -------------------------------- ### Example Kubernetes Namespace Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.K8S_NAMESPACE_NAME.html Illustrates the string value for the Kubernetes namespace name. This is typically 'default' if no specific namespace is set. ```text "default" ``` -------------------------------- ### Example Values for GEN_AI_OPENAI_RESPONSE_SERVICE_TIER Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.GEN_AI_OPENAI_RESPONSE_SERVICE_TIER.html These are example string values that can be used for the `gen_ai.openai.response.service_tier` attribute. ```text "scale" ``` ```text "default" ``` -------------------------------- ### Example Exception Messages Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.EXCEPTION_MESSAGE.html These are examples of string values that can be recorded for the EXCEPTION_MESSAGE attribute. ```text "Division by zero" ``` ```text "Can't convert 'int' object to str implicitly" ``` -------------------------------- ### Example Usage of SECURITY_RULE_REFERENCE Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.SECURITY_RULE_REFERENCE.html Illustrates how to use the SECURITY_RULE_REFERENCE attribute with a sample URL. ```text "https://en.wikipedia.org/wiki/DNS_over_TLS" ``` -------------------------------- ### Example Usage of USER_EMAIL Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.USER_EMAIL.html Illustrates how to use the USER_EMAIL constant with a sample email address. ```string "a.einstein@example.com" ``` -------------------------------- ### Example Symbolic Link Target Path Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.FILE_SYMBOLIC_LINK_TARGET_PATH.html Illustrates a typical value for the file.symbolic_link.target_path attribute. ```string "/usr/bin/python3" ``` -------------------------------- ### Example DB_CONNECTION_STRING Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.DB_CONNECTION_STRING.html Provides an example of a value for the deprecated DB_CONNECTION_STRING attribute. ```text "Server=(localdb)\v11.0;Integrated Security=true;" ``` -------------------------------- ### RPC JSON-RPC Request ID Source: https://docs.rs/opentelemetry-semantic-conventions/latest/src/opentelemetry_semantic_conventions/attribute.rs.html Deprecated attribute for JSON-RPC request IDs. Use `jsonrpc.request.id` instead. Examples show string and empty string IDs. ```rust pub const RPC_JSONRPC_REQUEST_ID: &str = "rpc.jsonrpc.request_id"; ``` -------------------------------- ### GCP CLOUD_RESOURCE_ID Example Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.CLOUD_RESOURCE_ID.html Example of a CLOUD_RESOURCE_ID for GCP, representing the resource URI. ```text "//run.googleapis.com/projects/PROJECT_ID/locations/LOCATION_ID/services/SERVICE_ID" ``` -------------------------------- ### Example CloudFoundry Org ID Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.CLOUDFOUNDRY_ORG_ID.html An example of a valid CloudFoundry organization ID. ```text "218fc5a9-a5f1-4b54-aa05-46717d0ab26d" ``` -------------------------------- ### Example Usage of SYSTEM_FILESYSTEM_STATE Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.SYSTEM_FILESYSTEM_STATE.html Illustrates a possible value for the `system.filesystem.state` attribute, indicating a 'used' state. ```text "used" ``` -------------------------------- ### Example Usage of CICD_WORKER_URL_FULL Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.CICD_WORKER_URL_FULL.html Provides an example of a full URL for a CI/CD worker. ```text "https://cicd.example.org/worker/abc123" ``` -------------------------------- ### Example Usage of CASSANDRA_COORDINATOR_ID Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.CASSANDRA_COORDINATOR_ID.html An example of a value for the CASSANDRA_COORDINATOR_ID attribute, representing a UUID. ```text "be13faa2-8574-4d71-926d-27f16cf8a7af" ``` -------------------------------- ### Example ONC/Sun RPC Program Names Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.ONC_RPC_PROGRAM_NAME.html Illustrates example values for the ONC/Sun RPC program name attribute. ```text "portmapper" ``` ```text "nfs" ``` -------------------------------- ### Example Usage of ARTIFACT_ATTESTATION_HASH Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.ARTIFACT_ATTESTATION_HASH.html An example of a value that would be assigned to the artifact.attestation.hash attribute. ```text "1b31dfcd5b7f9267bf2ff47651df1cfb9147b9e4df1f335accf65b4cda498408" ``` -------------------------------- ### Example Usage of ARTIFACT_ATTESTATION_ID Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.ARTIFACT_ATTESTATION_ID.html Shows an example value for the artifact attestation ID. ```string "123" ``` -------------------------------- ### URL_REGISTERED_DOMAIN Examples Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.URL_REGISTERED_DOMAIN.html Illustrates example values for the URL_REGISTERED_DOMAIN attribute, showing how subdomains are excluded. ```text "example.com" ``` ```text "foo.co.uk" ``` -------------------------------- ### Example Ordering Key Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.MESSAGING_GCP_PUBSUB_MESSAGE_ORDERING_KEY.html Illustrates a typical string value for the ordering key attribute. ```text "ordering_key" ``` -------------------------------- ### Example TLS_CLIENT_NOT_AFTER Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.TLS_CLIENT_NOT_AFTER.html Provides an example of a date/time string format for the TLS_CLIENT_NOT_AFTER attribute. ```text "2021-01-01T00:00:00.000Z" ``` -------------------------------- ### File Directory Examples Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.FILE_DIRECTORY.html Illustrates valid formats for the file.directory attribute, including Unix-like paths and Windows paths with drive letters. ```text "/home/user" ``` ```text "C:\\Program Files\\MyApp" ``` -------------------------------- ### Example SERVICE_INSTANCE_ID Value Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.SERVICE_INSTANCE_ID.html An example of a valid UUID string that can be used for the service.instance.id attribute. ```string "627cc493-f310-47de-96bd-71410b7dec09" ``` -------------------------------- ### Example Usage of OTEL_SCOPE_VERSION Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.OTEL_SCOPE_VERSION.html This example demonstrates a typical string value for the OTEL_SCOPE_VERSION attribute. ```text "1.0.0" ``` -------------------------------- ### Example Usage of NETWORK_CARRIER_MCC Source: https://docs.rs/opentelemetry-semantic-conventions/latest/opentelemetry_semantic_conventions/attribute/constant.NETWORK_CARRIER_MCC.html Provides an example value for the mobile carrier country code. ```text "310" ```