Bug 1048140 - Support logging XMLRPC method's namespace
Summary: Support logging XMLRPC method's namespace
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kobo
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Mach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-03 09:37 UTC by cqi
Modified: 2016-07-19 10:50 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 10:50:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
git patch for supporting logging XMLRPC method's namespace (2.92 KB, patch)
2014-01-03 09:37 UTC, cqi
no flags Details | Diff

Description cqi 2014-01-03 09:37:25 UTC
Created attachment 844889 [details]
git patch for supporting logging XMLRPC method's namespace

XmlRpcLog.method only contains the method's name being call. However, it's not enough sometimes, especially to TCMS.

TCMS exposes XMLRPC methods to external systems and standalone applications, such as lots of automation testing scrips. That methods contains get, filter, update and several other methods with same name defined in each module, TestPlan, TestCase, TestRun, etc. During the past maintenance of TCMS, developers and sys admins usually want to see a which module where a method is being called. But, there's no information from the log.

This patch is solve this problem from the kobo side. Now, log_call decorator accepts an optional argument named namespace to allow developers to specify proper value according to their circumstances. For example,

@log_call(namespace='testplan')
def get(request, id):
    pass

As a result, XmlRpcLog.method will contain testplan.get

That's it. This small change will help TCMS developers to log more useful information of XMLRPC invocation. And also hope it could help other projects that need similar requirement.

Comment 1 Jaroslav Reznik 2015-03-03 15:21:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 2 Fedora End Of Life 2016-07-19 10:50:35 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.