search

kieker-monitoring / kieker

Kieker's main repository
Apache License 2.0
70 stars 41 forks source link

[KIEKER-857] Monitoring Writer to ExplorViz Analysis Component #890

Open rju opened 3 weeks ago

rju commented 3 weeks ago

JIRA Issue: KIEKER-857 Monitoring Writer to ExplorViz Analysis Component Original Reporter: Florian Fittkau

Today, we implemented an ExplorVizExportWriter into the Monitoring component. Through the Writer, the monitoring component of Kieker can directly write the monitoring logs to a running ExplorViz analysis component.
Therefore, enabling fast analysis results of about several millions of analyzed monitoring records per second and visualizing the conducted monitoring by the ExplorViz web application.

Current limitations: Only Before-Records and AfterEvent-Records are supported (due to manual conversion).

To test the Writer: Download latest .war file of ExplorViz and put it in a local Jetty or Tomcat. Then run a monitored program and you should see a visualization of the traces.

Checklist:

rju commented 2 weeks ago

author André van Hoorn -- Mon, 17 Mar 2014 10:00:24 +0100

Do we have an automatic writer test according to other writer tests?

rju commented 2 weeks ago

author anonymous -- Mon, 17 Mar 2014 10:13:33 +0100

No, this writer writes to the external ExplorViz component, which is not part of Kieker.

rju commented 2 weeks ago

author André van Hoorn -- Mon, 17 Mar 2014 10:44:35 +0100

Replying to [anonymous|comment:4]:
> No, this writer writes to the external ExplorViz component, which is not part of Kieker.

Ah, OK. The JMS writer writes to a JMS queue, which is also not part of Kieker

Seriously: Is there any way to add at least a basic regression unit test making sure that the writer's functionality will not break accidentally when changing code in Kieker? Looking at the writer code, I feel that at least a test for the serialization would make sense.

rju commented 2 weeks ago

author André van Hoorn -- Mon, 17 Mar 2014 14:28:07 +0100

see KIEKER-1282 Done