Log file entries for GUI operations
Overview
The following is an example of a server log entry for the deletion of an IP interface using the client GUI:
<server.core.IFGBase.printDebug> IFG[generic]:([generic.GenericObject].deleteInstance() : BEGIN <server.core.NullDeployer.issueDatabaseLog> From RIWorker [8](1301414107317),DatabaseLogRuleInvokationCapsule User Id: securityManager:user-admin Request Id: AreqGenericObjectDeleteInstance-CLIENT-admin-NFM-P@6-181 Target Class: rtr.DirectInterfaceCtp Target Object Id: network:198.51.100.59:router-1:ip-interface-2:TP Operation: ObjectDeletion Result: true <server.core.IFGBase.printDebug> IFG[generic]:([generic.GenericObject].deleteInstance() : END ::: successfuly executed : true
The log entry contains the following information:
-
the class and method that corresponds to the GUI action, which in this example is generic.GenericObject.deleteInstance. You can use the identified class and method to create an OSS application that performs the same task.
-
the specific instance of the action that was on the managed router IP interface with the unique ID network:198.51.100.59:router-1:ip-interface-2:TP. The unique ID identifies that the router has an IP address of 198.51.100.59 and a name of router-1.
-
acknowledgement of successful completion of the configuration action
Note: In some cases, a GUI action may use custom methods that are not directly applicable for use by an OSS. For example, when configuring network objects using the GUI, the server log output could log the mpls.LspPath.configure method. In this case an OSS should use the generic method generic.GenericObject.configureInstance. See Configuration methods for more information about using generic methods for configuring network objects.
In some cases, no specific instance is returned, for example, when you perform a find action.