Type to search.

Registered Domain

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.

The registered_domain processor reads a field containing a hostname and then writes the "registered domain" contained in the hostname to the target field. For example, given www.google.co.uk the processor would output google.co.uk. In other words the "registered domain" is the effective top-level domain (co.uk) plus one level (google). Optionally, it can store the rest of the domain, the subdomain into another target field.

This processor uses the Mozilla Public Suffix list to determine the value.

YAML 
processors:
  - registered_domain:
      field: dns.question.name
      target_field: dns.question.registered_domain
      target_etld_field: dns.question.top_level_domain
      target_subdomain_field: dns.question.sudomain
      ignore_missing: true
      ignore_failure: true

The registered_domain processor has the following configuration settings:

Name Required Default Description
field yes Source field containing a fully qualified domain name (FQDN).
target_field yes Target field for the registered domain value.
target_etld_field no Target field for the effective top-level domain value.
target_subdomain_field no Target subdomain field for the subdomain value.
ignore_missing no false Ignore errors when the source field is missing.
ignore_failure no false Ignore all errors produced by the processor.
id no An identifier for this processor instance. Useful for debugging.