You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After successfully installing Grafana Alloy via the "Connections" -> "Add new connection" -> "Linux Server" method within the Grafana UI, a systemd service file for grafana-alloy is not created. This results in Alloy not starting automatically after a system reboot. Consequently, users have to manually start Alloy after each restart.
Steps to reproduce
Navigate to "Connections" in the Grafana UI.
Click on "Add new connection".
Select "Linux Server".
Follow the prompts to install Grafana Alloy on a Fedora 41 or Fedora 42 system.
Once the installation is reported as successful in the UI, reboot the Linux server.
After the reboot, check for the existence of a grafana-alloy.service file (e.g., in /etc/systemd/system/).
Observe that the service file is missing.
Attempt to check the status of the grafana-alloy service (e.g., using systemctl status grafana-alloy). Observe that the service cannot be found.
System information
Linux PTX-PC-178 6.14.2-300.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 10 21:50:55 UTC 2025 x86_64 GNU/Linux
Software version
alloy, version v1.8.1 (branch: HEAD, revision: dc3b14b)
What's wrong?
After successfully installing Grafana Alloy via the "Connections" -> "Add new connection" -> "Linux Server" method within the Grafana UI, a systemd service file for
grafana-alloy
is not created. This results in Alloy not starting automatically after a system reboot. Consequently, users have to manually start Alloy after each restart.Steps to reproduce
grafana-alloy.service
file (e.g., in/etc/systemd/system/
).grafana-alloy
service (e.g., usingsystemctl status grafana-alloy
). Observe that the service cannot be found.System information
Linux PTX-PC-178 6.14.2-300.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 10 21:50:55 UTC 2025 x86_64 GNU/Linux
Software version
alloy, version v1.8.1 (branch: HEAD, revision: dc3b14b)
Configuration
Logs
The text was updated successfully, but these errors were encountered: