- Print
- DarkLight
- PDF
Index Fields
Name | Type | Aggregation | Description |
---|---|---|---|
| text | keyword | HTTP method (GET, PUT, POST, PATHC, DELETE, OPTIONS) |
| text | keyword | A list of UUIDs shared across disparate audit events. This can be used to trace a user’s request path through the network. The first value is the upstream proxy’s UUID. The second value is the UUID of the downstream proxy associated with this audit event. |
| text | keyword | The UUID of the event. This will exist as one of the UUIDs in the |
| text | keyword | The service name associated this event. |
| text | keyword | A list of identities associated with the request. |
| boolean | n/a | A true/false value indicating that the request was successful. |
| text | keyword | The endpoint or route of the request. |
| text | keyword | The host and port of the external ingress. If Greymatter is deployed to Kubernetes, this would be the external LoadBalancer’s host and port. |
| text | keyword | The method of the request. Identical to the |
| text | keyword | The path or route of the request. Identical to the |
| text | keyword | The scheme (aka protocol) of the request. |
| text | keyword | The supported content types of the request such as |
| text | keyword | The supported content encoding, usually compression algorithm, of the request such as |
| text | keyword | The natural language and locale the client prefers such as |
| text | keyword | The directive that controls caching in browsers and shared caches (e.g. Proxies, CDNs). |
| text | keyword | The size of the message body, in bytes, sent to the recipient. |
| text | keyword | The type of content of the resource in the request such as |
| text | keyword | The cookie set by the server that is sent back by the browser. |
| text | keyword | The value of an authenticated user’s email address. This is only used for OIDC authentication where the email address is a JWT claim. |
| text | keyword | The UUID of the audit event of the upstream proxy. This is the first value in the |
| text | keyword | Determines if a request is conditional. |
| text | keyword | Determines if a request is conditional. |
| text | keyword | Indicates the origin (scheme, hostname, and port) that triggered the request. |
| text | keyword | Contains the absolute or partial address from which a resource has been requested. |
| text | keyword | Indicates whether the user consents to a website or service selling or sharing their personal information with third parties. |
| text | keyword | Sends a signal to the server expressing the client's preference for an encrypted and authenticated response, and that it can successfully handle the upgrade-insecure-requests CSP directive. |
| text | keyword | Lets servers and network peers identify the application, operating system, vendor, and/or version of the requesting user agent such as |
| text | keyword | The value of the distinguished name (DN) from a the x509 identity found in the request, manual TLS or Spire. |
| text | keyword | If the route utilizes prefix_rewrite or regex_rewrite, this header will be set to the original path. This can be useful for logging and debugging. |
| text | keyword | It is a common case where a service wants to know what the originating protocol (HTTP or HTTPS) was of the connection terminated by a front/edge proxy. |
| text | keyword | Correlates to the name and port of a domain registered with a proxy such as |
| text | keyword | Correlates to the name of the route registered with a proxy such as |
| text | keyword | A rule associated with a proxy route. Greymatter will always set this to |
| text | keyword | A shared-rule associated with a proxy route. Greymatter will always set this to |
| text | keyword | Used to uniquely identify a request as well as perform stable access logging and tracing. |
| long | n/a | The response code of the HTTP request such as |
| text | keyword | The status code of the request. Correlates with |
| text | keyword | A marker used by the server to advertise its support for partial requests from the client for file downloads. The value of this field indicates the unit that can be used to define a range. |
| text | keyword | The directive that controls caching in browsers and shared caches (e.g. Proxies, CDNs). |
| text | keyword | Controls whether the network connection stays open after the current transaction finishes. If the value sent is keep-alive, the connection is persistent and not closed, allowing for subsequent requests to the same server to be done. |
| text | keyword | Lists any encodings that have been applied to the representation (message payload), and in what order. This lets the recipient know how to decode the representation in order to obtain the original payload format. |
| text | keyword | The size of the message body, in bytes, sent to the recipient. |
| text | keyword | The type of content of the resource in the request such as |
| text | keyword | Contains the date and time at which the message originated |
| text | keyword | An identifier for a specific version of a resource. It lets caches be more efficient and save bandwidth, as a web server does not need to resend a full response if the content was not changed. |
| text | keyword | The UUID of the audit event of the upstream proxy. This is the first value in the |
| text | keyword | Allows the sender to hint about how the connection may be used to set a timeout and a maximum amount of requests. |
| text | keyword | A date and time when the origin server believes the resource was last modified. |
| text | keyword | Indicates the URL to redirect a page to. It only provides a meaning when served with a 3xx (redirection) or 201 (created) status respo nse. |
| text | keyword | Describes the software used by the origin server that handled the request — that is, the server that generated the response. |
| text | keyword | Specifies the form of encoding used to safely transfer the payload body to the user. |
| text | keyword | The value of the distinguished name (DN) from a the x509 identity found in the request, manual TLS or Spire. |
| text | keyword | Describes the parts of the request message aside from the method and URL that influenced the content of the response it occurs in. Most often, this is used to create a cache key when content negotiation is in use. |
| text | keyword | Contains the time in milliseconds spent by the upstream host processing the request and the network latency between the proxy and upstream host. This is useful if the client wants to determine service time compared to network latency between client and proxy. |
| text | keyword | Correlates to the name of the route registered with a proxy such as |
| text | keyword | A rule associated with a proxy route. Greymatter will always set this to |
| text | keyword | A shared-rule associated with a proxy route. Greymatter will always set this to |
| text | keyword | An optional and unofficial HTTP header, used to indicate the technology stack used on the server-side. |
| text | keyword | Used to uniquely identify a request as well as perform stable access logging and tracing. |
| text | keyword | Version of the audit event schema. |
| text | keyword | The IP address of the host of the Greymatter proxy. In Kubernetes, this is the Pod IP. |
| date | n/a | The UNIX timestamp when the audit event was captured. |
For more details on HTTP request/response headers, please refer to the MDN Web Docs .