Getting started with Monitoring

This guide helps you set up and configure your Monitoring server on ServerPrism. It covers ordering, initial setup, and basic configuration for various monitoring tools like Grafana, Loki, Prometheus, and Uptime Kuma.

Before you start

Ensure you have a clear idea of which monitoring tool you want to use (Grafana, Loki, Prometheus, or Uptime Kuma) and what data sources or agents you plan to connect.

Ordering on ServerPrism

1. Select a plan: Monitoring servers generally require at least 2 GB RAM. For extensive logging or metrics collection, consider plans up to 12 GB RAM.
2. Choose a region: Select the data center geographically closest to your data sources or users for optimal performance.
3. Deploy: During the order process, select your desired monitoring runtime (Grafana, Loki, Prometheus, or Uptime Kuma) from the available options. Your server will deploy automatically.

First boot

After ordering, your server will start provisioning. This process typically takes a few minutes. You can monitor the progress in the ServerPrism panel at https://serverprism.com/dashboard. Once the server status shows as Running and the console output indicates the application has started successfully, your monitoring instance is ready.

Connecting / inviting players

Monitoring servers are typically accessed via a web browser. The default port for each application is usually:

• Grafana: 3000
• Loki: 3100
• Prometheus: 9090
• Uptime Kuma: 3001

You can find your server's IP address and port in the ServerPrism panel on the Console or Network tab. Access your instance by navigating to http://YOUR_SERVER_IP:PORT in your web browser. For a more user-friendly URL, you can attach a free subdomain to your server from your ServerPrism customer dashboard.

Configuration basics

Initial configuration often involves setting up administrator credentials and connecting data sources.

Grafana

Upon first access, Grafana typically prompts you to create an admin user. After logging in, you can add data sources (e.g., Prometheus, Loki) and create dashboards. Key configuration files are often managed through the web UI or environment variables set in the Startup tab of your ServerPrism panel.

Loki

Loki's primary configuration is in config/loki-config.yaml. You can edit this file using the File Manager in your ServerPrism panel. This file defines storage, ingester, and querier settings. You will typically configure agents like Promtail to push logs to your Loki instance.

Prometheus

Prometheus configuration is handled in config/prometheus.yml. Use the File Manager in your ServerPrism panel to edit this file. Here, you define scrape targets (what Prometheus monitors), rules, and alerts. Restart your server after making changes to apply them.

Uptime Kuma

Uptime Kuma is largely configured through its intuitive web interface. Upon first launch, you will set up your admin account. From there, you can add new monitors, notification services, and status pages directly within the application.

For all runtimes, check the Startup tab in your ServerPrism panel for available environment variables that allow you to customize settings without editing files directly.

Common issues

• Cannot access the web interface: Ensure your server is running and you are using the correct IP address and port. Check the Console tab for any startup errors. Firewall issues are rare on ServerPrism, but confirm the port is open if you have custom network settings.
• Application not starting: Review the Console logs in your ServerPrism panel. Look for error messages related to configuration files, missing dependencies, or port conflicts.
• Data not appearing: For Prometheus or Loki, verify your scraping agents (e.g., Node Exporter, Promtail) are correctly configured to send data to your server's IP and port. Check the agent's logs for connection errors.
• Incorrect admin credentials: If you forget your admin password, consult the specific application's documentation for recovery steps. Often, this involves resetting via environment variables or a console command, which you can execute via the Web Console in your ServerPrism panel.

If you encounter persistent issues, open a support ticket at https://serverprism.com/tickets, providing your server ID and relevant console logs.

Next steps

• Connect data sources: Integrate your monitoring server with various data sources (e.g., Prometheus with Node Exporters, Loki with Promtail, Grafana with multiple backends).
• Create dashboards and alerts: Utilize the features of your chosen monitoring tool to visualize your data and set up notifications for critical events.
• Runtime switching: If you decide a different monitoring tool better suits your needs, you can switch runtimes (e.g., from Grafana to Uptime Kuma) directly from the Startup tab in your ServerPrism panel without needing to reorder your server.
• Explore plugins/integrations: Most monitoring platforms offer extensive plugin ecosystems to extend functionality.