[JBoss JIRA] (BAM-132) Activity collector event filtering
by Gary Brown (JIRA)
Gary Brown created BAM-132:
------------------------------
Summary: Activity collector event filtering
Key: BAM-132
URL: https://issues.jboss.org/browse/BAM-132
Project: Business Activity Monitoring
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M5
Collector activity event filtering mechanism to enable administrator to control what level of events are reported.
Some level of filtering may be performed based on which interceptors are installed. However may need more fine level of control.
--
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
13 years, 1 month
[JBoss JIRA] (BAM-130) Capture principal info from switchyard environment
by Gary Brown (JIRA)
Gary Brown created BAM-130:
------------------------------
Summary: Capture principal info from switchyard environment
Key: BAM-130
URL: https://issues.jboss.org/browse/BAM-130
Project: Business Activity Monitoring
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M4
Work out how best to obtain principal information from switchyard. May need to be accessed through first exchange, but activity collector is reporting activity, not origin info.
--
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
13 years, 1 month
[JBoss JIRA] (BAM-128) Synchronous activity event processing
by Gary Brown (JIRA)
Gary Brown created BAM-128:
------------------------------
Summary: Synchronous activity event processing
Key: BAM-128
URL: https://issues.jboss.org/browse/BAM-128
Project: Business Activity Monitoring
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M5
The current policy enforcement example has two parts, the event evaluation using mvel to determine whether a customer should be suspended, and then an exchange handler configured in switchyard app to enforce the decision.
This is an asynchronous approach to enforcement that potential enables a customer to exceed their restrictions (albeit briefly) before the enforcement kicks in.
In situations where enforcement must apply immediately a policy has been broken, then we need a synchronous event evaluation to occur at the activity collector and potentially immediately affect the message exchange.
Need to consider:
- whether this mechanism should use a restricted form of the EPN as a way to make configuration consistent - although it would be dealing with derived ActivityType rather than an ActivityUnit at the top level, and interaction between nodes would also be synchronous, which may lead to ordering issues or configurations that would not be supported.
- what actions are required based on the decision made in a policy - for the customer suspended case it is likely to be just throwing an exception, but are there other actions?
Deployment of these sync policies should be equivalent to other components in the architecture.
Benefit of having a specific mechanism may be that it doesn't cause confusion with the full blown configuration, and also the fact that it is supposed to be returning a decision, rather than just propagating derived results. Not using the EPN may have benefits of not including its mechanics in the lightweight server configuration.
However we need to consider how it would interact with 'services' (e.g. cache) - possibly this could be a similar/same mechanism without having to use the whole EPN infrastructure.
--
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
13 years, 1 month
[JBoss JIRA] (BAM-127) Consolidated service dependency view across DTGov and RTGov
by Gary Brown (JIRA)
Gary Brown created BAM-127:
------------------------------
Summary: Consolidated service dependency view across DTGov and RTGov
Key: BAM-127
URL: https://issues.jboss.org/browse/BAM-127
Project: Business Activity Monitoring
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M5
Where DTGov is available, it should be used to build the underlying dependency graph and then overlay the runtime information over the appropriate nodes and relationships.
Currently this graph is only built from runtime information, so if there are no direct links between two services (i.e. some intermediate components exist that are not monitored by RTGov), then they would be seen as separate graphs, without the user having an understanding of the indirect relationship.
--
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
13 years, 1 month