Page tree
Skip to end of metadata
Go to start of metadata

Overview

In version 1.6, JFrog Mission Control introduced Graphs that display historical data regarding how Artifactory instances and repositories use storage. The data used to produce these graphs is stored in an InfluxDB database. This document describes how the InfluxDB component is integrated into JFrog Mission Control, provides a usage guide and offers some troubleshooting and analysis details.

Version

JFrog Mission Control currently uses InfluxDB version 1.0.2

Page Contents


Official InfluxDB Resources

You may find the following links from the InfluxDB website useful


How InfluxDB is Packaged with Mission Control

InfluxDB is packaged as an integral part of the JFrog Mission Control installation file with minor variations to accommodate each particular distribution.

DistributionPackaging
Standalone LinuxThe InfluxDB for Linux ZIP file is included in the Mission Control ZIP installation. Linux service files are added.

Standalone Windows

The InfluxDB for Windows ZIP file is included in the Mission Control ZIP installation.
Standalone MacThe InfluxDB for Mac ZIP file is included in the Mission Control ZIP installation.
RPM

The InfluxDB for Linux ZIP file is included in the Mission Control RPM project. Linux service files are added.

DebianThe InfluxDB for Linux ZIP file is included in the Mission Control Debian project. Linux service files are added.
DockerInfluxDB for Docker is added as a docker container to the Mission Control docker-compose project.

Installation Structure

Once JFrog Mission Control is fully installed, the InfluxDB binary and data files can be found in the following locations:

Binaries

<JMFC_HOME>/influxdb/

Data files

Linux: /var/lib/influxdb/meta

Mac: /Users/<username>/.influxdb/meta

Windows: %USERPROFILE%\.influxdb\meta

Docker: $HOME/.jfrog/jfmc/influxdb/


Ports

InfluxDB uses the following communication ports:

ServicePort
HTTP API8086

Admin interface (for Web UI)

8083
Standalone MacUDP
Graphite2003
Collectd25826
OpenTSDB4242

 


Monitoring and Controlling the InfluxDB Process

The InfluxDB process is called influxd.

The following table shows how to monitor and control the process on Linux, Windows and Mac platforms.

Linux

Action

Command/Location
Process statusps -ef | grep influxdb
Start process$MC_HOME/bin/influxdb.sh start
Stop process$MC_HOME/bin/influxdb.sh stop
Restart$MC_HOME/bin/influxdb.sh restart
Logs$MC_HOME/logs

Windows

ActionCommand/Location
Process statusView status in the Windows Task Manager
Start process%MC_HOME%\bin\mission-control.bat
Stop processKill the process in the Windows Task Manager
Restart

Kill the process in the Windows Task Manager, and then restart the process using:

%MC_HOME%\bin\mission-control.bat

Logs%MC_HOME%\logs

Mac

ActionCommand/Location
Process statusps -ef | grep influxdb
Start process$MC_HOME/bin/influxdb.sh start
Stop process$MC_HOME/bin/influxdb.sh stop
Restart$MC_HOME/bin/influxdb.sh restart
Logs$MC_HOME/logs

 


InfluxDB Log Rotation

To prevent InfluxDB log files from becoming inflated, Mission Control manages them using log rotation which is currently supported for RPM and Debian installations. The parameters for log rotation are specified in /etc/logrotate.d/influxdb

Permissions

On RPM, the SELinux policy must either be permissive or disabled.

 

 

  • No labels