Type to search.

HTTP server metricset

Serverless

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

This is the server metricset of the module http.

Events sent to the http endpoint will be put by default under the http.server prefix. To change this use the server.paths config options. In the example below every request to /foo will be put under http.foo. Also consider using secure settings for the server using TLS/SSL as shown

YAML
- module: http
  metricsets: ["server"]
  host: "localhost"
  ssl.certificate: "/etc/pki/server/cert.pem"
  ssl.key: "/etc/pki/server/cert.key"
  port: "8080"
  server.paths:
    - path: "/foo"
      namespace: "foo"

For a description of each field in the metricset, see the exported fields section.

Here is an example document generated by this metricset:

JSON
{
    "@timestamp":"2016-05-23T08:05:34.853Z",
    "beat":{
        "hostname":"beathost",
        "name":"beathost"
    },
    "metricset":{
        "host":"localhost",
        "module":"http",
        "name":"server",
        "rtt":44269
    },
    "http":{
        "server":{
            "test_metric": 5,
        }
    },
    "type":"metricsets"
}