Skip to main content

.NET Diagnostic Metrics with Helm

This section contains some guidelines for troubleshooting and handling errors that you may encounter when trying to collect .NET diagnostic metrics.

Problem: No metrics received​

No metrics are observed in your Logz.io account.

Possible cause - Incorrect token and/or listener URL​

Your Logz.io token and/or listener URL may be incorrect.

Suggested remedy​

  1. Navigate to Manage tokens > Data shipping tokens - Metrics and verify your account's metrics token and listener URL.

  2. Check in the integration code whether the token and listener URL are specified correctly.

Possible cause - Shipper connectivity failure​

Your host/server may not be connected to your Logz.io listener.

Suggested remedy​

Verify connectivity of your Logz.io listener as follows.

  • For Linux and Mac servers, use telnet:

    telnet listener.logz.io <<PORT>>

  • For Windows servers running Windows 8/Server 2012 and later, use the following command in PowerShell:

    Test-NetConnection listener.logz.io -Port <<PORT>>

    Replace <<PORT>> with the appropriate port nummber. For HTTPS communication use port 8053. For HTTP communication use port 8052.

Possible cause - Incorrect listener endpoint​

Your Logz.io listener may not be using the correct endpoint.

Suggested remedy​

Change the endpoint of your listener from https://<<LISTENER-HOST>>:<<PORT>> to http://<<LISTENER-HOST>>:<<PORT>> or from http://<<LISTENER-HOST>>:<<PORT>> to https://<<LISTENER-HOST>>:<<PORT>>

include file not found: ../log-shipping/listener-var.html --> /opt/build/repo/docs/user-guide/Infrastructure-monitoring/log-shipping/listener-var.html

Possible cause - Pod is not running​

One of your Kubernetes pods may not be running.

Suggested remedy​

Check if a required pod is runing by using the following command:

kubectl -n <<NAMESPACE>> get pods

Replace <<NAMESPACE>> with the name of the namespace for the required pod.

Possible cause - Pod is not running​

The dotnet monitorpod may not be running.

Suggested remedy​

Check the logs of the pod that was created for dotnet monitor.

If the logs do not appear, check the pod's configuration by running:

dotnet monitor config show

If the configuration is correct, contact the Support team.