package envoy.config.bootstrap.v3

Get desktop application:
View/edit binary Protocol Buffers messages

Administration interface :ref:`operations documentation <operations_admin_interface>`. [#next-free-field: 7]

Used in: Bootstrap

• repeated accesslog.v3.AccessLog access_log = 5

  Configuration for :ref:`access logs <arch_overview_access_logs>` emitted by the administration server.

• string access_log_path = 1

  The path to write the access log for the administration server. If no access log is desired specify ‘/dev/null’. This is only required if :ref:`address <envoy_v3_api_field_config.bootstrap.v3.Admin.address>` is set. Deprecated in favor of ``access_log`` which offers more options.

• string profile_path = 2

  The cpu profiler output path for the administration server. If no profile path is specified, the default is ‘/var/log/envoy/envoy.prof’.

• optional core.v3.Address address = 3

  The TCP address that the administration server will listen on. If not specified, Envoy will not start an administration server.

• repeated core.v3.SocketOption socket_options = 4

  Additional socket options that may not be present in Envoy source code or precompiled binaries.

• bool ignore_global_conn_limit = 6

  Indicates whether :ref:`global_downstream_max_connections <config_overload_manager_limiting_connections>` should apply to the admin interface or not.

Bootstrap :ref:`configuration overview <config_overview_bootstrap>`. [#next-free-field: 42]

Used in: admin.v3.BootstrapConfigDump

• optional core.v3.Node node = 1

  Node identity to present to the management server and for instance identification purposes (e.g. in generated headers).

• repeated string node_context_params = 26

  A list of :ref:`Node <envoy_v3_api_msg_config.core.v3.Node>` field names that will be included in the context parameters of the effective xdstp:// URL that is sent in a discovery request when resource locators are used for LDS/CDS. Any non-string field will have its JSON encoding set as the context parameter value, with the exception of metadata, which will be flattened (see example below). The supported field names are: - "cluster" - "id" - "locality.region" - "locality.sub_zone" - "locality.zone" - "metadata" - "user_agent_build_version.metadata" - "user_agent_build_version.version" - "user_agent_name" - "user_agent_version" The node context parameters act as a base layer dictionary for the context parameters (i.e. more specific resource specific context parameters will override). Field names will be prefixed with “udpa.node.” when included in context parameters. For example, if node_context_params is ``["user_agent_name", "metadata"]``, the implied context parameters might be:: node.user_agent_name: "envoy" node.metadata.foo: "{\"bar\": \"baz\"}" node.metadata.some: "42" node.metadata.thing: "\"thing\"" [#not-implemented-hide:]

• optional Bootstrap.StaticResources static_resources = 2

  Statically specified resources.

• optional Bootstrap.DynamicResources dynamic_resources = 3

  xDS configuration sources.

• optional ClusterManager cluster_manager = 4

  Configuration for the cluster manager which owns all upstream clusters within the server.

• optional core.v3.ApiConfigSource hds_config = 14

  Health discovery service config option. (:ref:`core.ApiConfigSource <envoy_v3_api_msg_config.core.v3.ApiConfigSource>`)

• string flags_path = 5

  Optional file system path to search for startup flag files.

• repeated metrics.v3.StatsSink stats_sinks = 6

  Optional set of stats sinks.

• optional Bootstrap.DeferredStatOptions deferred_stat_options = 39

  Options to control behaviors of deferred creation compatible stats.

• optional metrics.v3.StatsConfig stats_config = 13

  Configuration for internal processing of stats.

• optional google.protobuf.Duration stats_flush_interval = 7

  Optional duration between flushes to configured stats sinks. For performance reasons Envoy latches counters and only flushes counters and gauges at a periodic interval. If not specified the default is 5000ms (5 seconds). Only one of ``stats_flush_interval`` or ``stats_flush_on_admin`` can be set. Duration must be at least 1ms and at most 5 min.

• oneof stats_flush

  • bool stats_flush_on_admin = 29

    Flush stats to sinks only when queried for on the admin interface. If set, a flush timer is not created. Only one of ``stats_flush_on_admin`` or ``stats_flush_interval`` can be set.

• optional Watchdog watchdog = 8

  Optional watchdog configuration. This is for a single watchdog configuration for the entire system. Deprecated in favor of ``watchdogs`` which has finer granularity.

• optional Watchdogs watchdogs = 27

  Optional watchdogs configuration. This is used for specifying different watchdogs for the different subsystems. [#extension-category: envoy.guarddog_actions]

• optional trace.v3.Tracing tracing = 9

  Configuration for an external tracing provider. .. attention:: This field has been deprecated in favor of :ref:`HttpConnectionManager.Tracing.provider <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing.provider>`.

• optional LayeredRuntime layered_runtime = 17

  Configuration for the runtime configuration provider. If not specified, a “null” provider will be used which will result in all defaults being used.

• optional Admin admin = 12

  Configuration for the local administration HTTP server.

• optional overload.v3.OverloadManager overload_manager = 15

  Optional overload manager configuration.

• bool enable_dispatcher_stats = 16

  Enable :ref:`stats for event dispatcher <operations_performance>`, defaults to false. Note that this records a value for each iteration of the event loop on every thread. This should normally be minimal overhead, but when using :ref:`statsd <envoy_v3_api_msg_config.metrics.v3.StatsdSink>`, it will send each observed value over the wire individually because the statsd protocol doesn't have any way to represent a histogram summary. Be aware that this can be a very large volume of data.

• string header_prefix = 18

  Optional string which will be used in lieu of x-envoy in prefixing headers. For example, if this string is present and set to X-Foo, then x-envoy-retry-on will be transformed into x-foo-retry-on etc. Note this applies to the headers Envoy will generate, the headers Envoy will sanitize, and the headers Envoy will trust for core code and core extensions only. Be VERY careful making changes to this string, especially in multi-layer Envoy deployments or deployments using extensions which are not upstream.

• optional google.protobuf.UInt64Value stats_server_version_override = 19

  Optional proxy version which will be used to set the value of :ref:`server.version statistic <server_statistics>` if specified. Envoy will not process this value, it will be sent as is to :ref:`stats sinks <envoy_v3_api_msg_config.metrics.v3.StatsSink>`.

• bool use_tcp_for_dns_lookups = 20

  Always use TCP queries instead of UDP queries for DNS lookups. This may be overridden on a per-cluster basis in cds_config, when :ref:`dns_resolvers <envoy_v3_api_field_config.cluster.v3.Cluster.dns_resolvers>` and :ref:`use_tcp_for_dns_lookups <envoy_v3_api_field_config.cluster.v3.Cluster.use_tcp_for_dns_lookups>` are specified. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.

• optional core.v3.DnsResolutionConfig dns_resolution_config = 30

  DNS resolution configuration which includes the underlying dns resolver addresses and options. This may be overridden on a per-cluster basis in cds_config, when :ref:`dns_resolution_config <envoy_v3_api_field_config.cluster.v3.Cluster.dns_resolution_config>` is specified. This field is deprecated in favor of :ref:`typed_dns_resolver_config <envoy_v3_api_field_config.bootstrap.v3.Bootstrap.typed_dns_resolver_config>`.

• optional core.v3.TypedExtensionConfig typed_dns_resolver_config = 31

  DNS resolver type configuration extension. This extension can be used to configure c-ares, apple, or any other DNS resolver types and the related parameters. For example, an object of :ref:`CaresDnsResolverConfig <envoy_v3_api_msg_extensions.network.dns_resolver.cares.v3.CaresDnsResolverConfig>` can be packed into this ``typed_dns_resolver_config``. This configuration replaces the :ref:`dns_resolution_config <envoy_v3_api_field_config.bootstrap.v3.Bootstrap.dns_resolution_config>` configuration. During the transition period when both ``dns_resolution_config`` and ``typed_dns_resolver_config`` exists, when ``typed_dns_resolver_config`` is in place, Envoy will use it and ignore ``dns_resolution_config``. When ``typed_dns_resolver_config`` is missing, the default behavior is in place. [#extension-category: envoy.network.dns_resolver]

• repeated core.v3.TypedExtensionConfig bootstrap_extensions = 21

  Specifies optional bootstrap extensions to be instantiated at startup time. Each item contains extension specific configuration. [#extension-category: envoy.bootstrap]

• repeated FatalAction fatal_actions = 28

  Specifies optional extensions instantiated at startup time and invoked during crash time on the request that caused the crash.

• repeated core.v3.ConfigSource config_sources = 22

  Configuration sources that will participate in xdstp:// URL authority resolution. The algorithm is as follows: 1. The authority field is taken from the xdstp:// URL, call this ``resource_authority``. 2. ``resource_authority`` is compared against the authorities in any peer ``ConfigSource``. The peer ``ConfigSource`` is the configuration source message which would have been used unconditionally for resolution with opaque resource names. If there is a match with an authority, the peer ``ConfigSource`` message is used. 3. ``resource_authority`` is compared sequentially with the authorities in each configuration source in ``config_sources``. The first ``ConfigSource`` to match wins. 4. As a fallback, if no configuration source matches, then ``default_config_source`` is used. 5. If ``default_config_source`` is not specified, resolution fails. [#not-implemented-hide:]

• optional core.v3.ConfigSource default_config_source = 23

  Default configuration source for xdstp:// URLs if all other resolution fails. [#not-implemented-hide:]

• string default_socket_interface = 24

  Optional overriding of default socket interface. The value must be the name of one of the socket interface factories initialized through a bootstrap extension

• map<string, core.v3.TypedExtensionConfig> certificate_provider_instances = 25

  Global map of CertificateProvider instances. These instances are referred to by name in the :ref:`CommonTlsContext.CertificateProviderInstance.instance_name <envoy_v3_api_field_extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProviderInstance.instance_name>` field. [#not-implemented-hide:]

• repeated CustomInlineHeader inline_headers = 32

  Specifies a set of headers that need to be registered as inline header. This configuration allows users to customize the inline headers on-demand at Envoy startup without modifying Envoy's source code. Note that the 'set-cookie' header cannot be registered as inline header.

• string perf_tracing_file_path = 33

  Optional path to a file with performance tracing data created by "Perfetto" SDK in binary ProtoBuf format. The default value is "envoy.pftrace".

• optional core.v3.TypedExtensionConfig default_regex_engine = 34

  Optional overriding of default regex engine. If the value is not specified, Google RE2 will be used by default. [#extension-category: envoy.regex_engines]

• optional core.v3.TypedExtensionConfig xds_delegate_extension = 35

  Optional XdsResourcesDelegate configuration, which allows plugging custom logic into both fetch and load events during xDS processing. If a value is not specified, no XdsResourcesDelegate will be used. TODO(abeyad): Add public-facing documentation. [#not-implemented-hide:]

• optional core.v3.TypedExtensionConfig xds_config_tracker_extension = 36

  Optional XdsConfigTracker configuration, which allows tracking xDS responses in external components, e.g., external tracer or monitor. It provides the process point when receive, ingest, or fail to process xDS resources and messages. If a value is not specified, no XdsConfigTracker will be used. .. note:: There are no in-repo extensions currently, and the :repo:`XdsConfigTracker <envoy/config/xds_config_tracker.h>` interface should be implemented before using. See :repo:`xds_config_tracker_integration_test <test/integration/xds_config_tracker_integration_test.cc>` for an example usage of the interface.

• optional core.v3.TypedExtensionConfig listener_manager = 37

  [#not-implemented-hide:] This controls the type of listener manager configured for Envoy. Currently Envoy only supports ListenerManager for this field and Envoy Mobile supports ApiListenerManager.

• optional Bootstrap.ApplicationLogConfig application_log_config = 38

  Optional application log configuration.

• optional Bootstrap.GrpcAsyncClientManagerConfig grpc_async_client_manager_config = 40

  Optional gRPC async manager config.

• optional MemoryAllocatorManager memory_allocator_manager = 41

  Optional configuration for memory allocation manager. Memory releasing is only supported for `tcmalloc allocator <https://github.com/google/tcmalloc>`_.

Used in: Bootstrap

• optional ApplicationLogConfig.LogFormat log_format = 1

  Optional field to set the application logs format. If this field is set, it will override the default log format. Setting both this field and :option:`--log-format` command line option is not allowed, and will cause a bootstrap error.

Used in: ApplicationLogConfig

• oneof log_format

  • google.protobuf.Struct json_format = 1

    Flush application logs in JSON format. The configured JSON struct can support all the format flags specified in the :option:`--log-format` command line options section, except for the ``%v`` and ``%_`` flags.

  • string text_format = 2

    Flush application log in a format defined by a string. The text format can support all the format flags specified in the :option:`--log-format` command line option section.

Used in: Bootstrap

• bool enable_deferred_creation_stats = 1

  When the flag is enabled, Envoy will lazily initialize a subset of the stats (see below). This will save memory and CPU cycles when creating the objects that own these stats, if those stats are never referenced throughout the lifetime of the process. However, it will incur additional memory overhead for these objects, and a small increase of CPU usage when a at least one of the stats is updated for the first time. Groups of stats that will be lazily initialized: - Cluster traffic stats: a subgroup of the :ref:`cluster statistics <config_cluster_manager_cluster_stats>` that are used when requests are routed to the cluster.

[#next-free-field: 7]

Used in: Bootstrap

• optional core.v3.ConfigSource lds_config = 1

  All :ref:`Listeners <envoy_v3_api_msg_config.listener.v3.Listener>` are provided by a single :ref:`LDS <arch_overview_dynamic_config_lds>` configuration source.

• string lds_resources_locator = 5

  xdstp:// resource locator for listener collection. [#not-implemented-hide:]

• optional core.v3.ConfigSource cds_config = 2

  All post-bootstrap :ref:`Cluster <envoy_v3_api_msg_config.cluster.v3.Cluster>` definitions are provided by a single :ref:`CDS <arch_overview_dynamic_config_cds>` configuration source.

• string cds_resources_locator = 6

  xdstp:// resource locator for cluster collection. [#not-implemented-hide:]

• optional core.v3.ApiConfigSource ads_config = 3

  A single :ref:`ADS <config_overview_ads>` source may be optionally specified. This must have :ref:`api_type <envoy_v3_api_field_config.core.v3.ApiConfigSource.api_type>` :ref:`GRPC <envoy_v3_api_enum_value_config.core.v3.ApiConfigSource.ApiType.GRPC>`. Only :ref:`ConfigSources <envoy_v3_api_msg_config.core.v3.ConfigSource>` that have the :ref:`ads <envoy_v3_api_field_config.core.v3.ConfigSource.ads>` field set will be streamed on the ADS channel.

Used in: Bootstrap

• optional google.protobuf.Duration max_cached_entry_idle_duration = 1

  Optional field to set the expiration time for the cached gRPC client object. The minimal value is 5s and the default is 50s.

Used in: Bootstrap

• repeated listener.v3.Listener listeners = 1

  Static :ref:`Listeners <envoy_v3_api_msg_config.listener.v3.Listener>`. These listeners are available regardless of LDS configuration.

• repeated cluster.v3.Cluster clusters = 2

  If a network based configuration source is specified for :ref:`cds_config <envoy_v3_api_field_config.bootstrap.v3.Bootstrap.DynamicResources.cds_config>`, it's necessary to have some initial cluster definitions available to allow Envoy to know how to speak to the management server. These cluster definitions may not use :ref:`EDS <arch_overview_dynamic_config_eds>` (i.e. they should be static IP or DNS-based).

• repeated extensions.transport_sockets.tls.v3.Secret secrets = 3

  These static secrets can be used by :ref:`SdsSecretConfig <envoy_v3_api_msg_extensions.transport_sockets.tls.v3.SdsSecretConfig>`

Cluster manager :ref:`architecture overview <arch_overview_cluster_manager>`. [#next-free-field: 6]

Used in: Bootstrap

• string local_cluster_name = 1

  Name of the local cluster (i.e., the cluster that owns the Envoy running this configuration). In order to enable :ref:`zone aware routing <arch_overview_load_balancing_zone_aware_routing>` this option must be set. If ``local_cluster_name`` is defined then :ref:`clusters <envoy_v3_api_msg_config.cluster.v3.Cluster>` must be defined in the :ref:`Bootstrap static cluster resources <envoy_v3_api_field_config.bootstrap.v3.Bootstrap.StaticResources.clusters>`. This is unrelated to the :option:`--service-cluster` option which does not `affect zone aware routing <https://github.com/envoyproxy/envoy/issues/774>`_.

• optional ClusterManager.OutlierDetection outlier_detection = 2

  Optional global configuration for outlier detection.

• optional core.v3.BindConfig upstream_bind_config = 3

  Optional configuration used to bind newly established upstream connections. This may be overridden on a per-cluster basis by upstream_bind_config in the cds_config.

• optional core.v3.ApiConfigSource load_stats_config = 4

  A management server endpoint to stream load stats to via ``StreamLoadStats``. This must have :ref:`api_type <envoy_v3_api_field_config.core.v3.ApiConfigSource.api_type>` :ref:`GRPC <envoy_v3_api_enum_value_config.core.v3.ApiConfigSource.ApiType.GRPC>`.

• bool enable_deferred_cluster_creation = 5

  Whether the ClusterManager will create clusters on the worker threads inline during requests. This will save memory and CPU cycles in cases where there are lots of inactive clusters and > 1 worker thread.

Used in: ClusterManager

• string event_log_path = 1

  Specifies the path to the outlier event log.

• optional core.v3.EventServiceConfig event_service = 2

  [#not-implemented-hide:] The gRPC service for the outlier detection event service. If empty, outlier detection events won't be sent to a remote endpoint.

Used to specify the header that needs to be registered as an inline header. If request or response contain multiple headers with the same name and the header name is registered as an inline header. Then multiple headers will be folded into one, and multiple header values will be concatenated by a suitable delimiter. The delimiter is generally a comma. For example, if 'foo' is registered as an inline header, and the headers contains the following two headers: .. code-block:: text foo: bar foo: eep Then they will eventually be folded into: .. code-block:: text foo: bar, eep Inline headers provide O(1) search performance, but each inline header imposes an additional memory overhead on all instances of the corresponding type of HeaderMap or TrailerMap.

Used in: Bootstrap

• string inline_header_name = 1

  The name of the header that is expected to be set as the inline header.

• CustomInlineHeader.InlineHeaderType inline_header_type = 2

  The type of the header that is expected to be set as the inline header.

Used in: CustomInlineHeader

• REQUEST_HEADER = 0

• REQUEST_TRAILER = 1

• RESPONSE_HEADER = 2

• RESPONSE_TRAILER = 3

Fatal actions to run while crashing. Actions can be safe (meaning they are async-signal safe) or unsafe. We run all safe actions before we run unsafe actions. If using an unsafe action that could get stuck or deadlock, it important to have an out of band system to terminate the process. The interface for the extension is ``Envoy::Server::Configuration::FatalAction``. ``FatalAction`` extensions live in the ``envoy.extensions.fatal_actions`` API namespace.

Used in: Bootstrap

• optional core.v3.TypedExtensionConfig config = 1

  Extension specific configuration for the action. It's expected to conform to the ``Envoy::Server::Configuration::FatalAction`` interface.

Runtime :ref:`configuration overview <config_runtime>`.

Used in: Bootstrap

• repeated RuntimeLayer layers = 1

  The :ref:`layers <config_runtime_layering>` of the runtime. This is ordered such that later layers in the list overlay earlier entries.

Used in: Bootstrap

• uint64 bytes_to_release = 1

  Configures tcmalloc to perform background release of free memory in amount of bytes per ``memory_release_interval`` interval. If equals to ``0``, no memory release will occur. Defaults to ``0``.

• optional google.protobuf.Duration memory_release_interval = 2

  Interval in milliseconds for memory releasing. If specified, during every interval Envoy will try to release ``bytes_to_release`` of free memory back to operating system for reuse. Defaults to 1000 milliseconds.

Runtime :ref:`configuration overview <config_runtime>` (deprecated).

• string symlink_root = 1

  The implementation assumes that the file system tree is accessed via a symbolic link. An atomic link swap is used when a new tree should be switched to. This parameter specifies the path to the symbolic link. Envoy will watch the location for changes and reload the file system tree when they happen. If this parameter is not set, there will be no disk based runtime.

• string subdirectory = 2

  Specifies the subdirectory to load within the root directory. This is useful if multiple systems share the same delivery mechanism. Envoy configuration elements can be contained in a dedicated subdirectory.

• string override_subdirectory = 3

  Specifies an optional subdirectory to load within the root directory. If specified and the directory exists, configuration values within this directory will override those found in the primary subdirectory. This is useful when Envoy is deployed across many different types of servers. Sometimes it is useful to have a per service cluster directory for runtime configuration. See below for exactly how the override directory is used.

• optional google.protobuf.Struct base = 4

  Static base runtime. This will be :ref:`overridden <config_runtime_layering>` by other runtime layers, e.g. disk or admin. This follows the :ref:`runtime protobuf JSON representation encoding <config_runtime_proto_json>`.

[#next-free-field: 6]

Used in: LayeredRuntime

• string name = 1

  Descriptive name for the runtime layer. This is only used for the runtime :http:get:`/runtime` output.

• oneof layer_specifier

  • google.protobuf.Struct static_layer = 2

    :ref:`Static runtime <config_runtime_bootstrap>` layer. This follows the :ref:`runtime protobuf JSON representation encoding <config_runtime_proto_json>`. Unlike static xDS resources, this static layer is overridable by later layers in the runtime virtual filesystem.

  • RuntimeLayer.DiskLayer disk_layer = 3

  • RuntimeLayer.AdminLayer admin_layer = 4

  • RuntimeLayer.RtdsLayer rtds_layer = 5

:ref:`Admin console runtime <config_runtime_admin>` layer.

Used in: RuntimeLayer

(message has no fields)

:ref:`Disk runtime <config_runtime_local_disk>` layer.

Used in: RuntimeLayer

• string symlink_root = 1

  The implementation assumes that the file system tree is accessed via a symbolic link. An atomic link swap is used when a new tree should be switched to. This parameter specifies the path to the symbolic link. Envoy will watch the location for changes and reload the file system tree when they happen. See documentation on runtime :ref:`atomicity <config_runtime_atomicity>` for further details on how reloads are treated.

• string subdirectory = 3

  Specifies the subdirectory to load within the root directory. This is useful if multiple systems share the same delivery mechanism. Envoy configuration elements can be contained in a dedicated subdirectory.

• bool append_service_cluster = 2

  :ref:`Append <config_runtime_local_disk_service_cluster_subdirs>` the service cluster to the path under symlink root.

:ref:`Runtime Discovery Service (RTDS) <config_runtime_rtds>` layer.

Used in: RuntimeLayer

• string name = 1

  Resource to subscribe to at ``rtds_config`` for the RTDS layer.

• optional core.v3.ConfigSource rtds_config = 2

  RTDS configuration source.

Envoy process watchdog configuration. When configured, this monitors for nonresponsive threads and kills the process after the configured thresholds. See the :ref:`watchdog documentation <operations_performance_watchdog>` for more information. [#next-free-field: 8]

Used in: Bootstrap, Watchdogs

• repeated Watchdog.WatchdogAction actions = 7

  Register actions that will fire on given WatchDog events. See ``WatchDogAction`` for priority of events.

• optional google.protobuf.Duration miss_timeout = 1

  The duration after which Envoy counts a nonresponsive thread in the ``watchdog_miss`` statistic. If not specified the default is 200ms.

• optional google.protobuf.Duration megamiss_timeout = 2

  The duration after which Envoy counts a nonresponsive thread in the ``watchdog_mega_miss`` statistic. If not specified the default is 1000ms.

• optional google.protobuf.Duration kill_timeout = 3

  If a watched thread has been nonresponsive for this duration, assume a programming error and kill the entire Envoy process. Set to 0 to disable kill behavior. If not specified the default is 0 (disabled).

• optional google.protobuf.Duration max_kill_timeout_jitter = 6

  Defines the maximum jitter used to adjust the ``kill_timeout`` if ``kill_timeout`` is enabled. Enabling this feature would help to reduce risk of synchronized watchdog kill events across proxies due to external triggers. Set to 0 to disable. If not specified the default is 0 (disabled).

• optional google.protobuf.Duration multikill_timeout = 4

  If ``max(2, ceil(registered_threads * Fraction(*multikill_threshold*)))`` threads have been nonresponsive for at least this duration kill the entire Envoy process. Set to 0 to disable this behavior. If not specified the default is 0 (disabled).

• optional type.v3.Percent multikill_threshold = 5

  Sets the threshold for ``multikill_timeout`` in terms of the percentage of nonresponsive threads required for the ``multikill_timeout``. If not specified the default is 0.

Used in: Watchdog

• optional core.v3.TypedExtensionConfig config = 1

  Extension specific configuration for the action.

• WatchdogAction.WatchdogEvent event = 2

The events are fired in this order: KILL, MULTIKILL, MEGAMISS, MISS. Within an event type, actions execute in the order they are configured. For KILL/MULTIKILL there is a default PANIC that will run after the registered actions and kills the process if it wasn't already killed. It might be useful to specify several debug actions, and possibly an alternate FATAL action.

Used in: WatchdogAction

• UNKNOWN = 0

• KILL = 1

• MULTIKILL = 2

• MEGAMISS = 3

• MISS = 4

Allows you to specify different watchdog configs for different subsystems. This allows finer tuned policies for the watchdog. If a subsystem is omitted the default values for that system will be used.

Used in: Bootstrap

• optional Watchdog main_thread_watchdog = 1

  Watchdog for the main thread.

• optional Watchdog worker_watchdog = 2

  Watchdog for the worker threads.