Changing the TLS certificate for ITRS Analytics through the KOTS Admin Console can cause an upgrade failure error. To resolve this, apply a permanent ITRS Analytics license by contacting ITRS Support and following the license upload guide.
Liveness probe failures occur when a pod's startup time exceeds the default probe window, causing Kubernetes to restart the container prematurely. Extending the liveness probe initialDelaySeconds to 300 seconds allows the service to initialize fully and stabilize the pod.
The back-off error in the kotsadm pod occurs when the kotsadm console fails to start and errors indicate disk capacity issues during rqlite writes. The resolution involves checking disk usage and resizing the affected Persistent Volume Claim (PVC).
Compatibility with antivirus and security tools can cause warnings or installation issues with ITRS Analytics due to detected security packages or threat management modules. It is recommended to disable such tools before installation and contact technical support if issues persist.
Gateway cannot connect to ITRS Analytics due to the error "Cannot check peer: missing selected ALPN property." The issue is resolved by enabling ALPN in the load balancer.
Install failure with connection refused error occurs due to server configuration issues. Ensure SE Linux is disabled or permissive, home directory permissions are 755, umask is 077, and rp_filter kernel parameter is set to 2.
Installation can fail with a timeout waiting for openebs-localpv-provisioner to deploy due to network issues. Generate a support bundle, check k0controller logs, and adjust firewall settings to allow Kubernetes communication.
P99 write latency for disk speed in ITRS Analytics must be less than 10ms to meet preflight install requirements. Ensure to use SSD disks to meet performance prerequisites.
ITRS Analytics may need to be shut down for scheduled hardware or server maintenance. Procedures vary by deployment type: coordinate with your Kubernetes team for bring-your-own clusters, or follow Embedded Cluster guidance for single-node and multi-node setups.
ITRS Analytics version information can be found through the Web Console, Admin Console, config map, or support bundle. The version is displayed in the About section, Dashboard tab, or in the support bundle.
Geneos Gateway connectivity to an ITRS Analytics data access user may fail when token retrieval fails and accessTokenAvailable is false. Check the ITRS Analytics Connection plugin, gateway logs, curl token requests, and common HTTP error responses.
ITRS Analytics license entitlements and related errors occur due to expired, unrenewed, or exceeded licenses, or issues with the licensing process. Verify license status via the Web Console and troubleshoot license pod errors.
Verifying alerts received from Geneos in ITRS Analytics involves checking connection status, message statistics, and data trends. Use the ITRS Analytics Connection plugin, gateway logs, and the Ingestion and Alerting Apps to monitor and troubleshoot alert integration.
Old unused ITRS Analytics images can consume disk space and trigger security scanner findings. Verify images are not in use, prune them with k0s, and confirm removal with follow-up checks.
Grafana integration with ITRS Analytics requires correct grafana.ini hostname and OAuth settings, Keycloak redirect URLs, realm role mappers, and a user with admin rights.
Updating custom TLS certificates in ITRS Analytics Embedded Cluster installations involves using the Admin Console and specific kubectl commands. The process requires temporarily enabling anonymous uploads to upload new certificates, then quickly disabling this to minimize security risks.
Find individual app versions bundled in an ITRS Analytics installation package in the Release Notes. Use the packaging summary table or expand the Bill-of-materials or Docker images sections for a specific version.
ITRS Analytics pods may show as Evicted when Kubernetes nodes run low on memory, disk space, or inodes. Check kubelet eviction thresholds with kubectl and verify your nodes meet ITRS Analytics resource and hardware requirements.
Query Service performance errors in ITRS Analytics occur due to issues with WAL streaming and removed WAL segments. These errors are often caused by using unsupported local disk drives instead of required fast SSD volumes for local storage.
The Entity Viewer error "The dataview returned too many cells to render" occurs when a dataview contains excessive data. To resolve this, users should reduce the selected time period to limit the amount of data returned.
ITRS Analytics compatibility, documentation, demo requests, installation requirements, download process, and licensing are covered in this FAQ. It provides guidance on where to find resources, how to obtain licenses, and installation considerations.
Failing to verify certificate errors occur due to a missing or improperly installed cert-manager in the ITRS Analytics operator environment. The solution is to ensure cert-manager is installed before other operator services.
Pipeline task provisioning services in ITRS Analytics may enter an error state due to memory resource allocation problems during installation. Increasing the memory parameter threshold by modifying the yaml configuration file resolves this issue.
Timescale services in ITRS Analytics may enter an error state due to memory-related issues during installation. Increasing the memory threshold via the Helm Chart Values Override in the Admin Console Advanced Settings can resolve this error.
Multiple pods fail to start or enter CrashLoopBackOff when DNS resolution fails in ITRS Analytics. Check CoreDNS pod status, node security software, SELinux mode, and kernel parameters to resolve the issue.
Support bundle generation in ITRS Analytics may get stuck at a certain progress percentage and not complete. Refresh the browser page and use command line methods to check or generate the support bundle.
No FAQs match your search.