Surveillance des connexions WebSocket
Mettez en œuvre des solutions de surveillance pour suivre les connexions actives, le débit des messages et l’état du serveur.
Surveillance des connexions WebSocket est une leçon WebSockets & Real-Time Systems with Spring gratuite sur CoddyKit. Ceci est la leçon 2 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage WebSockets & Real-Time Systems with Spring, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours WebSockets & Real-Time Systems with Spring comprend 4 leçons au total.
Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.
Why Monitor WebSockets?
Real-time applications, powered by WebSockets, need constant attention to ensure smooth operation. Unlike traditional HTTP, WebSockets maintain persistent connections, making their health critical.
Monitoring helps us understand performance, identify bottlenecks, and react quickly to issues before users are affected. It's key for reliable real-time experiences.
Essential WebSocket Metrics
When monitoring WebSockets, focus on these key areas:
- Active Connections: How many clients are currently connected?
- Message Rates: How many messages are sent/received per second?
- Error Rates: How often do connections fail or messages encounter errors?
- Latency: How quickly are messages processed and delivered?
Tracking these gives you a clear picture of your application's health.
Basic Monitoring with Actuator
Spring Boot Actuator provides production-ready features to monitor and manage your application. It exposes various endpoints that give insights into your app's health, metrics, and environment.
While not specific to WebSockets, Actuator can show general JVM metrics, HTTP request metrics, and overall application health, which are foundational for any monitoring setup.
Actuator's Metrics Endpoint
To get started, add the Actuator dependency to your pom.xml. Then, you can access endpoints like /actuator/health or /actuator/metrics.
The /actuator/metrics endpoint lists available metrics, including some related to thread pools or network activity that might indirectly reflect WebSocket load.
<!-- pom.xml snippet -->
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-actuator</artifactId>
</dependency>Micrometer for Custom Metrics
For WebSocket-specific metrics, we'll use Micrometer, Spring Boot's metrics facade. It allows you to instrument your code with custom counters, gauges, timers, and more, which can then be exported to various monitoring systems.
Micrometer provides a unified API, letting you choose your monitoring backend (like Prometheus, Grafana, etc.) without changing your code.
Counting Live WebSocket Sessions
To track active WebSocket connections, we can use an AtomicInteger to count sessions. Micrometer's Gauge can then expose this value.
A Gauge is perfect for values that fluctuate, like the number of currently connected clients. In a real app, you'd update this counter on connect/disconnect events.
import io.micrometer.core.instrument.Gauge;
import io.micrometer.core.instrument.MeterRegistry;
import io.micrometer.core.instrument.simple.SimpleMeterRegistry;
import java.util.concurrent.atomic.AtomicInteger;
public class SessionCounterDemo {
private final AtomicInteger activeSessions = new AtomicInteger(0);
private final MeterRegistry meterRegistry;
public SessionCounterDemo(MeterRegistry registry) {
this.meterRegistry = registry;
Gauge.builder("websocket.active.sessions", activeSessions, AtomicInteger::get)
.description("Number of active WebSocket sessions")
.register(meterRegistry);
}
public void connect() {
activeSessions.incrementAndGet();
}
public void disconnect() {
activeSessions.decrementAndGet();
}
public static void main(String[] args) {
MeterRegistry registry = new SimpleMeterRegistry();
SessionCounterDemo demo = new SessionCounterDemo(registry);
System.out.println("Initial sessions: " + demo.activeSessions.get());
demo.connect();
demo.connect();
System.out.println("After 2 connects: " + demo.activeSessions.get());
demo.disconnect();
System.out.println("After 1 disconnect: " + demo.activeSessions.get());
}
}Tracking Message Rates
Besides connections, tracking message rates is crucial. We can use a Micrometer Counter to increment each time a message is sent or received.
A Counter is a single-value metric that only increases. It's perfect for counting events like messages processed, requests handled, or errors occurred.
import io.micrometer.core.instrument.Counter;
import io.micrometer.core.instrument.MeterRegistry;
import io.micrometer.core.instrument.simple.SimpleMeterRegistry;
public class MessageCounterDemo {
private final Counter messagesReceived;
public MessageCounterDemo(MeterRegistry registry) {
this.messagesReceived = Counter.builder("websocket.messages.received")
.description("Number of WebSocket messages received")
.register(registry);
}
public void onMessageReceived(String message) {
messagesReceived.increment();
System.out.println("Received message: " + message);
}
public static void main(String[] args) {
MeterRegistry registry = new SimpleMeterRegistry();
MessageCounterDemo demo = new MessageCounterDemo(registry);
System.out.println("Initial messages: " + demo.messagesReceived.count());
demo.onMessageReceived("Hello");
demo.onMessageReceived("World");
System.out.println("Total messages: " + demo.messagesReceived.count());
}
}Capturing WebSocket Errors
Errors can occur at various stages: connection handshakes, message parsing, or business logic. It's vital to track these to maintain application stability.
You can use a Counter for specific error types, perhaps with tags to differentiate between connection errors, message format errors, or server processing errors.
import io.micrometer.core.instrument.Counter;
import io.micrometer.core.instrument.MeterRegistry;
import io.micrometer.core.instrument.simple.SimpleMeterRegistry;
public class ErrorCounterDemo {
private final Counter connectionErrors;
private final Counter messageProcessingErrors;
public ErrorCounterDemo(MeterRegistry registry) {
this.connectionErrors = Counter.builder("websocket.errors.total")
.tag("type", "connection")
.description("Total connection errors")
.register(registry);
this.messageProcessingErrors = Counter.builder("websocket.errors.total")
.tag("type", "message_processing")
.description("Total message processing errors")
.register(registry);
}
public void simulateConnectionError() {
connectionErrors.increment();
System.out.println("Connection error occurred.");
}
public void simulateMessageProcessingError() {
messageProcessingErrors.increment();
System.out.println("Message processing error occurred.");
}
public static void main(String[] args) {
MeterRegistry registry = new SimpleMeterRegistry();
ErrorCounterDemo demo = new ErrorCounterDemo(registry);
System.out.println("Initial connection errors: " + demo.connectionErrors.count());
demo.simulateConnectionError();
System.out.println("Connection errors after one: " + demo.connectionErrors.count());
demo.simulateMessageProcessingError();
System.out.println("Message processing errors: " + demo.messageProcessingErrors.count());
}
}Exporting Metrics to Dashboards
Once you've instrumented your application with Micrometer, these metrics can be exported to various monitoring systems like Prometheus, Grafana, Datadog, or New Relic.
These systems then allow you to build powerful dashboards to visualize your WebSocket metrics in real-time. This helps you spot trends, set alerts, and troubleshoot issues effectively.
Micrometer Metrics Check
You want to track the number of currently active users in a chat application. Which Micrometer metric type is best suited for this purpose?
Monitoring Recap
Great job! You've learned the importance of monitoring WebSocket applications and how to implement it.
- We explored key WebSocket metrics like active connections and message rates.
- You saw how Spring Boot Actuator offers basic health checks.
- We used Micrometer to create custom
GaugeandCountermetrics for WebSocket sessions and messages.
Next, dive into specific tools like Prometheus and Grafana to visualize these metrics and build robust dashboards!
Questions Fréquemment Posées
La leçon « Surveillance des connexions WebSocket » est-elle gratuite ?
Oui — le texte complet de « Surveillance des connexions WebSocket » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours WebSockets & Real-Time Systems with Spring, passe à CoddyKit PRO. Le cours WebSockets & Real-Time Systems with Spring comprend 4 leçons au total.
Qu'est-ce que j'apprendrai dans « Surveillance des connexions WebSocket » ?
Mettez en œuvre des solutions de surveillance pour suivre les connexions actives, le débit des messages et l’état du serveur. Tu pratiques WebSockets & Real-Time Systems with Spring avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.
Dois-je avoir de l'expérience pour commencer WebSockets & Real-Time Systems with Spring ?
Aucune expérience préalable n'est requise. WebSockets & Real-Time Systems with Spring sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 2 sur 4.
Combien de temps prend la leçon « Surveillance des connexions WebSocket » ?
La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.
Peux-tu écrire et exécuter du code dans cette leçon WebSockets & Real-Time Systems with Spring ?
Oui. Chaque leçon WebSockets & Real-Time Systems with Spring inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.
Toutes les leçons de ce cours
- Évaluation des performances de WebSocket
- Surveillance des connexions WebSocket
- Optimisation des paramètres Spring WebSocket
- Réduire la bande passante grâce à la compression des messages