DIMENSION_TOO_LONG refers to character length limits for dimensions and values in ITRS Analytics data views. Dimensions can have up to 64 characters, values up to 128 characters, with a maximum of 32 dimensions per instance.
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. The FAQ advises disabling such tools before installation and contacting technical support if issues persist.
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.
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.
Failed to verify certificate errors occur due to a missing or improperly installed cert-manager in the ITRS Analytics Obcerv operator environment. The solution is to ensure cert-manager is installed before other operator services by following the prerequisite installation steps.
Gateway cannot connect to ITRS Analytics (Obcerv) due to the error "Cannot check peer: missing selected ALPN property." The issue is resolved by configuring the load balancer with the correct ALPN setting instead of NONE.
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.
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 replicated-app-info-stdout.txt file.
DPD pods restarting frequently can be caused by incorrect deployment size or configuration issues. Adjust the deployment size and update Config Map entries, then scale the DPD statefulset down and back up to apply changes.
Importing SSL certificates from Windows Active Directory as LDAP Provider resolves SSL handshake errors in Keycloak. The process involves creating a ConfigMap with PEM files and updating Keycloak deployment settings to trust the certificates.
Java buffer memory allocation errors on specific pods can cause OutOfMemoryError related to MaxDirectMemorySize and direct buffer memory limits. This FAQ provides possible root causes and corresponding solutions to increase Java buffer memory allocation on affected pods.
Purging old unused ITRS Analytics images helps free disk space and address security scanner vulnerabilities. The FAQ guides verifying image usage, pruning old images, and confirming removal through command checks.
ITRS Analytics services may need to be shut down for scheduled hardware or server maintenance. Procedures vary by deployment type, with Kubernetes clusters requiring coordination with support teams and embedded clusters managed via systemctl or support guidance.
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.
Connectivity issues between Geneos gateway and ITRS Analytics data access user can cause failed token retrieval and accessTokenAvailable to be false. This FAQ provides troubleshooting steps including checking gateway plugin status, verifying user credentials, network connectivity, and Keycloak client settings.
ITRS Analytics license entitlements and related errors occur due to expired, unrenewed, or exceeded licenses, or issues with the licenced process. The FAQ explains how to verify license status via the web console and troubleshoot licenced pod errors.
P99 write latency for disk speed in ITRS Analytics must be less than 10ms to meet pre-flight install requirements. The FAQ explains how to identify disk latency issues and emphasizes using SSD disks to meet performance prerequisites.
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.
Connecting Obcerv/Keycloak to Active Directory requires configuring LDAP settings in the Keycloak User Federation menu and synchronizing users. The FAQ provides step-by-step instructions for setup, attribute mapping, testing connections, and troubleshooting certificate errors.
Multiple pods fail to start or enter CrashLoopBackOff due to DNS errors in ITRS Analytics. Check CoreDNS pod status, node security settings, SELinux mode, and kernel parameters to resolve the issue.
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.
Replicate 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.
Replicate install can fail with a timeout waiting for openebs-localpv-provisioner to deploy due to network issues. The FAQ advises generating a support bundle, checking k0controller logs, and adjusting firewall settings to allow Kubernetes communication.
Support bundle generation in ITRS Analytics may get stuck at a certain progress percentage and not complete. The FAQ advises refreshing the browser page and using command line methods to check or generate the support bundle.
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 Replicate Web Page Advanced Settings can resolve this error.
Setting up Grafana for ITRS Analytics requires configuring the grafana.ini file and Keycloak settings correctly. Following the steps for hostname, redirect URLs, roles, and user creation enables successful login and data querying in Grafana.
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.
Individual app versions included in an ITRS Analytics installation package can be identified by reviewing the package contents. Users can find detailed version information by consulting the ITRS Analytics Release Notes and expanding the Bill-of-materials or Docker images sections.
Pods in ITRS Analytics can become Evicted due to node resource pressure such as memory, disk space, or inode shortages. The FAQ guides users to review eviction thresholds and node resources using kubectl commands and Kubernetes documentation.
The Capacity App may not show on the Web Front End if its pod is restarting frequently. Adjusting the livenessProbe delay or checking for OOM errors can resolve the issue.
No FAQs match your search.