Method and system for suppressing repetitive log entries

Abstract

The present disclosure relates to a method and a system for suppressing repetitive log entries The disclosure encompasses receiving, a one or more log entries; determining whether the one or more log entries is pre-stored in a log map, based at least on a method call; updating, upon determining that the one or more log entries are pre-stored in the log map, pre-stored log details associated with the one or more log entries; and adding, upon determining that the log entry is not pre-stored in the log map, the one or more log entries in the log map.

Description

METHOD AND SYSTEM FOR SUPPRESSING REPETITIVE LOG ENTRIESTECHNICAL FIELD

[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to suppressing repetitive log entries.BACKGROUND

[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.

[0003] Extensive Input / output operations due to massive log writing in files results in high CPU usage and slows down the application’s performance. Also, log analysis becomes difficult when any log line starts printing multiple times in the application log file.

[0004] Further, over a period of time, various solutions have been developed to optimize log updation and analysis. However, there are certain challenges with existing solutions. In the existing solutions, logs analysis becomes difficult when any log line starts printing multiple times in the application log file. Also, for extensive Input / output operations due to massive log writing in files results in high CPU usage and slows down the application’s performance.

[0005] Thus, there exists an imperative need in the art to suppress repetitive logs, which the present disclosure aims to address.SUMMARY

[0006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0007] An aspect of the present disclosure may relate to a method for suppressing repetitive log entries. The method comprises receiving, by a transceiver unit, a one or more log entries. The method further comprises determining, by a determining unit, whether the one or more log entries is pre-stored in a log map, based at least on a method call. The method further comprises updating, upon determining that the one or more log entries is pre-stored in the log map, updating, by an updating unit, pre-stored log details associated with the one or more log entries. And, the method further comprises adding, upon determining that the log entry is not pre-stored in the log map, adding, by an addition unit

[0304] , the one or more log entries in the log map.

[0008] In an exemplary aspect of the present disclosure, in the disclosed method, the log map comprises a mapping of the one or more log entries and their corresponding log details. It is to be noted that the corresponding log details comprise at least one of count, start time, and end time.

[0009] In an exemplary aspect of the present disclosure, the method further comprises periodically writing, by an analysis unit, data of the log map to a log fde in a mode. The method further comprises deleting, by the analysis unit, log mapping entries from a memory when a predetermined count threshold is reached.

[0010] In an exemplary aspect of the present disclosure, the method further comprises writing, by the analysis unit, data of the log map to the log fde with corresponding set of timestamps and counts.

[0011] In an exemplary aspect of the present disclosure, the method further comprises rendering, by a display unit, an interface on a user device to enable a user to write data of the log map to the log fde.

[0012] Another aspect of the present disclosure may relate to a system for suppressing repetitive log entries. The system comprises a transceiver unit configured to receive one or more log entries. The system further comprises a determining unit configured to determine whether the one or more log entries are pre-stored in a log map, based at least on a method call. The system further comprises an updating unit configured to, upon determining that the one or more log entries are pre-stored in the log map, update pre-stored log details associated with the one or more log entries. And the system further comprises an addition unit configured to, upondetermining that the one or more log entries is not pre-stored in the log map, add the one or more log entries in the log map.

[0013] Yet another aspect of the present disclosure may relate to a non-transitory computer-readable storage medium storing instructions for suppressing repetitive log entries, the instructions include executable code which, when executed by a one or more units of a system, causes: a transceiver unit to receive one or more log entries; a determining unit of the system to determine whether the one or more log entries are pre-stored in a log map, based at least on a method call; an updating unit, upon determining that the one or more log entries are pre-stored in the log map, to update pre-stored log details associated with the one or more log entries; and an addition unit, upon determining that the one or more log entries are not prestored in the log map, to add the one or more log entries in the log map.

[0014] Yet another aspect of the present disclosure may relate to a user equipment (UE) for suppressing repetitive log entries. The UE comprises a transceiver unit configured to transmit one or more log entries. The UE further comprises a determining unit configured to determine whether the one or more log entries are pre-stored in a log map, based at least on a method call. The UE further comprises an updating unit configured to, upon determining that the one or more log entries are pre-stored in the log map, update pre-stored log details associated with the one or more log entries. And the UE also comprises an addition unit configured to, upon determining that the one or more log entries are not pre-stored in the log map, add the one or more log entries in the log map.OBJECTS OF THE DISCLOSURE

[0015] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0016] It is an object of the present disclosure to provide a system and a method for suppressing repetitive logs.

[0017] It is another object of the present disclosure to provide a solution that saves CPU usage without any loss of data by suppressing repetitive logs.

[0018] It is yet another object of the present disclosure to provide a solution to avoid repetitive logging and cluttering of log fdes.

[0019] It is yet another object of the present disclosure to provide a solution to avoid scrolling multiple fdes for the same log.

[0020] It is yet another object of the present disclosure to provide an easier way of debugging.DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0022] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.

[0023] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.

[0024] Fig. 3 illustrates an exemplary block diagram of a system for suppressing repetitive log entries, in accordance with exemplary implementations of the present disclosure.

[0025] Fig. 4 illustrates a method flow diagram for suppressing repetitive log entries, in accordance with exemplary implementations of the present disclosure.

[0026] Fig. 5 illustrates another exemplary flow diagram for suppressing repetitive log entries, in accordance with exemplary implementations of the present disclosure.

[0027] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0028] 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, that embodiments of the present disclosure may be practised without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

[0029] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0030] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practised without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0031] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.

[0032] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “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” as an open transition word — without precluding any additional or other elements.

[0033] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.

[0034] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and / or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment / device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.

[0035] As used herein, “storage unit” or “memory unit” refers to a machine or computer- readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.

[0036] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0037] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general -purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0038] As used herein the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units / components within the system and / or connected with the system.

[0039] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of suppressing repetitive log entries.

[0040] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture

[0100] , in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture

[0100] includes a user equipment (UE)

[0102] , a radio access network (RAN)

[0104] , an access and mobility management function(AMF)

[0106] , a Session Management Function (SMF)

[0108] , a Service Communication Proxy (SCP)

[0110] , an Authentication Server Function (AUSF)

[0112] , a Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] , a Network Slice Selection Function (NSSF)

[0116] , a Network Exposure Function (NEF)

[0118] , a Network Repository Function (NRF)

[0120] , a Policy Control Function (PCF)

[0122] , a Unified Data Management (UDM)

[0124] , an application function (AF)

[0126] , a User Plane Function (UPF)

[0128] , and a data network (DN)

[0130] , wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.

[0041] The Radio Access Network (RAN)

[0104] is part of a mobile telecommunications system that connects user equipment (UE)

[0102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.

[0042] The Access and Mobility Management Function (AMF)

[0106] is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.

[0043] The Session Management Function (SMF)

[0108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.

[0044] The Service Communication Proxy (SCP)

[0110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.

[0045] The Authentication Server Function (AUSF)

[0112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.

[0046] The Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.

[0047] The Network Slice Selection Function (NSSF)

[0116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.

[0048] The Network Exposure Function (NEF)

[0118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.

[0049] The Network Repository Function (NRF)

[0120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.

[0050] The Policy Control Function (PCF)

[0122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.

[0051] The Unified Data Management (UDM)

[0124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.

[0052] The Application Function (AF)

[0126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.

[0053] The User Plane Function (UPF)

[0128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.

[0054] The Data Network (DN)

[0130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.

[0055] Fig. 2 illustrates an exemplary block diagram of a computing device

[1000] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device

[1000] may also implement a method for suppressing repetitive log entries utilising the system. In another implementation, the computing device

[1000] itself implements the method for suppressing repetitive log entries using one or more units configured within the computing device

[1000] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0056] The computing device

[1000] may include a bus

[1002] or other communication mechanism for communicating information, and a hardware processor

[1004] coupled with bus

[1002] for processing information. The hardware processor

[1004] may be, for example, a general-purpose microprocessor. The computing device

[1000] may also include a main memory

[1006] , such as a random access memory (RAM), or other dynamic storage device, coupled to the bus

[1002] for storing information and instructions to be executed by the processor

[1004] , The main memory

[1006] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[1004] , Such instructions, when stored in non-transitory storage media accessible to the processor

[1004] , render the computing device

[1000] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[1000] further includes a read-only memory (ROM)

[1008] or other static storage device coupled to the bus

[1002] for storing static information and instructions for the processor

[1004] ,

[0057] A storage device

[1010] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[1002] for storing information and instructions. The computing device

[1000] may be coupled via the bus

[1002] to a display

[1012] , such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device

[1014] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[1002] for communicating information and command selections to the processor

[1004] , Another type of user input device may be a cursor controller

[1016] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[1004] , and for controlling cursor movement on thedisplay

[1012] , This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

[0058] The computing device

[1000] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and / or program logic which in combination with the computing device

[1000] causes or programs the computing device

[1000] to be a special -purpose machine. According to one implementation, the techniques herein are performed by the computing device

[1000] in response to the processor

[1004] executing one or more sequences of one or more instructions contained in the main memory

[1006] , Such instructions may be read into the main memory

[1006] from another storage medium, such as the storage device

[1010] , Execution of the sequences of instructions contained in the main memory

[1006] causes the processor

[1004] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0059] The computing device

[1000] also may include a communication interface

[1018] coupled to the bus

[1002] , The communication interface

[1018] provides a two-way data communication coupling to a network link

[1020] that is connected to a local network

[1022] , For example, the communication interface

[1018] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface

[1018] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface

[1018] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0060] The computing device

[1000] can send messages and receive data, including program code, through the network(s), the network link

[1020] and the communication interface

[1018] , In the Internet example, a server

[1030] might transmit a requested code for an application program through the Internet

[1028] , the ISP

[1026] , the local network

[1022] and the communication interface

[1018] , The received code may be executed by the processor

[1004] as it is received, and / or stored in the storage device

[1010] , or other non-volatile storage for later execution.

[0061] Referring to Figure 3, an exemplary block diagram of a system

[0300] for suppressing repetitive log entries, is shown, in accordance with the exemplary implementations of the present disclosure. The system

[0300] comprises at least one transceiver unit

[0301] , at least one determining unit

[0302] , at least one updating unit

[0303] , at least one addition unit

[0304] , at least one analysis unit

[0305] , and at least one display unit

[0306] , Also, all of the components / units of the system

[0300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in Fig. 3 only a few units are shown, however, the system

[0300] may comprise multiple such units or the system

[0300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system

[0300] may be present in a user device [300u] (may also be referred herein as a UE) to implement the features of the present disclosure. The system

[0300] may be a part of the user device / or may be independent of but in communication with the user device. In another implementation, the system

[0300] may reside in a server or a network entity. In yet another implementation, the system

[0300] may reside partly in the server / network entity and partly in the user device.

[0062] The system

[0300] is configured for suppressing repetitive log entries, with the help of the interconnection between the components / units of the system

[0300] ,

[0063] The transceiver unit

[0301] is configured to receive one or more log entries. The transceiver unit

[0301] is associated with the determining unit

[0302] . It is to be noted that the one or more log entries may pertain to the logs generated due to massive input-output (I / O) operations during the application usage . The one or more log entries may include but not limited to storage disk I / O logs, network session logs, application logs, system logs, databases logs etc. The determining unit

[0302] is configured to determine whether the one or more log entries are pre-stored in a log map, based at least on a method call. It is to be noted that the log map comprises a mapping of the one or more log entries and their corresponding log details, wherein the corresponding log details comprise at least one of count, start time, and end time. Further, the method call here may include but not limited to a common method name getLogDetailsCount() that is responsible for checking in the log map if the log entries is already contained in the log map. Furthermore, the determining unit

[0302] may be associated with the updating unit

[0303] ,

[0064] The updating unit

[0303] is configured to, upon determining that the one or more log entries are pre-stored in the log map, update pre-stored log details associated with the pre-stored log entries. The updating unit

[0303] may be associated with the addition unit

[0304] , The prestored log details associated with the pre-stored log entries are updated, when the one or more log entries are added in the log map.

[0065] The addition unit

[0304] is configured to, upon determining that the one or more log entries are not pre-stored in the log map, add the one or more log entries in the log map.

[0066] The analysis unit

[0305] is configured to periodically write data of the log map in a log file in a mode. It is to be noted that the periodical writing of data of the log map to the log file is done to avoid log map memory from overflowing. The writing of data is periodical i.e., it can be based on configurable time interval. Further, the writing of the data of the log map is done in INFO mode. The analysis unit

[0305] is further configured to delete log mapping entries from a memory [300m] when a predetermined count threshold is reached. The analysis unit

[0305] is further configured to write data of the log map to the log file with corresponding set of timestamps and counts. The data pertains to information associated with the log map. The log map may be metadata that is data about data that maps corresponding log entries to their corresponding events. It is to be noted that the set of timestamps indicate the time when the data of the log map was written in the log file while the counts indicate a number of times the data of the log map was written in the log file.

[0067] The display unit

[0306] is configured to render an interface on a user device [300u] to enable a user to write data of the log map to the log file.

[0068] Referring to Figure 4, an exemplary method flow diagram

[0400] for suppressing repetitive log entries, in accordance with exemplary implementations of the present disclosure is shown. In an implementation, the method

[0400] is performed by the system

[0300] , Further, in an implementation, the system

[0300] may be present in a server device to implement the features of the present disclosure. Also, as shown in Figure 4, the method

[0400] starts at step

[0402] ,

[0069] At step

[0404] , the method

[0400] comprises receiving, by the transceiver unit

[0301] , the one or more log entries.

[0070] At step

[0406] , the method

[0400] comprises determining, by the determining unit

[0302] , whether the log entries are pre-stored in a log map, based at least on a method call. The method call here may include but not limited to a common method name getLogDetailsCount() that is responsible for checking in the log map if the log entries is already contained in the log map.

[0071] In an exemplary aspect of the present disclosure, in the disclosed method

[0400] , the log map comprises a mapping of the one or more log entries and their corresponding log details. It is to be noted that the corresponding log details comprise at least one of count, start time, and end time.

[0072] At step

[0408] , the method

[0400] comprises updating, upon determining that the one or more log entries are pre-stored in the log map, by the updating unit

[0303] , pre-stored log details associated with the pre-stored log entries.

[0073] At step

[0410] , the method

[0400] comprises adding, upon determining that the log entries are not pre-stored in the log map, by an addition unit

[0304] , the one or more log entries in the log map.

[0074] In an exemplary aspect of the present disclosure, the method

[0400] also comprises periodically writing, by an analysis unit

[0305] , data of the log map in a log fde in a mode. It is to be noted that the periodical writing of data of the log map to the log fde is done to avoid log map memory from overflowing. The writing of data is periodical i.e., it can be based on configurable time interval. Further, the writing of the data of the log map is done in INFO mode. The method

[0400] further comprises deleting, by the analysis unit

[0305] , log mapping entries from a memory [300m] when a predetermined count threshold is reached.

[0075] In an exemplary aspect of the present disclosure, the method

[0400] further comprises writing, by the analysis unit

[0305] , data of the log map in the log file with corresponding set of timestamps and counts. It is to be noted that the set of timestamps indicates the time when the data of the log map was written in the log file while the counts indicate a number of times the data of the log map was written in the log file.

[0076] In an exemplary aspect of the present disclosure, the method

[0400] further comprises rendering, by a display unit

[0306] , an interface on a user device [300u] to enable a user to write data of the log map to the log fde.

[0077] Thereafter, the method

[0400] terminates at step

[0412] ,

[0078] Referring to FIG. 5, an exemplary method flow diagram

[0500] for suppressing repetitive log entries, in accordance with exemplary implementations of the present disclosure is shown. In order to suppress repetitive logs, the system

[0300] (shown in Fig. 3) is configured to maintain the log map and the value as log details (count, start time and end time) that is used to record the count and time of one or more log entries. It is to be noted that any log is written to file only once and post that only count is incremented and time is updated in the log map. As shown in Fig 5 depicting an exemplary scenario of the present disclosure, each log that is generated by the system

[0300] will pass through a common method name getLogDetailsCount() (not shown in Figure). The getLogDetailsCount() method checks in the log map if the same log entry is already saved in the map or not. There are possible scenarios in the same:1. If the same log entry is already contained in the log map, then the common method updates the log details and does not write the log in the file else the method adds the log in the map.2. If the same log entry is not there in the log map, the system

[0300] , via its hourly scheduler will run at configurable time intervals.

[0079] Thus, to avoid log map memory from the overflowing in long run, the system

[0300] , via the hourly scheduler runs at configurable time intervals. When said configurable time interval run, the analysis unit

[0305] (as shown in Fig. 3) will write the data of the log map in a mode (preferably an INFO mode) and clear the log map entries from a memory [300m] (as shown in Fig. 3) when the map entries reached a predetermined count threshold (say 10000 being the number of map entries).

[0080] Further, to check the log details at any particular time, the system

[0300] runs the common method getLogDetailsCount() using any CLI or GUI command trigger to flush the data of the log map to a log file.

[0081] It is pertinent to note that the system

[0300] is capable of implementing the features that are obvious to a person skilled in the art in light of the disclosure as disclosed above and the implementation of the system is not limited to the above disclosure.

[0082] The present disclosure further discloses a non-transitory computer-readable storage medium storing instructions for suppressing repetitive log entries, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit

[0301] to receive one or more log entries; a determining unit

[0302] of the system

[0300] to determine whether the one or more log entries are pre-stored in a log map, based at least on a method call; an updating unit

[0303] , upon determining that the one or more log entries are prestored in the log map, to update pre-stored log details associated with the one or more log entries; and an addition unit

[0304] , upon determining that the one or more log entries are not pre-stored in the log map, to add the one or more log entries in the log map.

[0083] The present disclosure further discloses a user equipment (UE) for suppressing repetitive log entries. The UE comprises the transceiver unit

[0301] configured to transmit one or more log entries. The UE further comprises the determining unit

[0302] configured to determine whether the one or more log entries are pre-stored in a log map, based at least on a method call. The UE further comprises the updating unit

[0303] configured to, upon determining that the one or more log entries are pre-stored in the log map, update pre-stored log details associated with the one or more log entries. And the UE also comprises the addition unit

[0304] configured to, upon determining that the one or more log entries are not pre-stored in the log map, add the one or more log entries in the log map.

[0084] As is evident from the above, the present disclosure provides a technically advanced solution for suppressing repetitive log entries. The present solution has the following advantages:Log files are short and concise which makes debugging easier and faster.More CPU cycles are available to other modules of the application.Unforeseen events in the network where log files might be flooded resulting in application’s performance lag or even the process becoming unresponsive will be avoided with this feature.Log files can be maintained for a longer duration as log files will not roll over frequently.

[0085] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components / units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

[0086] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

Claims

We Claim:

1. A method [400] for suppressing repetitive log entries, the method [400] comprising: receiving, by a transceiver unit [301], one or more log entries; determining, by a determining unit [302], whether the one or more log entries are prestored in a log map, based at least on a method call;- updating, upon determining that the one or more log entries are pre-stored in the log map, by an updating unit [303], pre-stored log details associated with the pre-stored log entries; and adding, upon determining that the one or more log entries are not pre-stored in the log map, by an addition unit [304], the one or more log entries in the log map.

2. The method [400] as claimed in claim 1, wherein the log map comprises a mapping of the one or more log entries and their corresponding log details, wherein the corresponding log details comprise at least one of count, start time, and end time.

3. The method [400] as claimed in claim 1, further comprising:- periodically writing, by an analysis unit [305], data of the log map in a log fde in a mode; and deleting, by the analysis unit [305], log mapping entries from a memory [300m] when a predetermined count threshold is reached.

4. The method [400] as claimed in claim 3, further comprising writing, by the analysis unit [305], data of the log map in the log fde with corresponding set of timestamps and counts, wherein the set of timestamps indicating time when the data of the log map was written in the log fde, wherein the counts indicate number of times the data of the log map was written in the log fde.

5. The method [400] as claimed in claim 4, further comprising rendering, by a display unit [306], an interface on a user device [300u] to enable a user to write data of the log map to the log fde.

6. A system [300] for suppressing repetitive log entries, said system [300] comprising: a transceiver unit [301] configured to receive one or more log entries;a determining unit [302] connected at least to the transceiver unit [301 ], the determining unit [302] configured to determine whether the one or more log entries are pre-stored in a log map, based at least on a method call; an updating unit [303] connected at least to the determining unit [302], the updating unit [303] configured to, upon determining that the one or more log entries are prestored in the log map, update pre-stored log details associated with the pre-stored log entries; and an addition unit [304] connected at least to the updating unit [303], the addition unit [304] configured to, upon determining that the log entries are not pre-stored in the log map, add the one or more log entries in the log map.

7. The system [300] as claimed in claim 6, wherein the log map comprises a mapping of the one or more log entries and their corresponding log details, wherein the corresponding log details comprise at least one of count, start time, and end time.

8. The system [300] as claimed in claim 6, wherein an analysis unit [305] is configured to:- periodically write data of the log map to a log file in a mode; and delete log mapping entries from a memory [300m] when a predetermined count threshold is reached.

9. The system [300] as claimed in claim 8, wherein the analysis unit [305] is configured to write data of the log map in the log file with corresponding set of timestamps and counts, wherein the set of timestamps indicating time when the data of the log map was written in the log file, wherein the counts indicate number of times the data of the log map was written in the log file.

10. The system [300] as claimed in claim 9, wherein a display unit [306] is configured to render an interface on a user device [300u] to enable a user to write data of the log map to the log file.

11. A user equipment (UE) for suppressing repetitive log entries, said UE comprising: o a transceiver unit [301] configured to transmit one or more log entries;o a determining unit [302] connected at least to the transceiver unit [301], the determining unit [302] configured to determine whether the one or more log entries are pre-stored in a log map, based at least on a method call; o an updating unit [303] connected at least to the determining unit [302], the updating unit [303] configured to, upon determining that the one or more log entries are pre-stored in the log map, update pre-stored log details associated with the one or more log entries; and o an addition unit [304] connected at least to the updating unit [303], the addition unit [304] configured to, upon determining that the one or more log entries are not pre-stored in the log map, add the one or more log entries in the log map.

12. A non-transitory computer-readable storage medium storing instruction for suppressing repetitive log entries, the storage medium comprising executable code which, when executed by one or more units of a system, causes: a transceiver unit [301] to receive one or more log entries; a determining unit of the system [300] to determine whether the one or more log entries are pre-stored in a log map, based at least on a method call; an updating unit [303] connected at least to the transceiver unit [301], the updating unit [303] to update, upon determining that the one or more log entries are pre-stored in the log map, pre-stored log details associated with the one or more log entries; and an addition unit [304] connected at least to the updating unit [303], the addition unit [304], to add, upon determining that the one or more log entries are not pre-stored in the log map, the one or more log entries in the log map.

Images