Projects tagged ‘monitoring’ and ‘tracing’


Jump to tag:

Projects tagged ‘monitoring’ and ‘tracing’

Filtered by Project Tags monitoring tracing

Refine results Project Tags metrics (1) debugging (1) timing (1) university (1) db (1) oracle (1) sql (1) it (1) macquarie (1) oci (1) instrumentation (1) trace (1)

[4 total ]

1 Users

Mission Statement The Lemona project's objectives are to provide: a complete proposal for a secured and reliable open architecture; and its full-featured implementation. The goals of the Lemona ... [More] software are: to monitor and to trace system activity at the kernel and user level; to report and to store archives of this activity on remote and/or local repositories; to provide understandable information for the recovery and forensics analysis of compromised systems. Master of IT at Macquarie University Lemona was started by Laurent Malvert and Kenfe-Mickael Laventure, students at the Macquarie University in 2008, as part of the completion requirements for their Master of Information Technology (Software Engineering) program. [Less]
Created about 1 year ago.

0 Users

Tools for instrumentating .NET projects using multi-cast attributes. Uses the PostSharp (http://www.postsharp.org/) AOP system to inject tracing and logging code into your project.
Created 10 months ago.

0 Users

Tool for monitoring of OCI client applications [f.e.: TOAD/TOra, or any OCI-based fat client] interaction with Oracle Database. Monitors SQL statements and values passed/fetched. Consist of GUI [C#] ... [More] and events handler [C++]. Similar to Quest SQLMonitor. [Less]
Created 11 months ago.

0 Users

Hatch: A Stack-based Performance LoggerCheck out the GettingStarted page! Release Version 0.7 Release0Dot7 Snapshot Version 1.0-SNAPSHOT IntroductionLogging is still the simplest and most ... [More] popular way of tracing a program's execution. Even with many advanced tools at our disposal, we still lean toward simple I Am Here. style debugging. Hatch is a simple stack-based performance logger. Just by adding begin/end style calls into your code, you can trace how much time it is taking to perform a specific request. Example Output [135ms] request share purchase [5ms] validate purchase request [40ms] check account balances [39ms] synchronous balance request [30ms] read uncommitted share availability check [55ms] queue request [30ms] persist message to queue [15ms] write audit logFeaturesThreads can request tracing on a per-request basis, reducing clutter Enable or disable globally at runtime without restarting. Only log traces that meet specific criteria ("Only log requests that took over 1000ms during business hours.") Log to System.out or log4j (or extend the basic logger to log wherever you want, see AdvancedHatchUsage). More InformationPoke around the source to find out more. See the release notes history. [Less]
Created 12 months ago.