Derived from KTs for all customer solutions
Overview The issue pertains to backlogs being created at CHN collectors due to full utilization on the Pri viewer. This can prevent the normal operation of the system and cause significant operational...
Overview The customer was unable to retrieve records for a specific IP address within a certain date range from the PRI IPLOGGER URL, despite the data being present in the backend. The root cause of t...
Overview The customer was experiencing high CPU utilization on their host server, SURUMACGNAT01. This issue had been previously addressed but reoccurred, leading to an escalation to the Level 2 suppor...
Overview The customer experienced a server reboot due to a power failure and needed assistance to enable all services on the server. The server was an IPDR logging system, which required high priority...
Overview The customer is experiencing an issue with a script that is supposed to move logs from the live partition to the storage partition on a server. The server's IP address is 172.16.87.87 and the...
Overview A user may experience an issue where they are unable to access specific data from a certain date and time through their Graphical User Interface (GUI). This data could be associated with a pa...
Overview The issue at hand involves the SFTPUploader service, where files are getting stuck at the SFTP distribution path on the collection server and are not being pushed towards the Parsing server. ...
Overview The customer is experiencing high memory utilization on their node, specifically on port 8963, which is causing frequent alerts. Despite having a cache memory purging script already scheduled...