Pemeriksaan Kesehatan dan Metrik
Terapkan Spring Boot Actuator untuk menyediakan titik akhir kesehatan dan mengumpulkan metrik aplikasi.
Pemeriksaan Kesehatan dan Metrik adalah pelajaran Spring Boot 4 Microservices & REST APIs gratis di CoddyKit. Ini adalah pelajaran 2 dari 3. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Spring Boot 4 Microservices & REST APIs, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Spring Boot 4 Microservices & REST APIs mencakup 3 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
What is Spring Boot Actuator?
When running microservices, monitoring their health and performance is super important. Spring Boot Actuator provides a set of production-ready features to help you do just that!
It exposes operational information about your running application, making it easier to observe and manage.
Add Actuator Dependency
To start using Actuator, you just need to add its dependency to your Spring Boot project. This is typically done in your pom.xml for Maven or build.gradle for Gradle.
Here's how to add it with Maven:
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-actuator</artifactId>
</dependency>Explore Default Endpoints
Once the Actuator dependency is added, Spring Boot automatically configures several useful endpoints. These endpoints provide valuable insights into your application's state.
/actuator/health: Shows the application's health status./actuator/info: Displays general application information./actuator/metrics: Provides detailed metrics data.
Checking Application Health
The /actuator/health endpoint is a fundamental part of monitoring. It tells you if your application and its integrated components (like databases or disk space) are functioning correctly.
A simple "UP" status means everything is good! Run this basic app and check its health endpoint.
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
@SpringBootApplication
public class ActuatorDemoApplication {
public static void main(String[] args) {
SpringApplication.run(ActuatorDemoApplication.class, args);
}
}Accessing Health Endpoint
After running the previous application, open your browser and navigate to http://localhost:8080/actuator/health.
You should see a JSON response indicating the application's overall status, typically {"status":"UP"}.
This is a quick way to verify if your service is alive!
Create Custom Health Checks
You can extend Actuator's health checks to include your own custom logic. For example, checking the status of an external API, a message queue, or a specific business process.
To do this, you implement the HealthIndicator interface:
import org.springframework.boot.actuate.health.Health;
import org.springframework.boot.actuate.health.HealthIndicator;
import org.springframework.stereotype.Component;
@Component
public class CustomServiceHealthIndicator implements HealthIndicator {
private final String SERVICE_NAME = "MyExternalService";
@Override
public Health health() {
if (isServiceUp()) {
return Health.up().withDetail(SERVICE_NAME, "Available").build();
}
return Health.down().withDetail(SERVICE_NAME, "Not Available").build();
}
private boolean isServiceUp() {
// Simulate checking an external service
return Math.random() > 0.3; // 70% chance of being up
}
}Understanding Application Metrics
Metrics are numerical data points that describe your application's behavior over time. They are crucial for understanding performance, resource usage, and identifying potential bottlenecks.
Spring Boot Actuator, powered by Micrometer, automatically collects various metrics:
- CPU and memory usage
- HTTP request counts and latencies
- Database connection pool statistics
Querying Metrics Data
The /actuator/metrics endpoint provides a list of all available metrics. You can then query specific metrics for detailed information.
- Visit
http://localhost:8080/actuator/metricsto see available metrics. - Then, try
http://localhost:8080/actuator/metrics/jvm.memory.usedto see the specific memory usage metric.
This allows you to gather precise data for monitoring dashboards.
Implement Custom Metrics
Beyond the default metrics, you can track application-specific events using custom metrics. Micrometer provides simple APIs for different metric types like Counters, Gauges, and Timers.
Here's an example of a custom Counter:
import io.micrometer.core.instrument.Counter;
import io.micrometer.core.instrument.MeterRegistry;
import org.springframework.stereotype.Service;
@Service
public class MyService {
private final Counter customCounter;
public MyService(MeterRegistry meterRegistry) {
this.customCounter = Counter.builder("my_app.processed.items")
.description("Number of items processed by MyService")
.register(meterRegistry);
}
public void processItem() {
System.out.println("Processing an item...");
customCounter.increment(); // Increment the counter
}
}Customize Endpoint Exposure
By default, only /health and /info are typically exposed over HTTP. You can configure which other endpoints Actuator makes available using application.properties or application.yml.
To expose more endpoints like metrics, beans, and env, add this line:
management.endpoints.web.exposure.include=health,info,metrics,beans,envActuator Knowledge Check
Let's quickly check your understanding of Spring Boot Actuator's benefits.
Lesson Recap
Great job! In this lesson, you learned about:
- Spring Boot Actuator for monitoring and managing microservices.
- Implementing health checks using the
/actuator/healthendpoint. - Creating custom health indicators for specific services.
- Understanding and collecting application metrics via
/actuator/metrics. - Implementing custom metrics with Micrometer.
- The importance of securing Actuator endpoints in production.
Next, we'll dive into centralized logging and dashboarding!
Belajar Java dengan tutor AI — gratis
Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.
- Kursus
- 24
- Pelajaran
- 93
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Pemeriksaan Kesehatan dan Metrik” gratis?
Ya — teks lengkap “Pemeriksaan Kesehatan dan Metrik” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Spring Boot 4 Microservices & REST APIs, upgrade ke CoddyKit PRO. Kursus Spring Boot 4 Microservices & REST APIs mencakup 3 pelajaran total.
Apa yang akan aku pelajari di “Pemeriksaan Kesehatan dan Metrik”?
Terapkan Spring Boot Actuator untuk menyediakan titik akhir kesehatan dan mengumpulkan metrik aplikasi. Kamu berlatih Spring Boot 4 Microservices & REST APIs dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Spring Boot 4 Microservices & REST APIs?
Tidak diperlukan pengalaman sebelumnya. Spring Boot 4 Microservices & REST APIs di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 3.
Berapa lama pelajaran “Pemeriksaan Kesehatan dan Metrik” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Spring Boot 4 Microservices & REST APIs ini?
Ya. Setiap pelajaran Spring Boot 4 Microservices & REST APIs menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Pencatatan Terpusat dengan ELK Stack
- Pemeriksaan Kesehatan dan Metrik
- Pemberitahuan dan Dasbor