Skip to main content

Troubleshooting - Agent Installation

The list below presents issues you might face when installing the App Insights agent, and how to overcome them.

no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"

If you get a message like this:

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest:
resource mapping not found for name: "insights-opencost" namespace: "" from "":
no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
ensure CRDs are installed first

It means the Prometheus operator is not installed on your cluster. If you want to use the Cost Analysis features of App Insights, please first install the Prometheus operator external link and then try installing the App Insights agent again.

If you don't want to use the Cost Analysis features of App Insights, deselect the "Auto-install OpenCost" option in the UI (see image below), copy the updated commands, and then try the installation again.

Deselect the Auto-install OpenCost option

namespaces "randoli-agents" not found

If you get a message like this:

Error: INSTALLATION FAILED: create: failed to create: namespaces "randoli-agents" not found

It means your cluster is missing the "randoli-agents" namespace. Please follow the installation steps from the App Insights UI and create the "randoli-agents" namespace on your cluster:

Create the randoli-agents namespace

"randoli" already exists with the same configuration, skipping

The "randoli" already exists with the same configuration, skipping message is not an issue. It means you already have added Randoli's helm repo before, so you can safely ignore this message.

Cluster is not connected

Once you complete the installation steps using the helm cli, you will see a message like this:

NAME: insights
LAST DEPLOYED: Fri Mar 1 12:18:20 2024
NAMESPACE: randoli-agents
STATUS: deployed
REVISION: 1
TEST SUITE: None

If the App Insights UI still shows the cluster as PENDING, please wait 2 minutes and refresh the page. If it still shows the cluster as PENDING, please check the troubleshooting cluster connection page

Other issues

If you face any issues not covered here, please reach out to our support team, who is always happy to help!