Probe Action Modules

Probe Action Modules

This topic has not yet been rated Rate this topic

Updated: April 15, 2013

Applies To: System Center Operations Manager 2007

noteNote
This exercise has been updated to include a procedure for Visual Studio Authoring Extensions in the latest version of the Management Pack Authoring Guide on the TechNet Wiki.

Probe action modules resemble data source modules because they collect information and pass it into the data stream. A probe action module is also not intended to change the agent in any way. The difference is that a probe action requires some trigger to start it.

Probe action module

Conceptual view of probe action module

Probe action modules accept a single input from the data stream and produce a single output data stream. The input could be data from another module, or it could be a simple trigger for probe action modules that do not require input data.

Probe action modules are directly used in monitor types for On Demand Detection and can be used in Diagnostics and Recoveries. All those workflow types provide a trigger that is required to initiate the probe action. Probe action modules are most frequently used within composite data source modules. Many of the data source modules that are included in the management pack libraries actually contain probe action modules to perform their core functionality.

Common Probe Action Modules

The following table lists common probe action modules. This is not a complete list of all probe action modules that are available. However, they are the most common probe action modules that management pack authors will directly use in building custom workflows and modules.

 

Module Name Management Pack Function Input Data Type Output Data Type

Microsoft.Windows.PowerShellDiscoveryProbe

Microsoft.Windows.Library

Runs a Windows PowerShell discovery script.

System.BaseData

System.DiscoveryData

Microsoft.Windows.PowerShellPropertyBagProbe

Microsoft.Windows.Library

Runs a Windows PowerShell monitoring script. Requires input data.

System.BaseData

System.PropertyBagData

Microsoft.Windows.PowerShellPropertyBagTriggerOnlyProbe

Microsoft.Windows.Library

Runs a Windows PowerShell monitoring script. Does not require input data.

None

System.PropertyBagData

Microsoft.Windows.ScriptPropertyBagProbe

Microsoft.Windows.Library

Runs a monitoring script.

System.BaseData

System.PropertyBagData

Microsoft.Windows.WmiProbe

System.Library

Runs WMI query to retrieve data. Requires input data.

System.BaseData

System.PropertyBagData

Microsoft.Windows.WmiTriggerProbe

Microsoft.Windows.Library

Runs WMI query to retrieve data. Does not require input data.

None

System.PropertyBagData

System.CommandExecuterProbe

System.Library

Run a command line program.

System.BaseData

System.CommandOutput

System.PassThroughProbe

System.Library

Use to provide input to non-trigger probe action modules for on demand monitor type workflows.

None

System.BaseData

  • 1
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
SQLAlchemy 是一个 SQL 工具包和对象关系映射(ORM)库,用于 Python 编程语言。它提供了一个高级的 SQL 工具和对象关系映射工具,允许开发者以 Python 类和对象的形式操作数据库,而无需编写大量的 SQL 语句。SQLAlchemy 建立在 DBAPI 之上,支持多种数据库后端,如 SQLite, MySQL, PostgreSQL 等。 SQLAlchemy 的核心功能: 对象关系映射(ORM): SQLAlchemy 允许开发者使用 Python 类来表示数据库表,使用类的实例表示表中的行。 开发者可以定义类之间的关系(如一对多、多对多),SQLAlchemy 会自动处理这些关系在数据库中的映射。 通过 ORM,开发者可以像操作 Python 对象一样操作数据库,这大大简化了数据库操作的复杂性。 表达式语言: SQLAlchemy 提供了一个丰富的 SQL 表达式语言,允许开发者以 Python 表达式的方式编写复杂的 SQL 查询。 表达式语言提供了对 SQL 语句的灵活控制,同时保持了代码的可读性和可维护性。 数据库引擎和连接池: SQLAlchemy 支持多种数据库后端,并且为每种后端提供了对应的数据库引擎。 它还提供了连接池管理功能,以优化数据库连接的创建、使用和释放。 会话管理: SQLAlchemy 使用会话(Session)来管理对象的持久化状态。 会话提供了一个工作单元(unit of work)和身份映射(identity map)的概念,使得对象的状态管理和查询更加高效。 事件系统: SQLAlchemy 提供了一个事件系统,允许开发者在 ORM 的各个生命周期阶段插入自定义的钩子函数。 这使得开发者可以在对象加载、修改、删除等操作时执行额外的逻辑。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值