Mission Control

Sitting at the core of developer and DevOps environments, Artifactory is a mission-critical resource for an organization that develops software. An Artifactory administrator must make sure that Artifactory is properly configured and running smoothly to serve all developers in the organization. While Artifactory does provide extensive facilities for configuration, both in the UI and through the REST API, as soon as the administrator needs to manage several instances of Artifactory, monitoring them all becomes an issue, and she is faced with scripting requirements to perform configurations automatically, or the need to repeatedly enter configurations in a manual, error-prone process.

JFrog Mission Control is the answer to these issues. Mission Control is a command and control center that gives you full control over all your Artifactory HA instances, and real-time visibility into how your organization develops, distributes and consumes software packages around the world. Letting you configure multiple instances of Artifactory simultaneously, Mission Control prevents configuration issues as you scale up to thousands of engineers in multiple teams around the world.

JFrog Mission Control Diagram


Mission Control shows you general system health of all your Artifactory HA instances in one convenient dashboard. At a glance, you can see which are online and if any are down. With a single click, you drill down into any offline instances and investigate what happened.


View and Monitor

Just select any Artifactory HA instance to view full details about it including general information, a full list of repositories, replication and proxy relationships with other instances of Artifactory, system information, license details, HA configuration and more.


Flexible Management with Roles

Roles represent an action you want to perform on your Artifactory instances, and may be reused as often as needed. They are written in a Groovy-based DSL, so they are easy to use and flexible.Roles can be used to define anything from simple actions like creating a single repository to more complex ones like setting up of multipush replication. To keep things flexible, you can even define roles to ask for user input just before being applied. That way, for example, you could defer specifying a proxy port, an LDAP server URL or pretty much any parameter, to the last minute, just before you apply the role.

Roles are at the heart of Mission Control for three reasons:

Automation: They let you automate configuration tasks preventing the need for repetitive and error-prone manual configuration or complex configuration scripts.

Reliability: They improve the reliability of your configuration tasks since you can reuse roles at any time on multiple Artifactory instances running on any runtime environment.

Standardization: Using roles, you can enforce standards and consistency when configuring things such as repository names, include/exclude patterns caching policies and more.


Repository Relationships

While roles are used to manage your Artifactory instances and their repositories, it’s also important to see the relationships between different repositories to determine how artifacts flow through your organization. For any Artifactory instance you select, Mission Control displays its proxying relationships with other repositories, and both push and pull replication relationships.


With more and more enterprises setting up multiple clusters of Artifactory HA in every corner of the world, there is a critical need for DevOps and developers to have a single integrated view of their core systems. Mission Control fills that need providing the ability to monitor, maintain and configure these systems automatically and safely.