Have a question? Want to report an issue? Contact JFrog support

Skip to end of metadata
Go to start of metadata


Mission Control stores historical data about Artifactory services and their repositories, and displays a variety of graphs showing different parameters related to storage and usage of Artifacts in Artifactory services that are managed by Mission Control.

Migrating Data from JFMC 1.x to 2.x

From version 2.0, Mission Control data is stored in Elasticsearch. If you still want your historical data to be accessible, you need to migrate your data from the previously used InfluxDB as described on this page. However, if you are not interested in your historical data, there is no need to migrate your data. Mission Control will continue to collect data from the installation of version 2.0.

Storing Graph Data

Data for the Graphs module is stored using an Elasticsearch database. Mission control runs a service, which collects, stores and manages the historical data in Elasticsearch, and is fully controlled by Mission Control. You should be aware Elasticsearch service is running in the background, however, there should be no need to interact with it directly since it is fully managed by Mission Control.

For full details on using the ElasticSearch database with JFrog Mission Control, please refer to the Elasticsearch Usage Guide.

Page contents

Usage Graphs

The following graphs are currently available:

You can view these graphs in the Graphs module by selecting the corresponding tab.

Storage / Artifact Usage

This graph displays the amount of storage used, and the number of artifacts, in the services and repositories selected in the corresponding lists. There are three available filters: servicesrepositories, and time period.

Data and services list

After a service is configured in Mission Control, data is captured every 15 minutes of the hour. The graphs will show "No data available yet". The services list will also be empty and will be populated when the first 15 minute interval of data collection window occurs.

Use the navigation bar to zoom in and navigate within the timeline. The blank spaces in the graph demonstrate no data collected, where the Artifactory services were unavailable.

Focusing on Artifactory Services and Repositories

By default, this graph displays readings that are accumulated for all Artifactory services managed by Mission Control, and all their respective repositories. You can, however, focus on any specific service or repository by making the appropriate selection in the corresponding lists, and filter it by the time period as needed.

Re-adding services with same name

If a service is deleted, the historical data for the deleted service is not deleted. If a service with the same name is added, the deleted service will be renamed as <service_name>_old_1 for the first time and <service_name>_old_2 the second time and so on. The services drop down will show the deleted ones to help with historical debugging.

Top 5 Repositories (Max. per Week)

This graph displays the 5 repositories (in all managed Artifactory services) whose maximal storage used over the selected week is greatest. If any repository appears in more than one time period, it is displayed using the same color which makes it convenient to compare that repository's maximal storage used week over week. Selecting any bar or hovering over it displays additional details, including the Artifactory service and repository name.

By default, this graph displays readings that are accumulated for all services managed by Mission Control, for the current week. You can, however, focus on any specific service by making the appropriate selection in the drop-list provided, and slide the navigation bar to focus on the needed time period.

Top 5 Services (Max. per Week)

This graph shows the five Artifactory services whose artifacts storage size over the selected week is greatest. Slide the navigation bar to the time period and hover over the bars to view details.