[JBoss JIRA] (RTGOV-519) Intercept activity from Vertx app interactions and report as activity events
by Gary Brown (JIRA)
Gary Brown created RTGOV-519:
--------------------------------
Summary: Intercept activity from Vertx app interactions and report as activity events
Key: RTGOV-519
URL: https://issues.jboss.org/browse/RTGOV-519
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.1.0.Final
Vertx has a simple core that is not going to be extended to support any form of intercept mechanism.
The current advice from the vertx team is to create a module that essentially acts as proxy to the real module being used. The problem with this approach is that it does not have any information about the client or service, which are required by rtgov.
Therefore the suggested approach will be to wrap the event bus api with an implementation that can be configured with information about the verticle in which it is being used. Then it can use that information when a message is being sent or received, to create activity events (e.g. request sent/received, response sent/received).
The other issue to consider is how to build ActivityUnits out of the various ActivityType events that may be associated with a business transaction instance. In some environments, the thread can be used to track and accumulate multiple activity events to the same unit. However this approach wouldn't work in Vertx.
One approach to be considered:
The activity events should be reported to an intermediate module responsible for accumulating events into a unit. If a response is expected, then when recording the request it should record the fact, so that the module building the activity unit can determine when invocation scopes have been completed, and therefore the activity unit submitted. (May be more complex than this, but possibly a starting point). The response handler would need to cache a 'replyTo' id that would enable it to submit response events to the same activity unit. This may be controlled on the client side (i.e. event bus proxy), as it may know when it has finished doing its work.
Worst case is that each verticle 'instance' would record its activity in a single activity unit - i.e. request received, and sent messages and received responses, before returning its reply.
Need to investigate whether vertx exposes any form of message ids between verticles - and if not, whether this is something they would consider adding. This would enable correlation of activity across verticles.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RTGOV-518) Deploy RTGov server as a Vertx module
by Gary Brown (JIRA)
Gary Brown created RTGOV-518:
--------------------------------
Summary: Deploy RTGov server as a Vertx module
Key: RTGOV-518
URL: https://issues.jboss.org/browse/RTGOV-518
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.1.0.Final
Enable the RTGov server to be used as a Vertx module.
Although the complete server could be encapsulated in a module, it may be better to separate out the main server components (e.g. ActivityStore, Event Process Network Manager, Active Collection Manager) as separate modules with appropriate inter-communication.
Also some of the existing REST services should be made available as modules.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (SRAMP-474) CLI: Add a log-to-file option
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-474?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-474:
-----------------------------------
Once merged, include in the docs
> CLI: Add a log-to-file option
> -----------------------------
>
> Key: SRAMP-474
> URL: https://issues.jboss.org/browse/SRAMP-474
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Shell
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> Currently CLI batch files must be created by hand. This isn't too much of a hardship, but it might be convenient for the interactive console to help out with this by allowing the user to log all commands executed to a file. This could be the basis for a CLI batch file that the user could include in some sort of integration scenario.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (SRAMP-474) CLI: Add a log-to-file option
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-474?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-474:
-----------------------------------
[~eric.wittmann], up for reviewing https://github.com/Governance/s-ramp/pull/449 and make sure it's what you had in mind? If the log file is enabled, AbstractShellCommandReader simply writes each line. That's the 2nd commit. The first was me encapsulating all sramp.sh arguments in a class, including #properties and the new log-to-file option.
> CLI: Add a log-to-file option
> -----------------------------
>
> Key: SRAMP-474
> URL: https://issues.jboss.org/browse/SRAMP-474
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Shell
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> Currently CLI batch files must be created by hand. This isn't too much of a hardship, but it might be convenient for the interactive console to help out with this by allowing the user to log all commands executed to a file. This could be the basis for a CLI batch file that the user could include in some sort of integration scenario.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (SRAMP-474) CLI: Add a log-to-file option
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-474?page=com.atlassian.jira.plugin.... ]
Work on SRAMP-474 started by Brett Meyer.
> CLI: Add a log-to-file option
> -----------------------------
>
> Key: SRAMP-474
> URL: https://issues.jboss.org/browse/SRAMP-474
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Shell
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> Currently CLI batch files must be created by hand. This isn't too much of a hardship, but it might be convenient for the interactive console to help out with this by allowing the user to log all commands executed to a file. This could be the basis for a CLI batch file that the user could include in some sort of integration scenario.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months