What is Master?
Axelix Master (or simply "Master") is the central hub of the Axelix ecosystem, application with enhanced capabilities for managing and monitoring Spring Boot applications across various environments.
Core Purpose
Axelix Master serves as a centralized management console that automatically discovers, registers, and monitors Spring Boot applications, providing real-time insights and control.
Key Capabilities
π Service Discovery
Master learns about Spring Boot applications through two complementary mechanisms:
Self-registration (any environment):
Applications that include the Axelix Spring Boot Starter announce themselves to Master and send periodic heartbeats. This
works anywhere the app can reach Master β Docker Compose, bare-metal, VMs, Kubernetes, etc. It is opt-in per
application: enable it on in your application with axelix.sbs.discovery.self-registration=true (it is off by default). Master
accepts these registrations out of the box (axelix.master.discovery.self-registration.enabled setting in Master on by default).
Automatic discovery (Kubernetes only):
When enabled (controlled by axelix.master.discovery.auto.enabled property), Master actively scans the platform to find qualifying services.
Platform scanning is currently implemented for Kubernetes only. It is off by default in Master's own configuration,
but the official Helm chart turns it on by default.
How discovery works:
- Self-registration: apps with the Axelix Starter register themselves and heartbeat
- Platform scanning (Kubernetes): Master probes the cluster for services exposing Axelix SBS endpoints
- Health monitoring: Master periodically polls registered instances and evicts ones that stop heartbeating
π₯οΈ Unified Web Interface
A single pane of glass for all your Spring Boot applications:
Features include:
- Dashboard with all registered applications
- Embedded MCP server to serve this information to the AI Agents
- Configuration property and Environment inspection
- Detailed analysis Beans
- and so on, see the Features section