<?php

// DO NOT EDIT, this is an Auto-generated file from script/semantic-conventions

declare(strict_types=1);

namespace OpenTelemetry\SemConv\Attributes;

/**
 * Semantic attributes and corresponding values for http.
 * @see https://opentelemetry.io/docs/specs/semconv/registry/attributes/http/
 */
interface HttpAttributes
{
    /**
     * HTTP request headers, `<key>` being the normalized HTTP Header name (lowercase), the value being the header values.
     *
     * Instrumentations SHOULD require an explicit configuration of which headers are to be captured.
     * Including all request headers can be a security risk - explicit configuration helps avoid leaking sensitive information.
     *
     * The `User-Agent` header is already captured in the `user_agent.original` attribute.
     * Users MAY explicitly configure instrumentations to capture them even though it is not recommended.
     *
     * The attribute value MUST consist of either multiple header values as an array of strings
     * or a single-item array containing a possibly comma-concatenated string, depending on the way
     * the HTTP library provides access to headers.
     *
     * Examples:
     *
     * - A header `Content-Type: application/json` SHOULD be recorded as the `http.request.header.content-type`
     *   attribute with value `["application/json"]`.
     * - A header `X-Forwarded-For: 1.2.3.4, 1.2.3.5` SHOULD be recorded as the `http.request.header.x-forwarded-for`
     *   attribute with value `["1.2.3.4", "1.2.3.5"]` or `["1.2.3.4, 1.2.3.5"]` depending on the HTTP library.
     *
     * @stable
     */
    public const HTTP_REQUEST_HEADER = 'http.request.header';

    /**
     * HTTP request method.
     * HTTP request method value SHOULD be "known" to the instrumentation.
     * By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
     * the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
     * and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
     *
     * If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
     *
     * If the HTTP instrumentation could end up converting valid HTTP request methods to `_OTHER`, then it MUST provide a way to override
     * the list of known HTTP methods. If this override is done via environment variable, then the environment variable MUST be named
     * OTEL_INSTRUMENTATION_HTTP_KNOWN_METHODS and support a comma-separated list of case-sensitive known HTTP methods
     * (this list MUST be a full override of the default known method, it is not a list of known methods in addition to the defaults).
     *
     * HTTP method names are case-sensitive and `http.request.method` attribute value MUST match a known HTTP method name exactly.
     * Instrumentations for specific web frameworks that consider HTTP methods to be case insensitive, SHOULD populate a canonical equivalent.
     * Tracing instrumentations that do so, MUST also set `http.request.method_original` to the original value.
     *
     * @stable
     */
    public const HTTP_REQUEST_METHOD = 'http.request.method';

    /**
     * CONNECT method.
     * @stable
     */
    public const HTTP_REQUEST_METHOD_VALUE_CONNECT = 'CONNECT';

    /**
     * DELETE method.
     * @stable
     */
    public const HTTP_REQUEST_METHOD_VALUE_DELETE = 'DELETE';

    /**
     * GET method.
     * @stable
     */
    public const HTTP_REQUEST_METHOD_VALUE_GET = 'GET';

    /**
     * HEAD method.
     * @stable
     */
    public const HTTP_REQUEST_METHOD_VALUE_HEAD = 'HEAD';

    /**
     * OPTIONS method.
     * @stable
     */
    public const HTTP_REQUEST_METHOD_VALUE_OPTIONS = 'OPTIONS';

    /**
     * PATCH method.
     * @stable
     */
    public const HTTP_REQUEST_METHOD_VALUE_PATCH = 'PATCH';

    /**
     * POST method.
     * @stable
     */
    public const HTTP_REQUEST_METHOD_VALUE_POST = 'POST';

    /**
     * PUT method.
     * @stable
     */
    public const HTTP_REQUEST_METHOD_VALUE_PUT = 'PUT';

    /**
     * TRACE method.
     * @stable
     */
    public const HTTP_REQUEST_METHOD_VALUE_TRACE = 'TRACE';

    /**
     * Any HTTP method that the instrumentation has no prior knowledge of.
     * @stable
     */
    public const HTTP_REQUEST_METHOD_VALUE_OTHER = '_OTHER';

    /**
     * Original HTTP method sent by the client in the request line.
     *
     * @stable
     */
    public const HTTP_REQUEST_METHOD_ORIGINAL = 'http.request.method_original';

    /**
     * The ordinal number of request resending attempt (for any reason, including redirects).
     *
     * The resend count SHOULD be updated each time an HTTP request gets resent by the client, regardless of what was the cause of the resending (e.g. redirection, authorization failure, 503 Server Unavailable, network issues, or any other).
     *
     * @stable
     */
    public const HTTP_REQUEST_RESEND_COUNT = 'http.request.resend_count';

    /**
     * HTTP response headers, `<key>` being the normalized HTTP Header name (lowercase), the value being the header values.
     *
     * Instrumentations SHOULD require an explicit configuration of which headers are to be captured.
     * Including all response headers can be a security risk - explicit configuration helps avoid leaking sensitive information.
     *
     * Users MAY explicitly configure instrumentations to capture them even though it is not recommended.
     *
     * The attribute value MUST consist of either multiple header values as an array of strings
     * or a single-item array containing a possibly comma-concatenated string, depending on the way
     * the HTTP library provides access to headers.
     *
     * Examples:
     *
     * - A header `Content-Type: application/json` header SHOULD be recorded as the `http.request.response.content-type`
     *   attribute with value `["application/json"]`.
     * - A header `My-custom-header: abc, def` header SHOULD be recorded as the `http.response.header.my-custom-header`
     *   attribute with value `["abc", "def"]` or `["abc, def"]` depending on the HTTP library.
     *
     * @stable
     */
    public const HTTP_RESPONSE_HEADER = 'http.response.header';

    /**
     * [HTTP response status code](https://tools.ietf.org/html/rfc7231#section-6).
     *
     * @stable
     */
    public const HTTP_RESPONSE_STATUS_CODE = 'http.response.status_code';

    /**
     * The matched route template for the request. This MUST be low-cardinality and include all static path segments, with dynamic path segments represented with placeholders.
     *
     * MUST NOT be populated when this is not supported by the HTTP server framework as the route attribute should have low-cardinality and the URI path can NOT substitute it.
     * SHOULD include the [application root](/docs/http/http-spans.md#http-server-definitions) if there is one.
     *
     * A static path segment is a part of the route template with a fixed, low-cardinality value. This includes literal strings like `/users/` and placeholders that
     * are constrained to a finite, predefined set of values, e.g. `{controller}` or `{action}`.
     *
     * A dynamic path segment is a placeholder for a value that can have high cardinality and is not constrained to a predefined list like static path segments.
     *
     * Instrumentations SHOULD use routing information provided by the corresponding web framework. They SHOULD pick the most precise source of routing information and MAY
     * support custom route formatting. Instrumentations SHOULD document the format and the API used to obtain the route string.
     *
     * @stable
     */
    public const HTTP_ROUTE = 'http.route';

}
