The following shows a Dashboard with replication successfully running between theRnDtoDatacenter 2and that replication has failed between the two JPDs in India.
Viewing JPD Health and Services
The Dashboard Topology page displays your registered JPDs across geographical areas in a map view with a set of indicators that provide insight into the health of your services running on each JPD.By default, the Topology page displays information about theHome JPDthat was configured during the installation process.When youinstall Mission Controland connect it to JFrog Artifactory, the JPD that Mission Control is part of is automatically declared theHome JPDand is displayed in the Topology view as the default location.
The Topology page is divided into two main panels:
- Map View: Youcantoggle between the再保险plication and Access Federationviews or focus on specific JPDsby entering tags that were predefined during theJFrogPlatform Deployment Registration Process.Tags arelabels that help you to organize your JPDs according to logical categories. For example: you can group JPDs by location or by data centers including Development, Testing, and Production.
- Information Panel: You can view basic status information and a list of services configured for the selected JPD.
To access the Topology page, from theApplicationmodule, clickDashboardand selectTopology.
The Topology page displays the JPDs on a map with one of the following health indicators next to each JPD, allowing you to quickly assess the state of your services running in the JPD.
|
|
Indicates that one or more JPDs are running in the same location. |
|
|
Indicates that the services are offline. |
|
|
Indicates that only certain services are offline. Proceed to view the detailed service information. |
|
|
Indicates that all the services are online and functioning in the JPD. |
|
|
Indicates that Access Federation information could not be retrieved. |
|
|
Indicates that the JPD is offline. View the topology metrics to find the problem. |
Click the dropdown arrow in the bottom panel and scroll to view the service details.
A list of services installed on the JPD opens.
The following metrics are displayed in the bottom panel of the Dashboard providing information on the health of the selected JPD and its services.
- Service Status:Displays thehealthof the selected JPD.
- Storage:Displays storage utilisation for repositories and packages.
- 再保险plication:Displays the Replication status -Succeeded, Failed, Not Configured, or Not Run.
- Licenses:Displays the JFrog license activated on the JPD.
- Service Breakdown Per JPD:Displays a list of services installed.
Checking Data Replication Status
再保险plication ensures developers all work with the same version of remote artifacts and that build artifacts are shared efficiently between the different development teams.
The再保险plicationview tracks and displays information on all replications in which the selected JPD is involved. If multiple replications are configured for theJPD, you can filter the list by source or destination repository.再保险plication is used in a variety of use cases to synchronise repositories between remote JPDs. Depending on repository size this may require the transportation of huge quantities of data. Since speed of transportation is limited by bandwidth and network latency, this is a process that may take hours and even days to complete.For more information, see再保险pository Replication.
To access Replication view, from theApplicationmodule, clickTopologyand select再保险plicationfrom theShowlist.
You can quickly check the Replication status for the selected JPD In the bottom panel.
The arrows between the source and target JPDs indicate the direction of the replication data flow from the Target JPD to the Source JPD and colour indicates the replication status:
- Green: Replication was completed successfully.
- Blue: Replication is in progress.
- 再保险d: Replication has failures.
TheDashboard Topology view is displayed with replication between five JPDs with a main RnD Center in Europe, an additional RnD Center in India and three data centers. Replication between RnD to the Datacenter 2 in in progress, whereas replication between Datacenter 3 and Datacenter 2 are still in progress and replication between RnD and DataCenter 1 has failed.
Viewing Access Federation Status
Access Federation gives you control over access to all, or any subset of your services from one location by synchronising all security entities (users, groups, permissions and access tokens) between the federated services. For more information, seeAccess Federation.
You can view the status and health of Access Federation with arrows indicating direction and the status of the synchronisation process according to your Access Federation topology set up in the system.
From theApplicationmodule, clickTopologyand selectAccess Federationfrom theShowlist.
In the following example, Access Federation is configured in a star topology, with grey arrows indicating that Datacenter3 is the sourcefederatingDataCenter1 and Datacenter2.
Viewing Trends in the Dashboard
TheTrendsview displays metrics and a set of graphs related to Distribution, Replication, Security and Storage based on historical data collected and stored.
To view a trend, from theApplication|DashboardclickTrendsand select a trend from theTypedropdown list.
Global Trend Filters
You can apply these global filters to gain different perspectives regarding the health of your JPD:
- Platform Deployments:Allows you to select a JPD from a list of registered JPDs.
- Type:You can view graphs for the following metrics: Distribution, Replication, Security and Storage.
- Time Range:To set the time period, clickFilter. You can select a predefinedperiod:Last 24 hours, Last week, Last month, Last quarter, and Last year. You can also set a custom time range and select any period of time during which data was collected.
In addition to the global filters,each trendsupports a set of dedicated filters. For example, you can filter the Storage Trend by Repositories and Package Types. To view the filters for each trend type, see the specific Trend section.
Storage Trends
Temporary Slow-Running Queries
When running queries including all the repositories in the Storage Trends page, you may experience slow-running queries if you have more than 300 repositories in the JPD.
The StorageTrendtracks the physical storage for each of your registered JPDs. To gain deeper insight, you can filter the data by repositories or by supported package types. Tracking your storage allows you to manage, control, and plan your storage based on the actual storage usage against the maximum allocated space for each of the repositories.
选择图上的一个点displays the total usedspace,the max space allocated, andthe size and number of artifacts in Maven repositories at that point intime. In addition to the graph,you can drill down anddialog view that opens to the left of the graph.
Cloud Deployments
The "Max allocated" and "Allocation by %"过滤器不是艾娃ilable for JPDs that are backed by Cloud providers.
再保险plication Trends
The Replication Trend tracks full or incremental replication从选中的詹妮弗詹妮弗的任何目标according to status type - Failed, Finished, Running or Stopped.Tracking the Replication trends provides you with insight on the quality of the replication based on rate and errors.
In the example above, the graph shows the incremental replicationfromDatacenter 1to any repository inJPD-2.选择图上的一个点showsthat the replication wascompleted successfully with anaveragereplication rate of 1 KB/S and an Upper Deviation of 90 KB/S.
Security Trends
The Security Trend tracks all the vulnerabilities found on your scanned repositories and builds. Tracking the security vulnerabilities allows you to detect problematic builds orrepositoriesand analyze vulnerability trends over a period of time.
In the example above, you can view the number of security vulnerabilities for builds and repositories. Selecting a point on the graph indicates the vulnerabilities by severity level - High, Medium or Low, with a percentage breakdown by repositories and builds.
Distribution Trends
The Distribution Trend tracks the Release Bundle distribution to the Edge nodes. Tracking the Release Bundle distribution process allows you to evaluate the quality of your distribution process from the selected JPD to any Edge nodes.
In the example above, you can view the number of successful and failed distributed Release Bundles. Selecting a point on the graph indicates the number of successful and failed distributed Release Bundles with a breakdown by Edge nodes.
