CLIAMS:1. An infrastructure support optimization system (102) comprising:
a processor (202);
an authorization module (212) coupled to the processor (202) to:
verify a user, based on authorization rules, to provide access to the user to one or more infrastructure elements (108) from among a plurality of infrastructure elements (108);
an integration module (214) coupled to the processor (202) to:
obtain ticket attribute data from a ticketing system, based on the verification, wherein the ticket attribute data comprises a plurality of attributes associated with a ticket to be resolved by the user, and wherein the ticket is indicative of an issue associated with an infrastructure element (108) from among the one or more infrastructure elements(108);
a support action assistance module (216) coupled to the processor (202) to:
receive a support action, to be performed on the infrastructure element (108) to resolve the ticket, wherein the support action comprises at least one of an operation including one or more steps to resolve the ticket, and a standard support service; and
a log generation module (220) coupled to the processor (202) to:
append the support action to an operation log (300), wherein each entry in the operation log (300) includes information pertaining to support action performed by users on the plurality of infrastructure elements (108), and corresponding ticket attribute data.

2. The infrastructure support optimization system (102) as claimed in claim 1, wherein the ticket attribute data comprises a ticket id (304), and at least one of a ticket category (306), a ticket type (308), and a ticket summary (310).

3. The infrastructure support optimization system (102) as claimed in claim 1, wherein the operation log (300) further comprises least one of a user id, a session id, and infrastructure element attributes.

4. The infrastructure support optimization system (102) as claimed in claim 1, wherein the integration module (214) integrates the infrastructure support optimization system (102) with at least one of the ticketing system, configuration management database (CMDB), and a static knowledgebase.

5. The infrastructure support optimization system (102) as claimed in claim 1, wherein the support action assistance module (216) further:
obtains a search query from the user, to resolve the ticket, the search query comprising at least one of an attribute of the ticket, user id, session id, and an attribute of an infrastructure element (108); and
analyzes the operation log (300), based on the search query, to identify one or more previously appended operations in the operation log (300) to resolve the ticket, wherein the operation to be executed on the infrastructure element (108) is based on the one or more previously appended operations.

6. The infrastructure support optimization system (102) as claimed in claim 1 further comprising a validation module (218) coupled to the processor (202), to:
determine whether one or more validation rules are defined for the received operation, based on rule data (228), wherein the rule data (228) comprises a plurality of validation rules corresponding to a plurality of operations, and wherein each of the plurality of validation rules is indicative of checks to be performed before a received operation is executed;
ascertain, when it is determined that the one or more validation rules are defined for the operation, whether the operation is to be executed, based on the validation rules; and
execute the operation on the infrastructure element (108) based on the ascertaining.

7. The infrastructure support optimization system (102) as claimed in claim 6, wherein the validation module (218) is to further:
decline execution of the operation, when it is ascertained that the one or more validation rules defined for the received operation are not met; and
provide a notification to the user, wherein the notification is indicative of the declining.

8. The infrastructure support optimization system (102) as claimed in claim 1 further comprising a service assistance module (222) coupled to the processor (202), to:
analyze the operation log (300), based on recurrence criteria, to identify at least one recurring operation; and
provide the at least one recurring operation as a standard service in a service catalog, based on the indentifying.

9. A computer implemented method for providing support for a plurality of infrastructure elements (108), the method comprising:
verifying a user, based on authorization rules, to provide access to the user to one or more infrastructure elements (108) from among the plurality of infrastructure elements (108);
obtaining ticket attribute data from a ticketing system, based on the verifying, wherein the ticket attribute data comprises a plurality of attributes associated with a ticket to be resolved by the user, and wherein the ticket is indicative of an issue associated with an infrastructure element (108) from among the one or more infrastructure elements(108);
receiving a support action to be performed on the infrastructure element (108) to resolve the ticket, wherein the support action comprises at least one of an operation including one or more steps to resolve the ticket, and a standard service; and
appending the support action to an operation log (300), based on the receiving, wherein each entry in the operation log (300) includes information pertaining to support action performed by users on the plurality of infrastructure elements (108), and corresponding ticket attribute data.

10. The method as claimed in claim 9, wherein the ticket attribute data comprises a ticket id (304), and at least one of a ticket category (306), a ticket type (308), and a ticket summary (310).

11. The method as claimed in claim 9, wherein the operation log (300) further comprises at least one of a user id, a session id, and infrastructure element attributes.

12. The method as claimed in claim 9, wherein the receiving further comprises:
obtaining a search query from the user, to resolve the ticket, the search query comprising at least one of an attribute of the ticket, user id, session id, and an attribute of an infrastructure element (108); and
analyzing the operation log (300), based on the search query, to identify one or more previously appended operations in the operation log (300) to resolve the ticket, wherein the operation to be executed on the infrastructure element (108) is based on the one or more previously appended operations.

13. The method as claimed in claim 9, wherein the authorization rules comprises rules for primary level authorization, and secondary level authorization, wherein the primary level authorization is performed based on user id, and wherein the secondary level authorization is performed based on role of the user to provide role based access control to the user.

14. The method as claimed in claim 9 further comprising:
determining whether one or more validation rules are defined for the received operation, based on rule data (228), wherein the rule data (228) comprises a plurality of validation rules corresponding to a plurality of operations, and wherein each of the plurality of validation rules is indicative of checks to be performed before the received operation is executed;
ascertaining, when it is determined that the one or more validation rules are defined for the operation, whether the validation rules corresponding to the received operation are met; and
executing the operation on the infrastructure element (108) based on the ascertaining.

15. The method as claimed in claim 14, wherein the method further comprises:
declining execution of the operation, when it is ascertained that the one or more validation rules defined for the received operation are not met; and
providing a notification to the user, wherein the notification is indicative of the declining.

16. The method as claimed in claim 14, wherein the validation rules are associated with at least one of a user, role of the user, and the infrastructure element (108) accessible by the user.

17. The method as claimed in claim 9 further comprising:
analyzing the operation log (300), based on recurrence criteria, to identify at least one recurring operation; and
providing the at least one recurring operation as a standard service in a service catalog, based on the identifying.

18. A non-transitory computer-readable medium having embodied thereon a computer program for executing a method comprising:
verifying a user, based on authorization rules, to provide access to the user to one or more infrastructure element (108) from among the plurality of infrastructure elements (108);
obtaining ticket attribute data from a ticketing system, based on the verifying, wherein the ticket attribute data comprises a plurality of attributes associated with a ticket to be resolved by the user, and wherein the ticket is indicative of an issue associated with an infrastructure element (108) from among the one or more infrastructure elements(108);
receiving a support action to be performed on the infrastructure element (108) to resolve the ticket, wherein the support action comprising at least one of an operation including one or more steps to resolve the ticket, and a standard support service; and
appending the support action to an operation log (300), based on the receiving, wherein each entry in the operation log (300) includes information pertaining to support action performed by the user on the plurality of infrastructure elements (108), and corresponding ticket attribute data. ,TagSPECI:As Attached