HelidonHelidon4.5.6

Eureka Registration

Eureka Server Service Instance Registration

Overview

Helidon’s Eureka Server Service Instance Registration Integration provides a ServerFeature that offers support for automatically and unobtrusively attempting to register a running Helidon microservice with an available Netflix Eureka Server of at least version 2.0.5 in the microservice’s runtime environment.

Usage

Installation

Maven Coordinates

To enable Eureka Server Service Instance Registration Integration, add the following dependency to your project’s pom.xml (see Managing Dependencies).

pom.xml
<dependency>
    <groupId>io.helidon.integrations.eureka</groupId>
    <artifactId>helidon-integrations-eureka</artifactId>
    <scope>runtime</scope>1
</dependency>
  1. Most users do not need to interact programmatically with this feature; the scope is therefore usually runtime, indicating that the feature will be available on the runtime classpath.

This feature is fundamentally a ServerFeature, and is automatically installed by its associated ServerFeatureProvider when the provider is found in configuration (see below).

Configuration

You need to specify at an absolute minimum the URI to the available Netflix Eureka Server of at least version 2.0.5 in the microservice’s runtime environment:

application.yaml
server:
  features:
    eureka:1
      client:2
        base-uri: "http://localhost:8761/eureka"34
  1. The feature’s configuration is a child of the server.features.eureka node, which lists available ServerFeature implementations. This feature is one such implementation.
  2. Information about the HTTP client the feature uses to communicate with Eureka is a child of this node.
  3. The base-uri needs to identify an available Netflix Eureka Server of at least version 2.0.5. Netflix Eureka Server is commonly made available on port 8761.
  4. Configuration under the client node is wholly defined by the HttpClientConfig interface.

All other configuration values can be (and ordinarily are) defaulted, but some are best set explicitly:

application.yaml
server:
  features:
    eureka:
      instance:1
        name: "My Application"2
        hostName: example.com <3>
  1. The feature’s configuration pertaining to the registration itself is a child of the server.features.eureka.instance node. Configuration is designed to be familiar to current users of other Netflix Eureka libraries. See the Helidon Config Reference for a full description of what configuration is allowed.
  2. The name describes the microservice application, not any given instance of it. Its default value is unknown, following Netflix Eureka client convention, so it is best to set it explicitly here instead.
  3. The hostName node identifies the host. It defaults to the current host, which may or may not be suitable in your environment. Most of the time you can simply omit this node and use the defaulted value.

Please consult the Helidon Config Reference for a full description of the permitted configuration.

Logging

This feature attempts initial registration when the WebServer starts, before starting lease renewal. If the Eureka Server refuses the connection, the feature logs a warning and the WebServer starts; the renewal loop can attempt registration later. An unsuccessful HTTP response also allows startup to continue when the feature can process its body. Other exceptions during initial registration, such as an unsupported response media type, can propagate from WebServer.start(). The server listener has already started when this happens. Check the feature's logs when registration does not succeed.

Like all other Helidon components, this feature uses Java logging. Its loggers begin with the io.helidon.integrations.eureka prefix, and log debug, warning and error-level information.

Information about how this feature is communicating with the Eureka Server is logged by loggers under the io.helidon.webclient prefix.

Related Documentation

Users of this feature may also be interested in the (related) Discovery feature, particularly its Eureka provider.

Overview

Helidon SE Integrations

HashiCorp Vault

Helidon HashiCorp Vault Integration

Copyright © 2018, 2026 Oracle and/or its affiliates.