[JBoss JIRA] (RTGOV-203) Add context 'type' combo to call trace gadget
by Gary Brown (JIRA)
Gary Brown created RTGOV-203:
--------------------------------
Summary: Add context 'type' combo to call trace gadget
Key: RTGOV-203
URL: https://issues.jboss.org/browse/RTGOV-203
Project: RTGov (Run Time Governance)
Issue Type: Enhancement
Reporter: Gary Brown
Assignee: Gary Brown
Priority: Minor
Fix For: 1.0.0.Final
Add context 'type' combo box to the call trace gadget. Currently it only supplies the value, and therefore the type defaults to 'conversation', which will generally be the one required. However conversation ids may not always be provided, so users may wish to search for a trace based on a process id etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (RTGOV-202) Call trace REST service support retrieving call trace based on Context
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-202?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-202.
------------------------------
Resolution: Done
> Call trace REST service support retrieving call trace based on Context
> ----------------------------------------------------------------------
>
> Key: RTGOV-202
> URL: https://issues.jboss.org/browse/RTGOV-202
> Project: RTGov (Run Time Governance)
> Issue Type: Enhancement
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.Final
>
>
> Currently using a GET with query parameter for an identifier, which assumes clients will only be interested in call traces based on conversation ids.
> However some traces may not have conversation ids, so will need to use other types of context - so need the REST service and gadget to allow other types of context to be specified.
> Could use a POST with the Context supplied, but probably more appropriate to still use a GET, but specify the context type and value as separate query parameters?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (RTGOV-202) Call trace REST service support retrieving call trace based on Context
by Gary Brown (JIRA)
Gary Brown created RTGOV-202:
--------------------------------
Summary: Call trace REST service support retrieving call trace based on Context
Key: RTGOV-202
URL: https://issues.jboss.org/browse/RTGOV-202
Project: RTGov (Run Time Governance)
Issue Type: Enhancement
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.Final
Currently using a GET with query parameter for an identifier, which assumes clients will only be interested in call traces based on conversation ids.
However some traces may not have conversation ids, so will need to use other types of context - so need the REST service and gadget to allow other types of context to be specified.
Could use a POST with the Context supplied, but probably more appropriate to still use a GET, but specify the context type and value as separate query parameters?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months