Skip to main content
Version: 3.1.0 (Preview)

Quick Links

Quick Links are service-owned navigation entries that Ambari exposes for web consoles, status pages, and other supported endpoints. They are declared in a service's quicklinks/quicklinks.json and loaded and inherited with the Stack service definition. A Quick Link only describes how to derive an entry from the current topology; it does not start a component, grant authorization, or prove that the target service is healthy.

Definition And Resolution​

Each entry identifies a display label, target component, and URL template or port-backed endpoint rule. The service definition can associate protocol, port, path, and high-availability information with configuration properties so Ambari derives the final URL from the installed cluster's effective configuration. A link must not assume a fixed host name, a fixed active role, or an unconfigured port, and it must never append credentials to the URL.

Ambari evaluates the selected Stack, component assignments, high-availability roles, and effective configuration when rendering links. HTTP or HTTPS policy, configuration-group overrides, host changes, and active-component failover can therefore change the final URL. A link should be hidden or unavailable when the target component is absent, no instance is usable, or required configuration is missing, rather than presenting a plausible but invalid address.

Operational Use​

  1. Install the service and components required by the link.
  2. Set the service configuration that determines its endpoint and security policy.
  3. Open the service page and inspect the resolved Quick Links menu.
  4. If a link is unavailable, check component state, effective configuration, host resolution, and the service's quicklinks.json definition.

Quick Links are navigation metadata, not a monitoring scrape contract or the sole evidence of service health. The pinned BIGTOP quick-link definitions show the current service-owned entries. After adding or changing a link, verify normal deployment, high-availability failover, HTTPS, configuration overrides, and missing-component behavior separately.