Understanding Eureka Console Parameters and the Self‑Preservation Mechanism

This article walks through the Eureka dashboard’s System Status section, explains the meaning of each displayed metric, describes how the self‑preservation mode works and how to enable or disable it, and reviews cluster and instance information shown in a local Eureka cluster.

Wukong Talks Architecture
Wukong Talks Architecture
Wukong Talks Architecture
Understanding Eureka Console Parameters and the Self‑Preservation Mechanism

The article begins by showing how to open the Eureka console at http://localhost:8762/ and points out the top‑most System Status panel.

It then explains each field in the panel:

Environment : defaults to test.

Data center : defaults to default.

Current time : the server’s current time.

Uptime : how long the server has been running.

Lease expiration enabled : indicates whether lease expiration is active; it is true when self‑preservation is off and false when it is on.

Renews threshold : the minimum number of renewals expected per minute.

Renews (last min) : the actual number of renewals received in the last minute.

The next section covers the Self‑Preservation Mechanism . It explains three situations that trigger red warnings in the UI:

The self‑preservation setting is turned off.

The setting is on, but the renewal rate falls below the threshold, causing the server to keep instances marked as UP.

The setting is off and the renewal rate is below 85% for a minute, indicating a possible network partition.

To disable self‑preservation, add the following line to the configuration: eureka.server.enable-self-preservation = false The article then describes Cluster Information . When multiple Eureka servers form a cluster, the DS Replicas field lists the other nodes; in a single‑node setup it shows only the current instance.

It proceeds to the Registered Instances List , which displays all services currently registered with Eureka. An example entry shows a service named SERVICEA with status UP at localhost:ServiceA:8006.

The General Information section lists various metrics such as total available memory, environment name, CPU count, current memory usage, server uptime, and replica registration details.

Further details are provided for Service Instance Information , showing the IP address and status of each Eureka server instance.

Finally, the article covers the Last 1000 Cancelled Leases and Last 1000 Newly Registered Leases tables, which list recent lease cancellations and new registrations respectively.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

backendmicroservicesservice discoveryEurekaSpring CloudSelf-Preservation
Wukong Talks Architecture
Written by

Wukong Talks Architecture

Explaining distributed systems and architecture through stories. Author of the "JVM Performance Tuning in Practice" column, open-source author of "Spring Cloud in Practice PassJava", and independently developed a PMP practice quiz mini-program.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.