有两个主要工具，用途不一，有了它们您就可以访问数据库监控信息：快照监控器和事件监控器。
There are two primary tools, each serving a different purpose, with which you can access database monitor information: the snapshot monitor and event monitors.
本文通过实例演示了如何使用锁事件监控器来收集所有种类的并发性问题：死锁、锁超时及锁等待。
It showed, by example, how you can use the lock event monitor to collect information about any kind of concurrency issue: deadlocks, lock-timeouts, and lock-waits.
快照监控器允许您捕获特定时间内数据库活动的状态，而事件监控器只在特定数据库事件发生时记录数据。
The snapshot monitor enables you to capture a picture of the state of the database activity at a specific moment in time, while event monitors log data only as specified database events occur.
在使用首次创建的事件监控器之前，您必须首先禁用数据库然后再激活它，或手动运行事件监控器，如清单15所示。
Before you can use the event monitors after you first create them, you either have to deactivate and activate the database or manually start the event monitors, as shown in Listing 15.
为了格式化锁事件监控器收集的死锁事件数据，并将其写到普通文本文件中，再次调用db 2evmonfmt工具。
To format the data about the deadlock event that the lock event monitor collects and write it to a plain text file, call the db2evmonfmt utility again.
默认情况下，事件监控器创建之后带有AUTOSTART选项，这表示在数据库下一次被激活时将自动运行事件监控器。
By default, the event monitors are created with the AUTOSTART option, which means that the event monitors are automatically started the next time the database is activated.
它将读取从事件监控器表执行的sql语句，然后对每个语句运行Explain实用程序以生成对应的访问计划。
It reads the SQL statements executed from the event monitor tables and runs the Explain utility for each statement to generate the corresponding access plan.
本文已经显示了一个过程，您可以使用该过程自动生成表函数，其以关系格式报告以XML文档形式捕获的事件监控器元素。
This article has shown a procedure that you can use to automatically generate table functions that report event monitor elements captured as an XML document in a relational format.
PerformanceWarehouse保存的历史监控数据由较长时间的(长期历史)DB 2快照数据、DB2事件监控数据和配置数据组成。
Performance Warehouse saves historical monitoring data consisting of DB2 snapshot data, DB2 event monitor data, and configuration data over a long period of time (long-term history).
在IBMDB 2 9.7中，活动和统计事件监控器都具有DETAILS_XML监控器元素，该元素存储包含大量活动和系统指标的XML文档。
In IBM DB2 9.7, both the activity and statistics event monitors have a DETAILS_XML monitor element that stores an XML document which contains a wealth of activity and system metrics.
MDMServer环境中事件监控器的一个常见用途是死锁事件监控，用于了解和解决 MDM Server 数据库中偶尔发生的过度死锁（excessive deadlocks）。
One common usage of event monitor in the MDM Server environment is deadlock event monitoring to understand and resolve excessive deadlocks that sometimes happen in an MDM Server database.
但是，您可以创建并维护一个全面的系统来监控应用程序的整个生态系统，从而显著降低这些事件的严重性和持续时间。
But you can significantly reduce the severity and duration of these events by creating and maintaining a comprehensive system that monitors your application's entire ecosystem.
对于DB2，您可以使用事件和快照监控功能。
For DB2, there are both event and snapshot monitoring capabilities.
IT开发人员创建和部署监控企业中的各种事件源所需的“适配器”组件并生成所需的业务事件。
The it developer creates and deploys the "adapter" components needed to monitor the various event sources in the enterprise and generate the business events needed.
当使用SNMP通知发出警告时，通过轮询来监控运行时间可确保所有的通知发生故障不会影响这些事件。
While you can use SNMP notification for alerting, monitoring uptime via polling ensures that any notification delivery failure will not obscure these events.
审计功能可以监控不同类型的数据库事件，您可以指定只记录成功的事件还是只记录失败的事件，或者两种事件都记录。
The audit facility can monitor different types of database events and you can specify whether only successful or failed events, or both, should be logged.
他们还会从这个简单的API中受益，可以立即收到事件通知，不需要定期轮询，可以监控自己或第三方的事件。
They'll also benefit from its simple API, immediate notification of events without the need for constant polling, and the extensibility to monitor their own or third-party events.
通过监控Notes文档的单个或多个创建、打开、更新或删除事件，VirtualField活动在外部系统数据中触发适当的结果。
By monitoring single or multiple create, open, update, or delete events to the Notes documents, Virtual Field activities trigger the appropriate result in the external system data.
Grails还支持对自动重新加载事件的拦截，这可用来监控资源的改变，当发生变化时会重新加载资源。
Grails also supports intercepting Auto reload Events that can be used to monitor resources for any data changes and then reload the changes when they occur.
在本文中，我们将介绍如何利用由CEI提供的EventAccess和EventDistribution服务来接收这些事件并创建业务流程监控应用程序。
In this article, we show how to receive these events using event Access and event Distribution services as provided by cei and to create a business process monitoring application.
当您已经创建了订阅portlet用于监控的事件出现时，应该创建您的内容适配器实例，然后提交必要的信息。
When an event occurs for which you have created a subscription portlet to monitor, create an instance of your content adapter and submit the necessary information.
在WebSphereIntegrationDeveloperv 7中，您也可以轻松地告诉被监控的流程，打开监控模型所关注事件的发射功能。
In WebSphere Integration Developer V7, you can also easily tell the processes being monitored to turn on emission of the events that the monitor model CARES about.
SupportInfrastructure集群：这是开箱即用监控组件处理 BPMN流程生成的跟踪事件的位置。
Support Infrastructure cluster: This is where the out-of-the-box monitoring components process the tracking events produced by the BPMN processes.
这些在BusinessIntegrationModeler 中指定的KPI用于监控由工作流代码生成的事件的业务性能。
These KPIs specified in Business Integration Modeler are later used to monitor the business performance from the events generated from the workflow code.
与VirtualField活动相似，Virtual Document 活动监控Domino应用程序中的事件并在外部系统触发适当的更新。
Similar to the Virtual Field activity, the Virtual Document activity monitors for events in the Domino application and triggers the appropriate update in the external system.
这个Loan项目类型的所有文档属性都会被选中，以便在AddItem和Update Item事件中进行监控。
All document attributes of this Loan item type are selected to be monitored in the event monitoring for both the Add item and Update item events.
本文将简要介绍inotify，告诉我们如何监控文件夹，如何一有变化就报告相关消息事件，并介绍了一些相关工具，我们可以把它们添加到自己的工具箱中。
In this article we will walk through how to use Inotify to monitor directories and trigger alerts on changes and present tools you might want to add to your personal toolbox.
管理员配置Loan项目类型监控文档创建和修改分别对应的一个AddItem事件或Update Item事件。
The administrator configured the Loan item type to monitor either an Add item event or an Update item event for document creation and revision respectively.
对本机监控系统最好的使用方式就是将其用于临时监控，或详细调查从一个监控系统触发的性能事件。
The best use of the native monitoring tools is for casual monitoring or in doing a detailed investigation into a performance event triggered from a monitoring system.
计划中的另外一个想法是，在Rubyland项目中通过监控即将发生的事件，以及猜测用户当前的处理动作，来整合不同的事件源。
One idea that comes to mind is to integrate these event sources with tools that monitor what is going on and try to guess what the user is doing.
应用推荐