Menu
DocumentationGrafana CloudMonitor infrastructureGrafana integrationsTroubleshoot installationsOn Windows using Alloy
Grafana Cloud

Troubleshoot an Integration installation on Windows using Grafana Alloy

When installing an Integration, you can experience errors when executing Grafana Alloy installation script and errors when configuring Alloy to work with the Integration.

Common errors when executing Alloy installation script

The installation script will return an error message if there is a problem during installation. You can use these messages to identify and correct the errors.

ERROR: The script needs to be run with Administrator privileges

The script provided to install Alloy on Windows creates a Windows Service, which is the recommended way to manage background processes for this OS. This operation requires you to execute the script with Administrator privileges.

ERROR: Failed to install Alloy for Windows

The script could not download and successfully execute Alloy installer. Check the detailed error message for more information. If you need help, contact us using one of the options available on our official Help page.

Any other error

Other errors might occur during installation, like exceptions when creating the Windows Service for Alloy. Check the error message for more details. If you need help, contact us using one of the options available on our official Help page.

Common errors when configuring Alloy for Integrations - Test Data Connection button

You can use the Test Data Connection button on the integration setup page to verify that you configured Alloy correctly and that it is sending the expected data.

A few things can cause a check failure. Before going into detail, make sure you have restarted Alloy service by running the following commands on Powershell with Administrator privileges:

powershell 
Stop-Service "Alloy"
Start-Service "Alloy"

If the test fails, check the error message for more information:

No metrics were found for this integration.

This message indicates that Alloy cannot contact your Grafana Cloud Prometheus endpoint. This can happen for several reasons, not limited to:

  • Alloy is not starting correctly due to problems in your configuration file syntax or indentation
  • Alloy is not able to connect to your Grafana Cloud Prometheus endpoint (networking or configuration issues)

To understand the reasons for this problem, check Alloy events in the Windows Event Visualizer, under Windows Logs > Application.

If there are component configuration error logs, make sure you followed all instructions provided. You can check Alloy components reference documentation for help or contact us using the Feedback form if you think there is a problem with the integration.

If you find errors about connecting to your Grafana Cloud Prometheus endpoint, make sure you didn’t change the URL or authentication details. You can verify your endpoint and create new keys under the Cloud Portal.

Alloy was not able to reach your application Prometheus metrics endpoint.

This message means that Alloy started successfully and was able to connect to your Grafana Cloud Prometheus endpoint but failed to scrape your application Prometheus metrics endpoint. This can happen for several reasons, not limited to:

  • The endpoint address is incorrect
  • The endpoint is protected, and no authentication details were provided
  • The endpoint is not online

To understand the reasons for this error, check Alloy events in the Windows Event Visualizer, under Windows Logs > Application.

If you find that the endpoint is not online or there are authentication errors, make sure you have followed the steps in the first section of the Integration setup page, Check prerequisites specific to....

Alloy was not able to collect your application logs

This message is displayed when Alloy can’t collect logs and send them to your Grafana Cloud Loki endpoint. This can happen for several reasons, not limited to:

  • It is still starting up. Give it a few moments to start sending data
  • There are no logs available
  • The logs path is incorrect
  • Alloy does not have the necessary permissions to access your application logs
  • Alloy is not able to connect to your Grafana Cloud Loki endpoint (networking or configuration issues)

To understand the reasons for this error, check Alloy events in the Windows Event Visualizer, under Windows Logs > Application.

If you find permission errors, make sure you have followed the steps in the first section of the Integration setup page, Check prerequisites specific to....

If you find errors in the logs about connecting to your Grafana Cloud Loki endpoint, make sure you didn’t change the logs URL or authentication details. You can verify your endpoint and create new keys under the Cloud Portal.