Apache Ambari 3.1.0 Overview
| Area | Change in 3.1.0 | Guide |
|---|---|---|
| Monitoring | Replace AMS with Prometheus-compatible collection, VMAGENT, VictoriaMetrics, and native React monitoring | Architecture comparison |
| User interface | Make React the primary experience for the operational and administrative workflows carried forward from Ember | React user interface |
| Java | Consolidate the JDK 17/Maven 3.9 baseline, managed framework dependencies, and separate Ambari/Stack JDK selection | Java dependencies |
| Python | Replace maintained-in-tree third-party forks with locked upstream distributions and standard-library APIs | Python runtime |
| Distribution | Make Python ABI, target architecture, dependency provenance, and RPM contents explicit | RPM packaging |
The new monitoring system is not an AMS configuration toggle. Metrics names, dashboard storage, service descriptors, and the storage deployment change. Plan the transition before replacing an existing installation.
Reading Paths
- Operators deploying monitoring: read deployment, then queries and dashboards.
- Existing 3.0.0 installations: start with the upgrade checklist and monitoring migration.
- Stack maintainers: read the architecture and service telemetry contract.
- Package builders: review the Java, Python, and RPM contracts together.
Illustrated Guides
| Diagram | Guide |
|---|---|
| Overall Ambari architecture | Ambari architecture |
| React request lifecycle | React user interface |
| Repository module map | Ambari code layout |
| Stack and service anatomy | Stacks and services |
| Blueprint provisioning | Blueprints |
| Kerberos enablement | Kerberos |
| Build pipeline | Building from source |
| Installation and Agent enrollment | Installation guide |
| Monitoring architecture | Monitoring architecture |
| VictoriaMetrics topology | Monitoring deployment |
| Service telemetry integration | Service integration |
| AMS migration | Monitoring migration |
| Dashboard query path | Queries and dashboards |
| Alert evaluation and notification | Alerts |
| Configuration resolution | Enhanced configs |
| Request, task, and recovery state | Ambari architecture |
Version Boundaries
These pages describe Ambari 3.1.0, not a new 3.0.x maintenance release. The existing 3.0.0 documentation remains the historical reference for AMS and the older packaging instructions.
Ambari's release number, the BIGTOP Stack version, and the VictoriaMetrics software version are independent. A Stack descriptor located under BIGTOP 3.2.0 may be inherited by another Stack version; its directory name is not an Ambari release requirement. Use the Stack metadata in the package being deployed.
The default website documentation entry remains the released 3.0.0 version while 3.1.0 is in preview. See release notes for the change summary and the source baseline for the reviewed revisions.