Hello,

Problem Statement

Currently, customers often need to retrieve information about hosts related to an event to correctly specify arguments for a run_job_template action.

A common use case: An environment has different Instance Groups (IGs) that are restricted to specific zones. A monitoring tool might send an event about a host but be unaware of these zone restrictions, so the event payload lacks this critical information.

The only workarounds today are cumbersome:

1. Use an initial run_job_template action solely to look up the data, save it as an artifact, and then pass that artifact to a second run_job_template action.

1. Chain the actions within a workflow.

Both methods add complexity and latency.

Proposed Solution

A valuable enhancement would be to add a new capability directly to rulebooks that allows them to query AAP inventories.

This feature would enable a rulebook to:

1. Gather information from the inventory (e.g., retrieve host variables or group variables for a host concerned by an event).

1. Use this retrieved information directly within the rulebook's actions, such as to dynamically populate arguments for the run_job_template action.

This would simplify rulebook logic, reduce complexity, and make the integration between event data and AAP inventory data much more seamless.