Releases: renvins/serverpulse
Releases · renvins/serverpulse
v0.2.2
v0.2.1
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
pluginsfolder
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
pluginsfolder
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.ymlintoinfra/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
pluginsfolder
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
pluginsfolder - 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
alertingin yourprovisioningfolder - 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
/serverpulsecommand 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 statusserverpulse.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:
- Delete your existing
plugins/ServerPulse/config.yml - Restart your server to generate the new config file
- Copy your existing InfluxDB settings (URL, token, org, bucket) and custom tags to the new config
- 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:
- Replace the old JAR with the new one
- Follow the configuration update steps above
- Restart your server
v0.1.1
Improvements:
- Enhanced database connection reliability
- Added automatic reconnection when connection is lost
- Better handling of connection failures in MetricsService
Fixes:
- Fixed issue where metrics collection would continue during connection loss
- Fixed database retry mechanism not triggering on ping failures
Note: no configuration changes are required.