v0.2.5

ServerPulse v0.2.5 Update Overview

🌟 Major New Features

Velocity Support

The most significant addition in this version is support for Velocity proxy servers. This allows you to monitor your entire Minecraft network infrastructure, including both backend servers (Bukkit/Paper) and the proxy layer.

Enhanced Dashboard Collection

Additional pre-configured dashboards have been added specifically for Velocity metrics, focusing on:

• Player count tracking
• Player ping statistics (min/max/average)
• Memory and system resource usage

🔄 Upgrading from v0.2.2

1. Plugin Update:

   • Simply replace your existing ServerPulse JAR in the plugins folder with the new version (Bukkit/Paper)
   • If you want to also use Velocity, drop the JAR in its plugins folder and follow the setup process in the Wiki (identical to Bukkit)

2. Dashboard Updates:

   • To get the new Velocity dashboards, you'll need to update your Grafana configuration:
   • Remove the old dashboard files from your Grafana provisioning directory
   • Add the new dashboard files from the infra/grafana/dashboards/ directory
   • Bukkit/Paper dashboards also have been improved, so remove all the files and put the new ones

If you're using the Docker Compose setup for Grafana and InfluxDB, make sure to restart the containers after updating your dashboard files to see the new Velocity dashboards.

🧰 Commands

New Velocity Commands

The addition of Velocity support introduces a new command structure for proxy servers:

• Base Command: /serverpulsevelocity (with alias /spv)
• Status Check: /serverpulsevelocity status - Shows the current connection status to InfluxDB
• Configuration Reload: /serverpulsevelocity reload - Reloads the plugin configuration

These commands follow the same permission structure as the Bukkit version, but are specifically implemented for the Velocity command system.

📚 Documentation

For comprehensive documentation on all commands, configuration, setup instructions, and developer API information, please visit the Wiki

v0.2.2

🔧 Technical Fixes

• Fixed Kotlin dependency problerm

🔄 Upgrading from v0.2.1

• Just put the new JAR in the plugins folder

v0.2.1

🔧 Technical Fixes

• Added InfluxDB volume to ensure persistent data

🔄 Upgrading from v0.2.0

• Update your docker-compose.yml with the updated one

No changes done inside the plugin

v0.2.0

🔧 Technical Improvements

• Universal Platform Support: Added compatibility for all Bukkit-based servers
• Automatic Platform Detection: Intelligently chooses between native Paper TPS API and custom Bukkit implementation
• TPS Monitoring for Vanilla Bukkit: Implemented custom TPS monitoring for standard Bukkit/CraftBukkit servers
• Reduced Dependencies: Removed explicit dependency on Paper API

🔄 Upgrading from v0.1.7

• Just put the new JAR in the plugins folder

v0.1.7

🔧 Technical Improvements

• Add API integration module for developers
• Use API internally in the project for future different implementations
• To understand how to use it: Developer API

🔄 Upgrading from v0.1.6

• Just put the new JAR in the plugins folder

v0.1.6

🎯 New Features

• Add telegram alerting integration
• Add fully documented-wiki

🔧 Technical Improvements

• Added provisioning files for telegram

🔄 Upgrading from v0.1.5

• Put the new file telegram_contact.yml into infra/grafana/provisioning/alerting
• Re-run docker_compose and follow instructions on Alert Wiki

v0.1.5

🔧 Technical Fixes

• Fixed Kotlin conflict with other plugins (specifically with EcoEnchants)
• Added Grafana volume to ensure persistent data

🔄 Upgrading from v0.1.4

• Deploy the docker-compose.yml to ensure Docker creates the Grafana volume
• Just put the new JAR in the plugins folder

v0.1.4

🎯 New Features

• Add new players' ping metrics (min, max, avg)
• Implement new dashboard displaying these new metrics

🔧 Technical Improvements

• Added provisioning files for ping's dashboard

🔄 Upgrading from v0.1.3

• Put the new plugin in your plugins folder
• Go to Grafana UI -> Dashboards -> New -> Import -> Import via dashboard JSON model
• The JSON can be found inside infra/grafana/dashboards/default_ping.json
• Dashboard ready :)

v0.1.3

🎯 New Features

• Add alert system for server metrics monitoring (TPS...)
• Implement threshold-based alerting with configurable values
• Add support for different comparison operators based on metric type
• Configure alert messages in configuration file

🔧 Technical Improvements

• Added provisioning files for alerting system
• Change your Discord webhook URL in discord_contact.yml

🔄 Upgrading from v0.1.2

• Just upload the new folder alerting in your provisioning folder
• Change Discord webhook URL as mentioned above
• Run docker compose

To create new metrics alert just follow the TPS example :)

v0.1.2

🎯 New Features

In-Game Commands

• Added /serverpulse command with the following subcommands:
  • /serverpulse status - Check the connection status with InfluxDB
  • /serverpulse reload - Reload the plugin configuration

Permission System

• Introduced granular permissions:
  • serverpulse.status - Permission to check InfluxDB connection status
  • serverpulse.reload - Permission to reload plugin configuration

Configuration Updates

• Added new message customization options in config.yml:
• All messages support color codes using '&' symbol

🔧 Technical Improvements

• Implemented command framework for easier future command additions
• Added proper command error handling and user feedback
• Enhanced configuration reload mechanism with error handling

🔄 Upgrading from v0.1.1

Important: Configuration Update Required

After upgrading, you must update your configuration:

1. Delete your existing plugins/ServerPulse/config.yml
2. Restart your server to generate the new config file
3. Copy your existing InfluxDB settings (URL, token, org, bucket) and custom tags to the new config
4. The new config includes additional message customization options - configure these as desired

There are no database schema changes or other breaking changes. The upgrade process is:

1. Replace the old JAR with the new one
2. Follow the configuration update steps above
3. Restart your server