January 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (BAM-115) Add context and properties fields to Situation

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-115?page=com.atlassian.jira.plugin.sy... ] Gary Brown resolved BAM-115. ---------------------------- Resolution: Done > Add context and properties fields to Situation > ---------------------------------------------- > > Key: BAM-115 > URL: https://issues.jboss.org/browse/BAM-115 > Project: Business Activity Monitoring > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > Need a way for a Situation to be associated back to a particular business transaction - allowing the user to then open the call trace for the particular business transaction to investigate further. > This could eventually be automated, but achieved manually in the short term. > The examples that create Situation object would also need to be updated. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-46) S-RAMP properties: honor 'propertyName' feature of ad-hoc atom query

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-46?page=com.atlassian.jira.plugin.s... ] Eric Wittmann resolved SRAMP-46. -------------------------------- Resolution: Done Fully resolved. > S-RAMP properties: honor 'propertyName' feature of ad-hoc atom query > -------------------------------------------------------------------- > > Key: SRAMP-46 > URL: https://issues.jboss.org/browse/SRAMP-46 > Project: S-RAMP > Issue Type: Sub-task > Components: Atom Binding, Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: Milestone 3 (Workflow and Relationships) > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Section 3.2 of the s-ramp atom binding indicates that optional 'propertyName' parameters can be included when issueing a query. When included, the indicated artifact properties should be returned as part of the atom feed. This allows clients to avoid a full fetch of all artifacts in the result set. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-46) S-RAMP properties: honor 'propertyName' feature of ad-hoc atom query

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-46?page=com.atlassian.jira.plugin.s... ] Eric Wittmann updated SRAMP-46: ------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/36, https://github.com/Governance/s-ramp/pull/142 (was: https://github.com/Governance/s-ramp/pull/36) > S-RAMP properties: honor 'propertyName' feature of ad-hoc atom query > -------------------------------------------------------------------- > > Key: SRAMP-46 > URL: https://issues.jboss.org/browse/SRAMP-46 > Project: S-RAMP > Issue Type: Sub-task > Components: Atom Binding, Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: Milestone 3 (Workflow and Relationships) > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Section 3.2 of the s-ramp atom binding indicates that optional 'propertyName' parameters can be included when issueing a query. When included, the indicated artifact properties should be returned as part of the atom feed. This allows clients to avoid a full fetch of all artifacts in the result set. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-46) S-RAMP properties: honor 'propertyName' feature of ad-hoc atom query

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-46?page=com.atlassian.jira.plugin.s... ] Eric Wittmann closed SRAMP-46. ------------------------------ > S-RAMP properties: honor 'propertyName' feature of ad-hoc atom query > -------------------------------------------------------------------- > > Key: SRAMP-46 > URL: https://issues.jboss.org/browse/SRAMP-46 > Project: S-RAMP > Issue Type: Sub-task > Components: Atom Binding, Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: Milestone 3 (Workflow and Relationships) > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Section 3.2 of the s-ramp atom binding indicates that optional 'propertyName' parameters can be included when issueing a query. When included, the indicated artifact properties should be returned as part of the atom feed. This allows clients to avoid a full fetch of all artifacts in the result set. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-137) Add getArtifactMetaData(ArtifactSummary) to the client api

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-137: ----------------------------------- Summary: Add getArtifactMetaData(ArtifactSummary) to the client api Key: SRAMP-137 URL: https://issues.jboss.org/browse/SRAMP-137 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: Milestone 4 Makes it easier for users to access the full meta-data for a given result set item. Consider alternatives such as: summary.fetchArtifact() -> BaseArtifactType -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-34) Situations gadget should present context and properties information to user

by Gary Brown (JIRA)

Gary Brown created GADGETS-34: --------------------------------- Summary: Situations gadget should present context and properties information to user Key: GADGETS-34 URL: https://issues.jboss.org/browse/GADGETS-34 Project: Gadget Server and Gadgets Issue Type: Enhancement Reporter: Gary Brown Assignee: Jeff Yu Fix For: 1.0.0.M4 The Situation gadget currently displays the descriptive fields associated with a situation, and in the future may provide a more automated means of navigating (or focusing) other gadgets on a business transaction(s) associated with the situation. However in the short term it would be good if a user could access information about the context (i.e. correlation identifier(s)) and properties associated with the activities that caused the situation. These details will be added to the Situation object (BAM-115). They shouldn't necessarily be displayed in the table, due to limited space, but possibly could be visible in a tooltip or a popup menu action associated with the situation entry. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-115) Add context and properties fields to Situation

by Gary Brown (JIRA)

Gary Brown created BAM-115: ------------------------------ Summary: Add context and properties fields to Situation Key: BAM-115 URL: https://issues.jboss.org/browse/BAM-115 Project: Business Activity Monitoring Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M4 Need a way for a Situation to be associated back to a particular business transaction - allowing the user to then open the call trace for the particular business transaction to investigate further. This could eventually be automated, but achieved manually in the short term. The examples that create Situation object would also need to be updated. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-90) intermittent error when restarting the SwitchYard with BAM distro and sla sample installed.

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-90?page=com.atlassian.jira.plugin.sys... ] Gary Brown updated BAM-90: -------------------------- Fix Version/s: 1.0.0.M4 > intermittent error when restarting the SwitchYard with BAM distro and sla sample installed. > ------------------------------------------------------------------------------------------- > > Key: BAM-90 > URL: https://issues.jboss.org/browse/BAM-90 > Project: Business Activity Monitoring > Issue Type: Bug > Reporter: Jeff Yu > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > Attachments: server.log > > > Note, sometimes I got this problem, it is not always.. :-( > reproduce steps: > 1) installed the BAM distro in SwitchYard 0.6 beta2 (by running the mvn install in distro) > 2) started the SwitchYard. (with --server-config=standalone-full.xml) > 3) deploy the sla sample into SwitchYard > 4) Stop the SwitchYard > 5) restart the SwitchYard again. > 6) log in the gadget server with 'admin'(default account) > I saw two sort of problems, one is the server couldn't be restarted successfully,, specifically it got hanged on the sla-monitor.war, and then am told it was deployed failed, and then rollback everything. > 2) sometimes I got 'out of heap' error when I log in the gadget server. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-46) S-RAMP properties: honor 'propertyName' feature of ad-hoc atom query

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-46?page=com.atlassian.jira.plugin.s... ] Work on SRAMP-46 started by Eric Wittmann. > S-RAMP properties: honor 'propertyName' feature of ad-hoc atom query > -------------------------------------------------------------------- > > Key: SRAMP-46 > URL: https://issues.jboss.org/browse/SRAMP-46 > Project: S-RAMP > Issue Type: Sub-task > Components: Atom Binding, Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: Milestone 3 (Workflow and Relationships) > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Section 3.2 of the s-ramp atom binding indicates that optional 'propertyName' parameters can be included when issueing a query. When included, the indicated artifact properties should be returned as part of the atom feed. This allows clients to avoid a full fetch of all artifacts in the result set. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-46) S-RAMP properties: honor 'propertyName' feature of ad-hoc atom query

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-46?page=com.atlassian.jira.plugin.s... ] Eric Wittmann updated SRAMP-46: ------------------------------- Fix Version/s: Milestone 3 (Workflow and Relationships) (was: Future (Unscheduled)) > S-RAMP properties: honor 'propertyName' feature of ad-hoc atom query > -------------------------------------------------------------------- > > Key: SRAMP-46 > URL: https://issues.jboss.org/browse/SRAMP-46 > Project: S-RAMP > Issue Type: Sub-task > Components: Atom Binding, Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: Milestone 3 (Workflow and Relationships) > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Section 3.2 of the s-ramp atom binding indicates that optional 'propertyName' parameters can be included when issueing a query. When included, the indicated artifact properties should be returned as part of the atom feed. This allows clients to avoid a full fetch of all artifacts in the result set. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues January 2013