What?s Next For CEP Vendors?


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News What?s Next For CEP Vendors?
# 1  
Old 01-28-2008
What?s Next For CEP Vendors?

by Larry Barrett, InternetNews.com, January 25, 2008 IBM on Wednesday made its first significant foray into the emerging but relatively low-profile complex event processing (CEP) market with its acquisition of privately held AptSoft. CEP applications aggregate information from corporate databases and applications in real time and applies rules to discern patterns and events that otherwise would go [...]

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

EPTS4: The Future, from the Vendors

vincent 09-20-2008 07:20 AM EPTS4 day 2 started with a a keynote by Susan Urban of Texas Tech Uni on a Roadmap for Research Directions. Susan comes from the active database world and was talking about fun stuff like distributed event processing agents and so forth. Susan emphasized... (0 Replies)
Discussion started by: Linux Bot
0 Replies

2. UNIX for Advanced & Expert Users

How to avoid vendors having root access ?

Hi gurus: We have several production *nix boxes from vendors and the policy here has been to give them root access as and when they require ( upgrade, troubleshooting the application, etc). Sudo is implemented on the systems but vendors cannot upgrade the application cause it says that the root... (2 Replies)
Discussion started by: geomonap
2 Replies
Login or Register to Ask a Question
profile(7D)							      Devices							       profile(7D)

NAME
profile - DTrace profile interrupt provider DESCRIPTION
The profile driver is a DTrace dynamic tracing provider that adds time-based interrupt event sources that can be used as DTrace probes. Each profile event source is a time-based interrupt firing every fixed, specified time interval. You can use these probes to sample some aspect of system state every unit time and the samples can then be used to infer system behavior. If the sampling rate is high, or the sam- pling time is long, an accurate inference is possible. By using the DTrace facility to bind arbitrary actions to probes, you can use the profile provider to sample practically anything in the system. For example, you could sample the state of the current thread, the CPU state, or the current machine instruction each time a probe fires. The profile driver is not a public interface and you access the instrumentation offered by this provider through DTrace. Refer to the Solaris Dynamic Tracing Guide for a description of the public documented interfaces available for the DTrace facility and the probes offered by the profile provider. ATTRIBUTES
See attributes(5) for a description of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWdtrp | +-----------------------------+-----------------------------+ |Interface Stability |Private | +-----------------------------+-----------------------------+ SEE ALSO
dtrace(1M), attributes(5), dtrace(7D) Solaris Dynamic Tracing Guide SunOS 5.10 4 Sep 2003 profile(7D)