Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
monitoring
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ExplorViz
explorviz-github-archive
monitoring
Graph
52f69a4fab46e5875027f1652873bc78e02e4e88
Select Git revision
Branches
2
android-monitoring
master
default
protected
Tags
1
v1.0.0
3 results
You can move around the graph by using the arrow keys.
Begin with the selected commit
Created with Raphaël 2.2.0
25
Oct
18
Jun
7
May
4
28
Apr
17
9
29
Mar
24
23
22
20
15
14
13
12
5
28
Feb
27
25
24
22
13
12
8
7
6
5
4
21
Oct
14
13
9
20
Sep
11
14
Aug
22
Jul
21
18
17
16
15
16
Jun
15
13
26
May
25
27
Apr
22
19
18
15
14
11
10
9
10
Mar
7
26
Feb
25
10
9
28
Jan
19
17
16
17
Dec
14
12
11
10
9
8
5
4
3
2
30
Nov
26
19
18
15
12
10
6
30
Oct
22
14
7
4
3
22
Sep
21
20
19
13
10
8
29
Aug
27
16
15
14
12
11
9
8
6
2
31
Jul
30
Add LICENSE
master
master
Create README.md
1.0
v1.0.0
v1.0.0
classpath...
eclipse import bug fix
jdbc monitoring
...
build update
migration
disabled sys monitoring by default
fixed server not instrumented
using sigar for cpu util
WiP
WiP
WiP
WiP Optimized String sending
WiP
...
WiP
WiP
WiP
minor
WiP
record batching now superfluous
disruptor in again
Merge branch 'master' of build.se.informatik.uni-kiel.de:explorviz/monitored-application
minor
fixed monitoring
failed records now smaller
reduced waiting CPU impact
monitoring now working again after switch to jctools
moved from disruptor to jctools
done some TODOs
minor
removed activemq from dist
fixed warnings
delete unused
also monitor the programming language as meta info
print stack trace instead of just toString when exception occurs
continous_monitoring_enabled switch
Loading