System for method for monitoring logs for upgradation of a server environment

Abstract

Disclosed is a system (100) and a method (400) for monitoring logs for upgradation of a server environment. The method comprises establishing a communication session between a client 104 and a target server of a plurality of target servers 102 in the server environment. Upon establishment of the communication session, a first log data file including first plurality of logs is fetched from the target server. Using a rule-based model (204-2), a log pattern of the first plurality of logs is identified by analyzing the first log data file. based on a pre-defined criteria, one of a presence or an absence of one or more critical logs from the identified log pattern of the first plurality of logs in the first log data file is determined. Based on the determination, a message indicating one of the presence or the absence of the one or more critical logs is generated.

Description

SYSTEM FOR METHOD FOR MONITORING LOGS FOR UPGRADATION OF A SERVER ENVIRONMENTTECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of communication networks. More particularly, the present disclosure relates to a system and a method for monitoring logs for upgradation of a server environment of communication networks.BACKGROUND OF THE INVENTION

[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely because of its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.

[0003] In a rapidly evolving and expanding field of telecommunications, particularly with advent of 5thGeneration (5G) networks, maintaining and upgrading server environments that support 5G node applications has become increasingly complex and critical. Management of a plurality of servers in the server environment is a crucial aspect of management of the communication network. Management of the server environment includes server configuration management, including the management of changes and upgradations made to applications and software running in the plurality of servers in the server environment. For example, the upgradation may include changes to individual servers or a group of servers in the server environment. The upgradation may include, but not limited to, installation of new applications, configuration changes in software or applications, upgrading to newer versions or downgrading to older versions of applications, removal of existing applications.

[0004] Typically, network operators perform various upgrade procedures, such as installing software updates and configuring system settings on a per-server basis or in small batches, with significant manual oversight to ensure each step is correctly executed and all necessary components are updated. However, this limits the scalability of the communication network.

[0005] As the 5G networks continue to scale and number of servers required to support the 5G networks grows, challenges associated with monitoring of upgradation of the server environment have become more pronounced. The sheer volume of the servers that need to be upgraded has led to an extended maintenance window, increased operational cost, and a risk of non-uniform configuration changes across the communication network.

[0006] Further, with substantial number of servers in the communication network, monitoring server configuration changes manually is a troublesome undertaking with unforeseen and potentially significant consequences. As non-standardized configuration changes may impair essential functionality of the communication network, introduce security vulnerabilities in the communication network, and may result in degraded network performance, business impact of lack of a system for monitoring progress of upgradation is significant.

[0007] Currently existing configuration management tools control configuration and maintenance of groups of servers. However, there are challenges associated with the existing configuration management tools as there is no provision to monitor progress of the upgradation and only an outcome of the upgradation is accessible to the network operators i.e., a successful or a failed upgradation operation. This impacts the efficiency and productivity of the network operators making it a labor- intensive task as they have to perform the upgrade again from scratch in case of the upgradation operation. Further, they are not able to troubleshoot to a point where the upgradation failed, leading to inconsistencies in the server environment, potential downtime, and security vulnerabilities.

[0008] Therefore, there is a need for an improved solution that minimizes manual effort and enhances consistency in performing upgradations of across large-scale server deployments.SUMMARY

[0009] The following embodiments present a simplified summary to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key / critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0010] In an embodiment, disclosed herein is a method for monitoring logs for upgradation of a server environment. The method comprises establishing, by a processing module, a communication session between a client and a target server of a plurality of target servers in the server environment, upon establishment of the communication session, the method comprises fetching, by a log management module, a first log data file comprising a first plurality of logs from the target server. Further, the method comprises identifying, by the log management module, a log pattern of the first plurality of logs by analyzing the first log data file using a rulebased model. Furthermore, the method comprises determining, by the log management module based on a pre-defined criteria, one of a presence or an absence of one or more critical logs from the identified log pattern of the first plurality of logs in the first log data file. Thereafter, based on a result of the determination the method comprises generating, by the processing module, a message indicating one of the presence or the absence of the one or more critical logs.[Oi l] In one aspect, the pre-defined criteria include one or more of a first condition for checking a count of a log or a count of a log sequence in the identified log pattern with respect to a first pre-defined threshold, a second condition for checking the log sequence in the identified log pattern in a pre-defined time-period with respect to a second pre-defined threshold, and a third condition for checking a count of the first plurality of logs in the identified log pattern with respect to a second plurality oflogs included in a second log data file fetched in a preceding communication session. The first log data file and the second log data file are associated with the upgradation of the target server.

[0012] In one aspect, the message includes a recommendation indicating at least one of proceeding with the upgradation, stopping the upgradation, initiating a rollback for the upgradation, or performing an analysis for deciding for proceeding with the upgradation.

[0013] In one aspect, the method comprises displaying, by the processing module, the message on a User Interface (UI) of a user device.

[0014] In one aspect, based on the determination of one of the presence or the absence of the one or more critical logs in the first log data file, the method comprises analyzing, by the log management module, an impact of the presence or absence of the one or more critical logs in the identified log pattern of the first plurality of logs on the upgradation. Further, the method comprises determining, by the log management module based on the impact of the presence or absence of the one or more critical logs, a confidence score indicating a likelihood of a success or failure of the upgradation of the server environment.

[0015] In one aspect, the first plurality of logs includes information associated with the upgradation of the target server.

[0016] In one aspect, the method comprises initiating, by the processing module, an Application Programming Interface (API) call request for establishing the communication session between the client and the target server. The API call request for establishing the communication session is initiated based on one of a reception of a user request at the processing module for monitoring logs corresponding to upgradation of the server environment, or a triggering of a scheduler at a pre-defined time interval.

[0017] According to another aspect of the present disclosure, disclosed is a system for monitoring logs for upgradation of a server environment. The system comprises a processing module and a log management module. The processing module is configured to establish a communication session between a client and a target server of a plurality of target servers in the server environment. The log management module is configured to fetch, upon establishment of the communication session, a first log data file comprising a first plurality of logs from the target server. Further, the log management module is configured to identify a log pattern of the first plurality of logs by analyzing the first log data file using a rule-based model. Furthermore, the log management module is configured to determine, based on a pre-defined criteria, one of a presence or an absence of one or more critical logs from the identified log pattern of the first plurality of logs in the first log data file. Thereafter, processing module is configured to generate, based on a result of the determination, a message indicating one of the presence or the absence of the one or more critical logs.

[0018] In one aspect, the pre-defined criteria include one or more of a first condition for checking a count of a log or a count of a log sequence in the identified log pattern with respect to a first pre-defined threshold, a second condition for checking the log sequence in the identified log pattern in a pre-defined time-period with respect to a second pre-defined threshold, and a third condition for checking a count of the first plurality of logs in the identified log pattern with respect to a second plurality of logs included in a second log data file fetched in a preceding communication session, wherein the first log data file and the second log data file are associated with upgradation of the target server.

[0019] In one aspect, the message includes a recommendation indicating at least one of proceeding with the upgradation, stopping the upgradation, initiating a rollback for the upgradation, or performing an analysis for deciding for proceeding with the upgradation.

[0020] In one aspect, the processing module is configured to display the message on a User Interface (UI) of a user device.

[0021] In one aspect, based on the determination of one of the presence or the absence of the one or more critical logs in the first log data file, the log management module is configured to analyze an impact of the presence or absence of the one or more critical logs in the identified log pattern of the first plurality of logs on the upgradation. Furthermore, the log management module is configured to determine, based on the impact of the presence or absence of the one or more critical logs, a confidence score indicating a likelihood of a success or failure of the upgradation of the server environment.

[0022] In one aspect, the first plurality of logs includes information associated with upgradation of the target server.

[0023] In one aspect, the processing module is configured to initiate an Application Programming Interface (API) call request for establishing the communication session between the client and the target server. The API call request for establishing the communication session is initiated based on one of a reception of a user request at the processing module for monitoring logs corresponding to upgradation of the server environment, or a triggering of a scheduler at a pre-defined time interval.BRIEF DESCRIPTION OF DRAWINGS

[0024] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.

[0025] Fig. 1 illustrates an exemplary system for monitoring logs for upgradation of a server environment, in accordance with an embodiment of the present disclosure.

[0026] Fig. 2 illustrates a block diagram showing different components present in the client, in accordance with an embodiment of the present disclosure.

[0027] Fig. 3 illustrates a functional block diagram depicting interactions between components of the client with a user device and target servers, in accordance with an embodiment of the present disclosure.

[0028] Fig. 4 illustrates a flowchart depicting a method for monitoring logs for upgradation of the server environment, in accordance with an embodiment of the present disclosure.

[0029] Fig. 5 illustrates a schematic block diagram of a computing system 500 for monitoring logs for upgradation of the server environment, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION OF THE INVENTION

[0030] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.

[0031] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.

[0032] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” or “some implementations” which may each refer to one or more or all of the same or different embodiments or implementations. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” or “in an implementation” refers to one embodiment or one implementation and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments.” Further, the term, for example, “in one or more implementations” refers to “at least one implementation, or more than one implementation, or all implementations.

[0033] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.”

[0034] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, thatembodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features.

[0035] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.

[0036] In the disclosure, various embodiments are described using terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), xRadio Access Network (xRAN), and Open-Radio Access Network (0-RAN)), but these are merely examples for description. Various embodiments of the disclosure may also be easily modified and applied to other communication systems.

[0037] In order to facilitate an understanding of the disclosed invention, a number of terms are defined below.

[0038] Logs correspond to automatically produced and timestamped documentation of events relevant to a particular system. Logs include a wide range of data points about a system, such as processes, events, messages, and timestamps.

[0039] A log data file is a specific type of data file generated by resources such as operating systems, servers, applications and connected devices. The file includes logs and historical information about that particular resource's operations, activities and usage patterns. This information allows users, such as system admins or hardware developers, to assess the system's health and determine if it is operating properly.

[0040] Log pattern refers to a structured representation of one or more sequences, arrangements, or correlations among log entries extracted from the log data file, which are indicative of the operational behavior of a target server during a computing operation of the upgradation of the server environment.

[0041] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein the description and in the appended claims, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.

[0042] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure and the appended claims. Accordingly, unless otherwise defined, all terms, and especially any technical and / or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.

[0043] The present disclosure relates to a system and method for monitoring logs for upgradation of a server environment. The server environment may generally correspond to a plurality of servers coupled with network infrastructure and network elements, forming a part of one or more of a core network and a Radio Access Network (RAN) in the communication network.

[0044] The network infrastructure may correspond to any “node” referring to any component (or collection of components) configured to provide wireless access to a network. Examples of the node may include, but not limited to, a Transmit Point (TP), a Transmit-Receive Point (TRP), an Evolved Base Station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a Wi-Fi Access Point (AP), or other wirelessly enabled devices. The nodes may provide wireless access to the network in accordance with wireless communication protocols, e.g., 5G / NR 3GPP New Radio interface / access (NR), LTE, LTE-A, High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. Aspects of the present disclosure are intended to include, or otherwise cover, any technology (known or later developed) bearingsame or similar characteristics as of the above-mentioned BS, without deviating from the scope of the present disclosure. For the sake of convenience, the terms “nodes” and “gNBs” are used interchangeably in the present disclosure to refer to network infrastructure components that provide wireless access to remote terminals.

[0045] The core network may be communicably operational or may be integrated with the user device via the RAN. The core network may pertain to 5G servicebased architecture and may be configured to interconnect distinct networks associated with the architecture. Therefore, the core network provides a path for the exchange of information between one or more of the networks, and corresponding subnetworks.

[0046] The core network may comprises a plurality of network elements of the core network including an Access and Mobility Management Function (AMF) node (alternatively referred to as AMF), a Policy Control Function (PCF) node (alternatively referred to as PCF), an Equipment Identity Register (EIR) node (alternatively referred to as EIR), an Authentication Server Function (AUSF) node (alternatively referred to as AUSF), a Unified Data Management (UDM) function node (alternatively referred to as UDM), a Subscriber Profile Repository (SPR) node (alternatively referred to as SPR), a Short Message Service Function (SMSF) node (alternatively referred to as SMSF), a Network Slice Selection Function (NSSF) node (alternatively referred to as NSSF), a Location Management Function (LMF) node (alternatively referred to as LMF), a Session Management Function (SMF) node (alternatively referred to as SMF), a Network Data Analytics Function (NWDAF) node (alternatively referred to as NWDAF), a Charging Function-Proxy Control (CHF-PC) node (alternatively referred to as CHF -PC), a Network Exposure Function (NEF) node (alternatively referred to as NEF), a Signaling Transfer Point (STP) node (alternatively referred to as STP), a Diameter Routing Agent (DRA) node (alternatively referred to as DRA), a Binding Support Function (BSF) node (alternatively referred to as BSF), a Gateway Mobile Location Center (GMLC) node (alternatively referred to as GMLC), a User Plane Function (UPF) node(alternatively referred to as UPF), and a Location Services (LCS) client node (alternatively referred to as LCS).

[0047] The server environment may host network applications, software, and dockers including the 5G node applications, for providing various network services of the communication network. The server environment may be required to be regularly upgraded to maintain optimal functionality and performance of the communication network. For tracking progress of upgradation in the server environment or identification of a fault in the upgradation in the server environment, the logs generated during the upgradation may have to be monitored across one or more servers in the server environment.

[0048] An object of the present disclosure is to provide a centralized system and method for monitoring logs for upgradation of the server environment. Another object of the present disclosure is to provide a system and a method for log management during one or more of adding a new network node or network element in the server environment, deployment of an application over an existing network node or network element in the server environment, and docker upgradation in the server environment. Yet another object of the present disclosure is to provide the system and the method that streamlines monitoring of the upgradation of the server environments by utilizing automation scripts. Still another object of the present disclosure is to detect faults, errors, or failures, if any, during the upgradation of the server environment.

[0049] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. Fig. 1 through Fig. 4, discussed below, and the one or more embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0050] Fig. 1 illustrates an exemplary system 100 for monitoring logs for upgradation of a server environment, in accordance with an embodiment of the present disclosure. The system 100 comprises a server environment including a plurality of servers 102-1 to 102-n (alternatively referred to as “plurality of target servers 102”) coupled with a client 104 hosting a Network Operations Platform (NOP) 106. In one embodiment, the client 104 corresponds to a server connected with the plurality of servers 102 in a client-server model. The plurality of servers 102 may further be connected to the network elements and the plurality of network infrastructure (alternatively referred to as the nodes) forming a part of one of the core network or the RAN of the communication network. The plurality of servers 102 in the server environment are interconnected to each other.

[0051] The plurality of servers 102 may include a group of servers such as a cloudbased server, an application server, a content server, a host server, a web server, a database server, or a server hosted over a desktop computer. Examples of the plurality of servers 102 may include, but are not limited to, personal computers, laptops, mini-computers, mainframe computers, any non-transient and tangible machine that can execute a machine-readable code, cloud-based servers, distributed server networks, or a network of computer systems. The plurality of servers 102 may be realized through various web-based technologies such as, but not limited to, a Java web-framework, a .NET framework, a personal home page (PHP) framework, or any web-application framework.

[0052] In one embodiment, the server environment may correspond to a live cloud environment of the plurality of servers 102 coupled with the plurality of network elements and the plurality of nodes. In another embodiment, the plurality of servers may represent physical servers that are subject to the upgradation. For tracking progress of upgradation in the server environment or identification of a fault in the upgradation in the server environment, the logs generated during the upgradation may have to be monitored across the plurality of servers 102 in the server environment.

[0053] The NOP 106 provides an operating environment for updating and upgrading applications and services hosted at the plurality of server(s) 102. A target server among the plurality of servers 102 in the server environment may include one or more servers among the plurality of servers 102 where computing operations associated with the upgradation are to be performed. The upgradation of the target server may include computing operations corresponding to, but not limited to, software installations or re-installations, configuration changes, deployment of new applications, updating software configurations, deployment of new applications, deployment of new nodes, and system updates on the server environment. The NOP 106 may be hosted over the client 104 comprising a processor (not shown in Fig. 1) coupled to a memory (not shown in Fig. 1). The memory comprises various modules as described below to facilitate operations for log management. The processor interacts with various components for execution of the modules, thereby coordinating their functions for log management and analysis for upgradation of the server environments.

[0054] The system 100 further provides front-end services to a user i.e., a network operations team through a user device 108. The client 104 communicates with the user device 108 and the server environment through a network. The network may include wired connections, a combination of wired and wireless connections, or wireless connections utilizing communication protocols such as 5G / NR 3GPPNew Radio interface / access (NR), Long Term Evolution (LTE), LTE advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.

[0055] For the sake of convenience, the term “user device” used herein refers to an electronic device such as a network management console that wirelessly accesses the client 104 via the network. The user device 108 may include a desktop computer, portable computing devices such as laptops, tablet computers, handheld computer, mobile phones, wearable computers, or any other device suitable to provide front end services. The user device 108 may include portable computing devices such as laptops, tablet computers, handheld computer, mobile phones, and wearable computers. Through the front-end services of the user device 108, the user mayaccess the NOP 106 and input a user request for monitoring the logs corresponding to the upgradation of the server environment.

[0056] The front-end service may include a secured NOP User Interface (UI) (alternatively referred to as a “Graphical User Interface (GUI)” or “UI”) for accessing different functionalities of the system 100. The NOP UI may include a software or a web application for navigating the NOP 106 and accessing logs corresponding to the upgradation of the server environment. In a configuration, the user device 108 includes the UI for intuitive interaction, data processing units for real-time analysis, and storage units for data archiving. The NOP UI is configured to provide options to the network operations team to initiate operations for monitoring the logs and detecting a fault in upgradation of the server environment. The NOP UI is also configured to display the logs corresponding to the upgradation of the server environment.

[0057] The system 100 further comprises an Operations, Administration, and Maintenance (0AM) module 110 configured for an overall administration of the NOP 106. The 0AM module 110 is responsible for monitoring performance, troubleshooting issues, and ensuring that all the components of the system 100 are functioning correctly.

[0058] Furthermore, the system 100 comprises an Identity and Access Management (IAM) module 112 and an Elastic Load Balancing (ELB) module 114. The IAM module 112 is responsible for managing user authentication and authorization within the NOP 106 received via the user device 108. The IAM module 112 may ensure that only authorized users may access the system 100 and perform log management of the server environment.

[0059] The ELB module 114 is configured to distribute incoming user requests across the various components of the NOP 106 to ensure optimal performance and reliability of the system 100. The ELB module 114 dynamically adjusts the user request in accordance with traffic patterns in the system 100. Load balancing is particularly important during monitoring of the upgradation of the serverenvironment where upgradation of the plurality of servers is going on simultaneously and a large volume of data and commands are being tracked.

[0060] Although Fig. 1 shows exemplary components of the system 100, in other implementations, the system 100 may include fewer components, different components, differently arranged components, or additional components than depicted in Fig. 1. Additionally, or alternatively, one or more components of the system 100 may perform functions described as being performed by one or more other components of the system 100.

[0061] Fig. 2 illustrates a block diagram 200 showing different components present in the client 104, in accordance with an embodiment of the present disclosure. The client 104 may comprise at least one processor 202 (alternatively referred to as a processor 202), a memory 204, interface(s) 206, a database 208, and a plurality of processing units 210 (collectively referred to as “processing units 210”). Components of the client 104 are coupled to each other via a communication bus (not shown in Fig. 2). Other embodiments of the client 104 may be used without departing from the scope of this disclosure.

[0062] In an embodiment, the client 104 may be configured as an application server and may be communicably operational or may be integrated with the NOP UI via the network. The network may provide a path for the exchange of information between the client 104, the NOP UI, and the target servers 102.

[0063] The processor 202 may correspond to one or more general purpose processors and / or one or more special purpose processors such as digital signal processors, Field Programmable Gate Array (FPGA) processor, a microprocessor, a digital signal processor, an application specific integrated circuit, a microcontroller, a state machine, or ay any type of programmable logic array.

[0064] The processor 202 may include various processing circuitry and communicates with the memory 204, the interface(s) 206, the database 208, and the processing units 210 via the communication bus. Examples of the communicationbus may include, but are not limited to, a Peripheral Component Interconnect (PCI)ZPCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), and a Front Side Bus (FSB). Aspects of the present disclosure are intended to include or otherwise cover any type of coupling means present or related to later developed technologies, that may be configured to connect the processor 202 to the other subsystems of the client 104 without deviating from the scope of the present disclosure.

[0065] The processor 202 is configured to execute instructions stored in the memory 204 and to perform various processes. The processor 202 may also include a plurality of processing engines i.e., information processing units for controlling overall operation of the client 104. For example, the processor 202 is configured to execute programs and other processes stored in the memory 204. The processor 202 is further configured to move data into or out of the memory 204 as required by an execution process.

[0066] The memory 204 may store program instructions for performing several functions through which log management for upgradation of the server environment may be performed, by the processor 202. A part of the memory 204 may include non-volatile storage elements. Examples of non-volatile storage elements may include, but are not limited to, non-volatile or non-transitory computer-readable storage devices such as hard drives, magnetic tape, floppy diskettes, optical disks, Compact Disc Read-Only Memories (CD-ROMs), and magneto-optical disks, semiconductor memories, such as ROMs, Random Access Memories (RAMS), Programmable Read-Only Memories PROMs), Erasable PROMs (EPROMs), Electrically Erasable PROMs (EEPROMs), flash memory, magnetic or optical cards, or other type of media / machine -readable medium suitable for storing electronic instructions. The "non-transitory" computer-readable medium is not embodied in a carrier wave or a propagated signal. However, the term "non- transitory" should not be interpreted as the memory 204 is non-movable. In some examples, the memory 204 can be configured to store larger amounts of information. In certain examples, a non-transitory storage medium may store data that can, overtime, change (e.g., in RAM or cache). The memory 204 can be an internal storage unit or it can be an external storage unit of the client 104, cloud storage, or any other type of external storage. In some embodiments, when the memory 204 is external to the client 104, the memory 204 may be removably attached to the client 104. Aspects of the present disclosure are intended to include or otherwise cover any data storage medium as “the memory 204”, without deviating from the scope of the present disclosure.

[0067] The processor 202 is configured to utilize output generated by a rule-based model 204-2 stored in the memory 204. The rule-based model 204-2 may include, but not limited to, an unsupervised, a semi -supervised, a supervised model or reinforcement machine learning model. In one embodiment, the rule-based model 204-2 may be a pre-trained machine learning model. The processor 202 is further configured for executing instructions stored in the memory 204. The memory 204 may store program instructions for performing several functions through which the logs may be monitored.

[0068] In an embodiment, the processing units 210 may be implemented as a combination of hardware and software programming (for example, programmable instructions) to implement one or more functionalities of the client 104. In nonlimiting examples, described herein, such combinations of hardware and software programming may be implemented in several different ways, without deviating from the scope of the present disclosure. The processing units 210 may include suitable logic, circuitry, interfaces, and / or codes. For example, the programming for the processing units 210 may be processor-executable instructions stored on a non- transitory machine-readable storage medium and the hardware for the processing units 210 may comprise a processing resource (for example, one or more processors), to execute such instructions. In an embodiment, the processing units 210 may be combined to a single module or each module of the processing units 210 may be further subdivided into different processing units 210.

[0069] In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing units 210. In such examples, the client 104 may also comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the server 140 and the processing resource. In other examples, the processing units 210 may be implemented using an electronic circuitry.

[0070] In one or more embodiments, the processing units 210 may include one or more modules such as a processing module 212, a Method of Procedure (MOP) management module 214, a server management module 216, an execution module 218, ancillary modules 220, and a log management module 222.

[0071] The processing module 212 is configured to facilitate automatic configuration of the target servers 102 with updated services, applications, and dockers. The upgradation of the server environment may include multiple operations such as, but not limited to, software installations or re-installations, configuration changes, deployment of new applications, updating software configurations, deployment of new applications, deployment of new nodes, and system updates on the server environment. The processing module 212 is also configured to establish a communication session with the target servers 102 for facilitating automatic configuration.

[0072] The MOP management module 214 is configured to manage creation, storage, and execution of scripts. The scripts may correspond to operations for upgrading the server environment. In one implementation, the scripts may comprise an orderly list of operations to be performed repeatedly over the target servers 102. The scripts follow a YAML Ain't Markup Language (YAML) format.

[0073] The server management module 216 is configured to manage identity information corresponding to each target server of the target servers 102. The identity information may include a hardware address of a target server, a virtualidentifier of a target server, and a local Internet Protocol (IP) address of a target server. The server management module 216 is further configured to perform an automatic login to the target servers 102 for the log management of the target servers 102.

[0074] In another embodiment, the ancillary modules 220 may include identity management modules that enables a secure and successful access to the logs of the target server. For accessing the logs, the identity management modules may authenticate the target server or an instances of the target server through various identifiers to uniquely locate the target server or instances of the target servers. Such identifiers may include IP addresses, hardware addresses (for an example, Media Access Control (MAC address), or virtual identifiers.

[0075] The execution module 218 is configured to ensure that the tasks specified in the operational procedures and / or the scripts for upgradation of the one or more applications, services, and dockers, are conducted efficiently and accurately on each target server of the target server 102.

[0076] The ancillary modules 220 may further include modules for performing additional functionalities such as configuration management module and history management module. The configuration management module is configured to store configuration settings of the target servers 102 and perform specific tasks on the target servers 10. The history management module is configured to maintain a historical record of all the operational procedures executed within the system 100. The history management module may store additional details corresponding to the target servers 102, the automation scripts used, timelines for execution of the automation scripts, and outcomes corresponding to execution of each operational procedure.

[0077] The log management module 222 is configured to fetch progress of upgradation of the server environment through a log data file. The log data file may comprise log data including a plurality of logs. The log management module 222 is responsible for recording all activities related to changes in the execution of theoperational procedures, including any errors or issues encountered. The log management module 222 is further configured to determine one of a presence or an absence of one or more critical logs in the log data file based on the output of the rule-based model 204-2 and provide a message indicating one of the presence or the absence of the one or more critical logs to the user device 120 via the processing module 212.

[0078] The database 208 stores the log data files fetched from the target servers, request configuration of the user for log management, the historical records, configuration settings, the automation scripts executed for the upgradation, identity of the target servers 102, and login details of the target servers 102. The database 208 is accessed by various components of the processor 202, such as the log management module 222 to store the log files fetched from the target servers 102.

[0079] The database 208 may be implemented as a centralized database, Relational Database Management System (RDBMS), Non-Relational Database Management System, Hierarchical Database Management System, Network Database Management System, an in-memory database including a distributed in-memory data storage, distributed database, or a distributed file system. It must be understood that in other embodiment, the client 104 may be communicatively coupled with the one or more databases hosted outside of the client 104.

[0080] The interface(s) 206 may include a variety of interfaces such as a communication pathway for one or more components of the client 104, an Input / Output interface, and communication interface. The I / O interface is configured to connect the processor 202 with I / O devices, storage devices, and the like.

[0081] The I / O interface may include suitable logic, circuitry, interfaces, and / or codes that may be configured to receive input(s). For example, the I / O interface may have an input interface and an output interface. The I / O interface may be configured to enable the user to provide a user request for monitoring the loges in the server environment. Examples of the input interface may include, but are not limited to, atouch interface, a mouse, and a keyboard, and the output interface includes a digital display, an analog display, or a touch screen display. Through the output interface, the user may see the logs generated in the server environment and receive a message indicating a likelihood of success or failure of the upgradation process. Aspects of the present disclosure are intended to include or otherwise cover any type of the I / O interface including known, related art, and / or later developed technologies without deviating from the scope of the present disclosure.

[0082] The communication interface includes an electronic circuit specific to a standard that enables wired or wireless communication. The communication interface is configured to facilitate communication of one or more components of the client 104 with external devices via the network.

[0083] Although Fig. 2 illustrates one example of client 104, various changes may be made to Fig. 2. For example, the client 104 may include any number of components in addition to the components shown in Fig. 2. Further, various components in Fig. 2 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs. Functioning of the plurality of modules for log management for upgradation of the server environment is described in greater detail further below.

[0084] Fig. 3 illustrates a functional block diagram depicting interactions between components of the client 104 with the user device 108 and the target servers 102, in accordance with an embodiment of the present disclosure. As illustrated in Fig. 3, the NOP 302 (same as NOP 106) may further host an automation adoption platform 304 and ancillary modules 306 (same as ancillary modules 220). The automation adoption platform 304 comprises a processing module 308 (same as processing module 212) for automating operations for upgrading the server environment within the NOP 302 and a log management module 310 (same as log management module 222) for log management of the upgradation of the server environment.

[0085] During operation of the server environment, the user may perform upgradation of the server environment by accessing a NOP UI 312 from the userdevice 108 and providing an input on basis of user requirement. Upon receiving the input, a MOP management module 314 (same as MOP management module 214) of the automation adoption platform 304, interacts with the processing module 308 to ensure that the operational procedures for upgradation of one or more of applications, services, and dockers are accurately defined based on user-configured parameters.

[0086] Once the operational procedures are created, the MOP management module 314 coordinates with a server management module 316 (same as the server management module 216) of the automation adoption platform 304, to automatically login to the target servers 102. After the login, an execution module 318 (same as the execution module 218) of the automation adoption platform 304, executes the operational procedures on the target servers 102 for upgradation of the server environment for upgradation of the one or more applications, services, and dockers accurately on each target server of the target servers 102.

[0087] In one embodiment, upon receiving a user request for monitoring upgradation of the server environment through the NOP UI 312 of the user device 120, the processing module 308 initiates an Application Programming Interface (API) call request to establish a communication session with the target servers 102. In another embodiment, the processing module 308 is triggered by a scheduler to initiate an API call request to establish a communication session with the target servers 102, at a pre-defined time interval.

[0088] The communication session may be established by the processing module 308 through an automatic login to the target server 102 via the server management module 316. In one embodiment, the processing module 308 may receive from the server management module 316, a resolved IP address of the target server 102 of the server environment with which the communication session is to be established. Based on the received IP address, the processing module 308 then establishes the communication session between the client 104 and the target server 102.

[0089] Upon establishment of the communication session, the log management module 310 fetches the log data file comprising the plurality of logs, from the target server 102. The plurality of logs includes information associated with one or more computing operations performed on the target server 102. The computing operations may include operations for updating services, applications, and dockers in the server environment, software installations, updating software versions, configuration changes, deployment of new applications, and system updates on the server environment.

[0090] In one embodiment, the log management module 310 is configured to utilize a rule-based model for identifying a log pattern of the plurality of logs by analyzing the log data file using the rule-based model 204-2. The rule-based model 204-2 may include, but is not limited to, a Machine Learning (ML) model, an Artificial Intelligence (Al) model, an algorithmic model, a computational model, and a neural network. In one embodiment, the rule-based model based on statistical algorithms may be used. In one embodiment, the rule-based model may correspond to the ML model and henceforth be alternatively referred to as ML model. It must be understood that although usage of the ML model is merely described as an example, it is possible to utilize other rule-based models.

[0091] In one embodiment, the log pattern may correspond to a generalized representation of a recurring structure or sequence in the plurality of logs that reflects a specific behavior of the target server 102. The behavior may indicate, for an example, a successful server startup, a failed authentication attempt, or a software upgrade process. The log pattern may comprise a structural pattern including logs having same format or fields such as message, timestamp, or a log level, a sequential pattern including logs indicating specific order of events, a temporal pattern including events occurring within a defined time window, or a semantic pattern including logs having similar meaning or intent across different data.

[0092] The rule -based model 204-2 may comprise a machine learning component to perform a plurality of machine learning and deep learning operations on the onthe dataset. In one embodiment, the rule -based model 204-2 may include one or more models based on linear regression, logistic regression, decision trees, random forest, Support Vector Machines (SVM), neural networks, K-Means clustering, hierarchical clustering, Density-Based Spatial Clustering of Applications with Noise (DBSCAN), Apriori Algorithm, and Principal Component Analysis (PCA). Further, the processor 202 may also be configured to fine-tune the rule-based model 204-2 as per requirement of network operators.

[0093] The rule-based model 204-2 may group the plurality of logs in clusters of similar logs and may identify the log pattern from the clusters based on parameters such as a frequency of occurrence of logs, a timestamp of logs, or a similarity of messages of logs. The log pattern may include temporal sequences, frequency distributions, or event correlations that characterize the target server's response to an upgradation process or other computing operations. The log pattern may help in detecting trends or identifying anomalies or deviations from expected patterns of logs generated during the upgradation process. In another embodiment, the rulebased model 204-2 may be re-trained based on a feedback corresponding to the detected trends or anomalies in the identified pattern.

[0094] For an example, logs including messages such as "connection refused", "timeout", "null pointer" may indicate a semantic log pattern of an anomaly in the upgradation process. In another scenario, logs including messages such as "initialized", "completed" may indicate a semantic log pattern of a successful upgradation process. Furthermore, a frequent occurrence of logs including messages such as “connection refused", "timeout", and "null pointer” may indicate a temporal log pattern of an anomaly in the upgradation process.

[0095] Further, the rule-based model 204-2 may group logs such as upgrade started, backing up configuration, applying patch, restarting services, upgrade completed successfully, and analyze the order of the logs to identify a behavioral log pattern indicating expected sequence of logs from the plurality of logs.

[0096] From the identified log pattern, the log management module 310 is configured to determine based on a pre-defined criteria, one of a presence or an absence of one or more critical logs from the identified log pattern of the plurality of logs in the log data file. The presence or absence of the one or more critical logs is determined based on the pre-defined criteria, including log sequence thresholds, time-based conditions, and comparative analysis with prior log data files. The predefined criteria may be selected or set by the network operator via the NOP UI 312 based on a requirement of the network operator.

[0097] In one embodiment, the pre-defined criteria may include a first condition for checking a count of a log or a count of a log sequence in the identified log pattern with respect to a first pre-defined threshold. The first pre-defined threshold corresponds to pre-defined log or sequence of logs associated with a type of computing operation in a target server among the plurality of target servers 202. The first pre-defined log or sequence of logs may be set based on a requirement of the network operator. For an example, in one scenario, for implementing an upgrade at the AMF node, the first pre-defined threshold logs may be “backing up configuration, applying patch, restarting services”. The log management module 310 is configured to determine whether the logs same as the first pre-defined threshold is present or absent in the identified log pattern. Further, based on the determination that the logs same as the first pre-defined threshold are present, the log management module 310 is configured to determine whether the logs are present in a same sequence as the first pre-defined threshold. Thereafter, the log management module 310 is configured to determine a count of times the logs are present in a same sequence as the first pre-defined threshold.

[0098] In another embodiment, the pre-defined criteria may include a second condition for checking the log sequence in the identified log pattern in a pre-defined time-period with respect to a second pre-defined threshold. The second pre-defined threshold corresponds to pre-defined sequence of logs associated with a type of computing operation in a target server among the plurality of target servers 202 occurring in a specific time window of initiation of the computing operation. Thesecond pre-defined sequence of logs may be set based on a requirement of the network operator. The pre-defined time-period corresponds to the specific time window of initiation of the computing operation. The log management module 310 is configured to determine whether the logs same as the second pre-defined threshold is present or absent in the identified log pattern. Further, based on the determination that the logs same as the second pre-defined threshold are present, the log management module 310 is configured to determine whether the logs are present in a same sequence as the second pre-defined threshold. Further, based on the determination that the logs same as the second pre-defined threshold are present in the same sequence, the log management module 310 is configured to check using the timestamp of the log entries to determine whether the logs occur in the predefined time-period.

[0099] In another embodiment, the log management module 310 is configured to detect a change in one or more log lines of the plurality of the logs with respect to a log data file fetched from a preceding communication session by checking a count of the log lines of the plurality of the logs. In another embodiment, the log management module 310 is configured to monitor progress of upgradation of the server environment from the log data file and detect a change in count of the one or more log lines of the plurality of the logs with respect to a default configuration file of the target server 102. To determine the change, the log management module 310 may read the log file line by line and count the number of log lines. Thereafter, based on the count of the number of log lines, the log management module 310 is configured to determine whether new log lines with respect to the log data file fetched from the preceding communication session. Both the log data file and the log data file fetched from the preceding communication session corresponds to a same computing operation among one or more computing operations performed on the target server.

[0100] For example, the log data file fetched from the preceding communication session comprises log lines 1 to 20 of the computing operation. The log management module 310 is configured to count the plurality of the logs in the log file and detecta change in one or more log lines with respect to a log data file fetched from the preceding communication session. The log management module 310 may determine whether the log data files comprise log lines after 20 of the computing operation.

[0101] When one or more of the pre-defined criteria is satisfied, the log management module 310 is configured to determine the presence or absence of the one or more critical logs from the identified pattern. The one or more critical logs may refer to specific set of log entries within the identified log pattern that are essential for evaluating success, or failure of a server upgradation process.

[0102] The presence or absence of critical logs is determined based on one or more pre-defined criteria, including log sequence thresholds, time -based conditions, and comparative analysis with prior log data files. The one or more critical logs may include, but is not limited to, logs such as error messages, success confirmations, rollback triggers, or security alerts. For an example, “Backup failed due to insufficient disk space”, “Service restart failed - missing configuration file”, and “upgrade validation failed - service not responding”. Critical logs may indicate successful execution of upgrade steps, occurrence of errors, or system-level warnings that impact an outcome of the upgradation.

[0103] The log management module 310 is configured to analyze an impact of the presence or absence of the one or more critical logs in the identified log pattern of the plurality of logs on the upgradation.

[0104] In a first scenario, based on the pre-defined criteria, presence of the one or more critical logs may indicate a successful upgradation of the server environment. For an example, presence of logs such as “patch applied” in a first two minutes of an installation process at the target server may indicate the successful upgradation.

[0105] In a second scenario, based on the pre-defined criteria, presence of the one or more critical logs may indicate a failure of upgradation of the server environment. For an example, presence of logs such as “missing configuration file” multiplenumber of times in a first two minutes of an installation process at the target server may indicate the failure of upgradation.

[0106] In a third scenario, based on the pre-defined criteria, absence of the one or more critical logs may indicate a successful upgradation of the server environment. For an example, absence of logs such as “service not responding” in a first two minutes of an installation process at the target server may indicate the successful upgradation.

[0107] In a fourth scenario, based on the pre-defined criteria, absence of the one or more critical logs may indicate a failure upgradation of the server environment. For an example, absence of logs such as “backup completed” in an installation process at the target server may indicate the failure of the upgradation.

[0108] In one embodiment, upon a determination, that the one or more critical logs are absent, the log management module 310 is configured to perform the determination for the presence of the one or more critical logs at a periodic interval until one of an expiry of the pre-defined time -period based on the pre-defined criteria or until the result of the determination indicates the presence of the one or more logs in the pre-defined sequence.

[0109] Based on the impact of the presence or absence of the one or more critical logs, the log management module 310 is configured to determine a confidence score indicating a likelihood of a success or failure of the upgradation of the server environment.

[0110] The confidence score may be determined based on the presence or absence of one or more critical logs within the identified log pattern. In one embodiment, the confidence score may be computed by analyzing an impact of the presence or the absence of the one or more critical logs such as error logs or warning logs against deviations in expected log sequence or timing of the log pattern based on the predefined criteria. In another embodiment, the confidence score may also be computed based on a comparison with previous logs of a previous successful upgradationassociated with the computing operation in the plurality of target servers 202. The computing score may be derived using a weighted model accounting for a severity of the one or more critical logs and a frequency of occurrence of the one or more critical logs, as well as comparative analysis with historical log data from previous upgrade sessions.

[0111] The confidence score may be assigned from 0 to 1, 0 indicating an expected upgrade failure and 1 indicating an expected successful upgrade. For example, a confidence score of 0.95 may be assigned when all the critical logs are present in the correct order and time frame, indicating a high probability of successful upgradation. In another scenario, a score of 0.30 may be assigned when multiple one or more critical logs are detected, such as backup failure, service restart failure, and validation failure, suggesting a high likelihood of upgrade failure.

[0112] Further, based on the confidence score, the log management module 310 may determine whether to proceed with the upgradation, halt the upgradation, initiate a rollback for the upgradation, or perform further analysis for proceeding with the upgradation.

[0113] The log management module 310 sends a result of the determination of one of the presence or the absence of the one or more critical logs to the processing module 308. Based on a result of the determination, the processing module 308 is configured to generate a message indicating one of the presence or the absence of the one or more critical logs for displaying to the user through the NAP UI 312, or a change in the count of the one or more logs. The message further includes a recommendation indicating at least one of proceeding with the upgradation, stopping the upgradation, initiating a rollback for the upgradation, or performing an analysis for deciding for proceeding with the upgradation.

[0114] Although FIG. 3 illustrates one example of client 104, various changes may be made to FIG. 3. For example, the client 104 may include any number of components in addition to the components shown in FIG. 3. Further, various components in FIG. 3 may be combined, further subdivided, or omitted andadditional components may be added according to particular needs. A detailed description of the method for monitoring logs for upgradation of the server environment is described further below.

[0115] Fig. 4 illustrates a flowchart depicting a method 400 for monitoring logs for upgradation of the server environment, in accordance with an embodiment of the present disclosure. The method 400 depicts operational steps 402-412 performed by the system 100 for monitoring logs for upgradation of the server environment. Although the method 400 shows example blocks of steps 402 to 412, in some embodiments, the method 400 may include additional steps, fewer steps or steps in different order than those depicted in Fig. 4. In other embodiments, the steps 402- 412 may be combined or may be performed in parallel.

[0116] At step 402, on triggering of the scheduler at a pre-defined time interval for log management corresponding to the upgradation of the server environment, the processing module 308 initiates the API call request for establishing the communication session between the client 104 and a target server of the plurality of target servers 102 in the server environment. In one embodiment, the pre-defined time interval may correspond to 1 (one) second.

[0117] In another embodiment, the processing module 308 initiates the API call request for establishing the communication session between the client 104 and the target server on reception of the user request at the processing module 308 for monitoring logs corresponding to upgradation of the server environment through the NOP UI 312. The communication session may be established by performing an automatic login operation to the target servers 102 via the server management module 316.

[0118] In one scenario, during docker upgradation at the target servers 102 through execution of automation scripts, the logs of upgradation performed are stored in a directory at the target servers 102. The logs of upgradation may be stored in a file format in the directory of a respective target server of the target servers 102.

[0119] In another scenario, during upgradation of application at the target servers 102, the logs of upgradation performed are captured in the application at the target servers 102. The logs are stored with node-level details served by the target server of the target servers 102 in a configuration file.

[0120] At step 404, upon establishment of the communication session, the log management module 310 fetches a first log data file. The first log data file comprises a first plurality of logs includes information associated with one or more computing operations performed on the target server of the target servers 102. The first plurality of logs includes logs of the upgradation operation from the target servers 102. The computing operations comprises execution of one or more automation scripts associated with a software installation process and a system upgradation process in the server environment. The first log data file may be one or more of the configuration file and the file stored at the directory. In a non-limiting example, the first log data file may be transferred from the target servers of the target servers 102 to the NOP 106, 302 via Secured File Transfer Protocol (SFTP).

[0121] In one embodiment, by the log management module 310 may dynamically adjust a frequency of fetching the first log data file based on one of an event, an activity of the target server, and a log generation rate. The frequency may be increased in case of unusual activity in the target server and increase a rate of monitoring of the logs for the upgradation.

[0122] At step 406, the log management module 310, using the rule-based model 204-2 reads the log file fetched from the target servers 102 and identifies a log pattern of the first plurality of logs by analyzing the first log data file. The log pattern may indicate the temporal sequences, frequency distributions, or event correlations that characterize the target server's response to an upgradation process or other computing operations.

[0123] At step 408, based on the pre-defined criteria, the log management module 310 determines one of the presence or the absence of the one or more critical logs from the identified log pattern of the first plurality of logs in the first log data file.The pre-defined criteria may be set in the NOP 302, via the NOP UI 312. The predefined criteria may include a plurality of conditions, one or more of which need to be satisfied to determine the presence or the absence of the one or more critical logs. A first condition of the plurality of conditions may include checking a count of a log or a count of a log sequence in the identified log pattern with respect to the first predefined threshold. A second condition of the plurality of conditions may include checking the log sequence in the identified log pattern in the pre-defined time-period with respect to a second pre-defined threshold. A third condition of the plurality of conditions may include checking a count of the first plurality of logs in the identified log pattern with respect to the second plurality of logs included in a second log data file fetched in the preceding communication session. In another embodiment, the change in one or more logs may be determined with respect to a default configuration setting file of the target server of the plurality of target servers 102 stored at the NOP 106, 302. The first log data file and the second log data file are associated with a computing operation among one or more computing operations performed on the target server.

[0124] The log management module 310 may read the first log data file line by line in a sequential manner and determine the presence or the absence of the one or more critical logs. Based on the determination of the presence or the absence of the one or more critical logs, the log management module 310 may generate the confidence score for generating one or more recommendations for the network operator associated with the upgradation process.

[0125] At step 410, upon determining the presence or the absence of the one or more critical logs, the processing module 308, generates the message indicating one of the presence or the absence of the one or more critical logs. The message may also include the recommendation indicating at least one of a suggestion for proceeding with the upgradation, stopping the upgradation, initiating a rollback for the upgradation, or performing an analysis for deciding for proceeding with the upgradation.

[0126] At step 412, the processing module 308 may control the user device 108 to display one or more of the message and the one or more critical logs in the first plurality of log lines on the NOP UI 312 of the user device 108. The processing module 212, 308 may send the one or more of the message and the one or more critical logs of the first log data file to the user device 108 via a transmission protocol. In one embodiment, the transmission protocol may correspond to a web socket connection providing a simultaneous two-way communication over a single transmission control connection between the processing module 308 and the user device 108.

[0127] In another embodiment, the processing module 308 prints the logs to the NOP UI 312. The network operations team may access and view the logs from the NOP UI 312. The network operations team may monitor and analyze the changes in the logs through the NOP UI 312. The network operations team may change a predefined time interval to view the message indicating presence or absence of the one or more critical logs on basis of their requirement. Further, the network operations team may track the progress of the upgradation of the server environment in realtime and detect a fault or an error in the upgradation at any target server among the target servers 102.

[0128] Although method 400 shows example blocks of steps 402 to 410, in some embodiments, the method 400 may include additional steps, fewer steps or steps in different order than those depicted in Fig. 4. In other embodiments, the steps 402 through 410 may be combined or may be performed in parallel.

[0129] Fig. 5 illustrates a schematic block diagram of a computing system 500 for monitoring logs for upgradation of the server environment, in accordance with an embodiment of the present disclosure.

[0130] The computing system 500 includes a network 502, a network interface 504, a processor 506 (similar in functionality to the processor 202 of Fig. 2), an Input / Output (I / O) interface 508 (similar in functionality to the I / O interface 205 of Fig. 2), and a non-transitory computer readable storage medium 510 (hereinaftermay also be referred to as the “storage medium 510” or the “storage media 510”). The network interface 504 includes an Ethernet card, Universal Serial Bus (USB), a communication port, or a Personal Computer Memory Card International Association (PCMCIA) slot and card.

[0131] The processor 506 may include various processing circuitry / modules and communicate with the storage medium 510 and the I / O interface 508. The processor 506 is configured to execute instructions stored in the storage medium 510 and to perform various processes for monitoring logs for upgradation of the server environment. The processor 506 may include an intelligent hardware device including a general-purpose processor, such as, for example, and without limitation, the CPU, the AP, the dedicated processor, or the like, the graphics-only processing unit such as the GPU, the microcontroller, the FPGA, the programmable logic device, the discrete hardware component, or any combination thereof. The processor 506 may be configured to execute computer-readable instructions 510-1 stored in the storage medium 510 to cause the system 300 to perform various functions disclosed throughput the disclosure.

[0132] The storage medium 510 stores a set of instructions i.e., computer program instructions 510-1 (hereinafter may also be referred to as instructions 510-1) required by the processor 506 for controlling its overall operations. The storage media 510 may include an electronic storage medium, a magnetic storage medium, an optical storage medium, a quantum storage medium, or the like. For example, the storage media 510 may include, but are not limited to, hard drives, floppy diskettes, optical disks, ROMs, RAMs, EPROMs, EEPROMs, flash memory, magnetic or optical cards, solid-state memory devices, or other types of physical media suitable for storing electronic instructions. In one or more embodiments, the storage media 510 includes a Compact Disk-Read Only Memory (CD-ROM), a Compact Disk- Read / Write (CD-R / W), and / or a Digital Video Disc (DVD). In one or more implementations, the storage medium 510 stores computer program code configured to cause the computing system 500 to perform at least a portion of the processes and / or methods disclosed herein throughput the disclosure.

[0133] Embodiments of the present disclosure have been described above with reference to flowchart illustrations of methods and systems according to embodiments of the disclosure, and / or procedures, algorithms, steps, operations, formulae, or other computational depictions, which may also be implemented as computer program products. In this regard, each block or step of the flowchart, and combinations of blocks (and / or steps) in the flowchart, as well as any procedure, algorithm, step, operation, formula, or computational depiction can be implemented by various means, such as hardware, firmware, and / or software including one or more computer program instructions embodied in computer-readable program code. As will be appreciated, any such computer program instructions may be executed by one or more computer processors, including without limitation a general -purpose computer or special purpose computer, or other programmable processing apparatus to perform a group of operations comprising the operations or blocks described in connection with the disclosed method.

[0134] Further, these computer program instructions, such as embodied in computer-readable program code, may also be stored in one or more computer- readable memory or memory devices (for example, the memory 204 or the storage medium 510) that can direct a computer processor or other programmable processing apparatus to function in a particular manner, such that the instructions 510-1 stored in the computer-readable memory or memory devices produce an article of manufacture including instruction means which implement the function specified in the block(s) of the flowchart(s).

[0135] It will further be appreciated that the term “computer program instructions” as used herein refer to one or more instructions that can be executed by the one or more processors (for example, the processor 202 or the processor 506) to perform one or more functions as described herein. The instructions 510-1 may also be stored remotely such as on a server, or all or a portion of the instructions can be stored locally and remotely.

[0136] Now, referring to the technical abilities and advantageous effect of the present disclosure, operational advantages that may be provided by one or more embodiments is that the system and the method disclosed herein significantly increases operational efficiency of the communication network by allowing the network operators’ team to monitor progress of the upgradation of the server environment by identifying the presence or the absence of the one or more critical logs. The system overcomes the need for manual monitoring of the upgradation in the server environment and reduces the time and effort in keeping a track of the upgradation.

[0137] Further, the disclosed system and the method pre-emptively provides the recommendations for the network operators associated with a likelihood of success or a failure of the upgradation process, enabling the network operators to optimize and schedule other related maintenance activities for the target servers.

[0138] Another noteworthy advantage provided by the one or more embodiments may include, but is not limited thereto, that the upgradation of the plurality of the servers are monitored at a centralized interface at a single click of the user. Further, the present disclosure allows the network operations team to monitor the upgradation and detect a fault in the upgradation in real time, ensuring that upgradation is performed consistently and correctly across all the target servers in one go.

[0139] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.

[0140] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certainelements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.

[0141] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.LIST OF REFERENCE NUMERALS

[0142] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is:100 - Exemplary system for monitoring logs for upgradation of a server environment102 - Plurality of target servers104 - Client106 - Network Operation Platform (NOP)108 - User device110 - Operations, Administration, Maintenance Module112 - Identity and Access Management Module114 - Elastic Load Balancing Module200 - Block diagram showing different components present in the client202- Processor204 - Memory204-2 - Rule-based model206 - Interface208 - Database210 - Processing Unit212 - Processing module214 - Method of Procedure Management module216 - Server Management module218 - Execution module220 - Ancillary module222- Log management module300 - Functional block diagram depicting interactions between components of the client with a user device and target servers302 - Network Operations Platform (NOP)304 - Automation Adoption Platform306- Ancillary modules308 - Processing module310 - Log management module312 - NOP User Interface (UI)314 - Method of Procedure Management module316 - Server Management module318 - Execution module400- Flowchart for monitoring logs for upgradation of the server environment402-412 - Operation steps of the method 400500 - Block diagram of a computing system502 - Network504 - Network interface506 - Processor508 - Input / Output (I / O) interface510 - Non-transitory computer readable storage medium 510-1 - Set of instructions

Claims

WE CLAIM:

1. A method (400) for monitoring logs for upgradation of a server environment, the method (400) comprising: establishing, by a processing module (212, 308), a communication session between a client (104) and a target server of a plurality of target servers (102) in the server environment; fetching, by a log management module (222, 310), upon establishment of the communication session, a first log data file comprising a first plurality of logs from the target server; identifying, by the log management module (222, 310), a log pattern of the first plurality of logs by analyzing the first log data file using a rule -based model; determining, by the log management module (222, 310) based on a predefined criteria, one of a presence or an absence of one or more critical logs from the identified log pattern of the first plurality of logs in the first log data file; and generating, by the processing module (212, 308) based on a result of the determination, a message indicating one of the presence or the absence of the one or more critical logs.

2. The method (400) as claimed in claim 1, wherein the pre-defined criteria include one or more of: a first condition for checking a count of a log or a count of a log sequence in the identified log pattern with respect to a first pre-defined threshold; a second condition for checking the log sequence in the identified log pattern in a pre-defined time-period with respect to a second pre-defined threshold; and a third condition for checking a count of the first plurality of logs in the identified log pattern with respect to a second plurality of logs included in a second log data file fetched in a preceding communication session, wherein the first log data file and the second log data file are associated with upgradation of the target server.

3. The method (400) as claimed in claim 1, wherein the message includes a recommendation indicating at least one of proceeding with the upgradation, stopping the upgradation, initiating a rollback for the upgradation, or performing an analysis for deciding for proceeding with the upgradation.

4. The method (400) as claimed in claim 1, comprising displaying, by the processing module (212, 308), the message on a User Interface (UI) (312) of a user device (308).

5. The method (400) as claimed in claim 1, based on the determination of one of the presence or the absence of the one or more critical logs in the first log data file, the method comprises: analyzing, by the log management module (222, 310), an impact of the presence or absence of the one or more critical logs in the identified log pattern of the first plurality of logs on the upgradation; and determining, by the log management module (222, 310) based on the impact of the presence or absence of the one or more critical logs, a confidence score indicating a likelihood of a success or failure of the upgradation of the server environment.

6. The method (400) as claimed in claim 1, wherein the first plurality of logs includes information associated with the upgradation of the target server.

7. The method (400) as claimed in claim 1, comprising: initiating, by the processing module (212, 308), an Application Programming Interface (API) call request for establishing the communication session between the client and the target server, wherein the API call request for establishing the communication session is initiated based on one of a reception of a user request at the processing module (212, 308) for monitoring logs corresponding to upgradation of the server environment, or a triggering of a scheduler at a pre-defined time interval.

8. A system (100) for monitoring logs for upgradation of a server environment, the system (100) comprising: a processing module (212, 308) configured to establish a communication session between a client (104) and a target server of a plurality of target servers (102) in the server environment; and a log management module (222, 310) configured to: fetch, upon establishment of the communication session, a first log data file comprising a first plurality of logs from the target server; identify a log pattern of the first plurality of logs by analyzing the first log data file using a rule-based model; and determine, based on a pre-defined criteria, one of a presence or an absence of one or more critical logs from the identified log pattern of the first plurality of logs in the first log data file, wherein the processing module (212, 308) is configured to generate, based on a result of the determination, a message indicating one of the presence or the absence of the one or more critical logs.

9. The system (100) as claimed in claim 8, wherein the pre-defined criteria include one or more of: a first condition for checking a count of a log or a count of a log sequence in the identified log pattern with respect to a first pre-defined threshold; a second condition for checking the log sequence in the identified log pattern in a pre-defined time-period with respect to a second pre-defined threshold; and a third condition for checking a count of the first plurality of logs in the identified log pattern with respect to a second plurality of logs included in a second log data file fetched in a preceding communication session, wherein the first log data file and the second log data file are associated with upgradation of the target server.

10. The system (100) as claimed in claim 8, wherein the message includes a recommendation indicating at least one of proceeding with the upgradation,stopping the upgradation, initiating a rollback for the upgradation, or performing an analysis for deciding for proceeding with the upgradation.

11. The system (100) as claimed in claim 8, wherein the processing module (212, 308) is configured to display the message on a User Interface (UI) (312) of a user device (308).

12. The system (100) as claimed in claim 8, wherein, based on the determination of one of the presence or the absence of the one or more critical logs in the first log data file, the log management module (222, 310) is configured to: analyze an impact of the presence or absence of the one or more critical logs in the identified log pattern of the first plurality of logs on the upgradation; and determine, based on the impact of the presence or absence of the one or more critical logs, a confidence score indicating a likelihood of a success or failure of the upgradation of the server environment.

13. The system (100) as claimed in claim 8, wherein the first plurality of logs includes information associated with the upgradation of the target server.

14. The system (100) as claimed in claim 8, wherein the processing module (212, 308) is configured to: initiate an Application Programming Interface (API) call request for establishing the communication session between the client and the target server, wherein the API call request for establishing the communication session is initiated based on one of a reception of a user request at the processing module (212, 308) for monitoring logs corresponding to upgradation of the server environment, or a triggering of a scheduler at a pre-defined time interval.

15. A computer program product for monitoring logs for upgradation of a server environment, the computer program product comprising computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processor performs operations comprising:establishing a communication session between a client and a target server of a plurality of target servers in a server environment; fetching, upon establishment of the communication session, a first log data file comprising a first plurality of logs from the target server; identifying a log pattern of the first plurality of logs by analyzing the first log data file using a rule -based model; determining, based on a pre-defined criteria, one of a presence or an absence of one or more critical logs from the identified log pattern of the first plurality of logs in the first log data file; and generating, based on a result of the determination, a message indicating one of the presence or the absence of the one or more critical logs.

Images