Prerequisites

Before diving into the installation, ensure that the following prerequisites are met:

1. Sudo Privileges: Administrative privileges are required to perform installation and configuration tasks.
2. Internet Access: The server must have internet access to download Prometheus binaries.
3. Firewall Configuration: Ensure that port 9090 is open to access Prometheus’s web interface.

Step 1: Installing Prometheus Binary Files

Update Package Repositories

Before downloading Prometheus, update the package repositories to ensure all packages are up to date:

sudo yum update -y

Download Prometheus Binary

Use the following command to download the latest Prometheus binary:

curl -LO https://github.com/prometheus/prometheus/releases/download/v2.22.0/prometheus-2.22.0.linux-amd64.tar.gz

Extract and Rename Files

Extract the downloaded archive and rename the folder for convenience:

tar -xvf prometheus-2.22.0.linux-amd64.tar.gz
mv prometheus-2.22.0.linux-amd64 prometheus-files

Step 2: Setting Up Prometheus User and Directories

Create Prometheus User

Create a dedicated system user for running Prometheus:

sudo useradd --no-create-home --shell /bin/false prometheus

Create Necessary Directories

Set up the required directories for Prometheus configuration and data storage:

sudo mkdir /etc/prometheus
sudo mkdir /var/lib/prometheus

Set the appropriate ownership for these directories:

sudo chown prometheus:prometheus /etc/prometheus
sudo chown prometheus:prometheus /var/lib/prometheus

Step 3: Moving Prometheus Binary Files

Move Prometheus Binaries

Move the prometheus and promtool binaries to a system-wide location:

sudo cp prometheus-files/prometheus /usr/local/bin/
sudo cp prometheus-files/promtool /usr/local/bin/
sudo chown prometheus:prometheus /usr/local/bin/prometheus
sudo chown prometheus:prometheus /usr/local/bin/promtool

Move Console Files

Copy Prometheus console files to the appropriate directories:

sudo cp -r prometheus-files/consoles /etc/prometheus
sudo cp -r prometheus-files/console_libraries /etc/prometheus
sudo chown -R prometheus:prometheus /etc/prometheus/consoles
sudo chown -R prometheus:prometheus /etc/prometheus/console_libraries

Step 4: Configuring Prometheus

The Prometheus configuration file defines how the application behaves, which metrics to scrape, and how often.

Create prometheus.yml

Create the main configuration file at /etc/prometheus/prometheus.yml:

sudo vi /etc/prometheus/prometheus.yml

Add the following content:

global:
  scrape_interval: 10s

scrape_configs:
  - job_name: 'prometheus'
    scrape_interval: 5s
    static_configs:
      - targets: ['localhost:9090']

Set ownership of the configuration file:

sudo chown prometheus:prometheus /etc/prometheus/prometheus.yml

Step 5: Creating a Systemd Service for Prometheus

To ensure Prometheus runs as a service, create a systemd unit file.

Create the Service File

Open a new service file for Prometheus:

sudo vi /etc/systemd/system/prometheus.service

Add the following content:

[Unit]
Description=Prometheus
Wants=network-online.target
After=network-online.target

[Service]
User=prometheus
Group=prometheus
Type=simple
ExecStart=/usr/local/bin/prometheus \
    --config.file /etc/prometheus/prometheus.yml \
    --storage.tsdb.path /var/lib/prometheus/ \
    --web.console.templates=/etc/prometheus/consoles \
    --web.console.libraries=/etc/prometheus/console_libraries

[Install]
WantedBy=multi-user.target

Reload Systemd and Start Prometheus

Reload the systemd manager configuration and start Prometheus:

sudo systemctl daemon-reload
sudo systemctl start prometheus

Verify that the service is running:

sudo systemctl status prometheus

Enable the service to start on boot:

sudo systemctl enable prometheus

Step 6: Accessing the Prometheus Web Interface

Prometheus’s web interface can be accessed via port 9090. Open a web browser and navigate to:

http://<your-server-ip>:9090/graph

Here, you can query existing metrics and visualize data. The default configuration scrapes Prometheus’s own metrics.

Step 7: Adding Additional Monitoring Targets

Prometheus can monitor multiple targets. To add more targets, edit the prometheus.yml file:

scrape_configs:
  - job_name: 'my-app'
    static_configs:
      - targets: ['my-app-server:8080']

Restart Prometheus to apply changes:

sudo systemctl restart prometheus

Conclusion

In this guide, we have covered the complete process of installing and configuring Prometheus on a Linux server. Prometheus is a powerful tool for monitoring system health, gathering metrics, and triggering alerts. Its flexibility allows you to monitor various services and applications by simply adjusting the configuration file.

By following these steps, you’ve set up a robust monitoring solution for your systems. Remember to keep Prometheus updated and secure access to its web interface for optimal performance and security.

Key Features of Snipe-IT:

• Asset Management: Easily track hardware, software, and other assets.
• User Management: Create user profiles to assign assets.
• Advanced Reporting: Generate detailed reports about your asset inventory.
• API Support: Provides a RESTful API for integration with other applications.
• Customizable Fields: Add custom fields based on your needs.
• Movement History: Track the history of assets and their movements.

Snipe-IT Installation

Below are the steps to install Snipe-IT:

Required System Requirements

• Web server (Apache or Nginx)
• PHP 7.3 or higher
• MySQL or MariaDB
• Composer

Installation Steps

1. Prepare the Server: First, ensure that Apache or Nginx, PHP, and MySQL/MariaDB are installed on your server. You can install the necessary components with the following commands:

sudo apt update
sudo apt install apache2 php php-mysql php-xml php-mbstring php-curl php-zip php-json mysql-server

2. Download Snipe-IT: Clone the latest version of Snipe-IT from GitHub.

git clone https://github.com/snipe/snipe-it.git
cd snipe-it

3. Install Dependencies with Composer: Use Composer to install the required dependencies.

composer install --no-dev

4. Create the .env File: Copy the example .env file and edit it.

cp .env.example .env
nano .env

Don’t forget to configure the database settings in the .env file:

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=snipeit
DB_USERNAME=your_username
DB_PASSWORD=your_password

5. Set Up the Database: Create the Snipe-IT database and generate the necessary tables.

php artisan key:generate
php artisan migrate

6. Set File Permissions: Set the required permissions for the directories.

sudo chown -R www-data:www-data /path/to/snipe-it
sudo chmod -R 755 /path/to/snipe-it/storage
sudo chmod -R 755 /path/to/snipe-it/public

7. Configure the Web Server: Configure Apache or Nginx to allow access to Snipe-IT’s web interface.For Apache:

ServerName cpynet.com
DocumentRoot /path/to/snipe-it/public

<Directory /path/to/snipe-it/public>
    AllowOverride All
</Directory>

ErrorLog ${APACHE_LOG_DIR}/snipe-it-error.log
CustomLog ${APACHE_LOG_DIR}/snipe-it-access.log combined

For Nginx:

server {
    listen 80;
    server_name cpynet.com;
    root /path/to/snipe-it/public;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location ~ .php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/var/run/php/php7.3-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }
}

8. Restart the Web Server: Restart the web server to apply the changes.For Apache:

sudo systemctl restart apache2

Or for Nginx:

sudo systemctl restart nginx

9. Launch Snipe-IT: Open your browser and go to http://cpynet.com to access Snipe-IT’s web interface. Follow the setup wizard to complete the initial configuration.

Conclusion

Snipe-IT is a powerful tool that simplifies IT asset management. By following the steps above, you can quickly set up your own Snipe-IT server and start managing your assets.