Custom data aggregation and integration processing

A method, comprising:

• deploying, by a processor, agents to terminals, each agent activated and executed on a corresponding terminal and each agent registered with a corresponding operating system (OS) of the corresponding terminal to receive event information, wherein the event information at least includes a periodic signal indicating normal operation of the corresponding terminal;
• receiving, by the processor, metrics collected by the agents and a data pump application, the metrics comprising heartbeat signals of the terminals, software component versions of the terminals, and whether a particular terminal is out-of-service, available for full service, available for card only transactions, available for cash only transactions, a given software component is unable to process a particular transaction, or whether the particular terminal is closed;
• aggregating, by the processor, the metrics based on specific events identified in terminal data using a schema that maps format for a plurality of data to data types;
• and
• providing, by the processor, aggregated metrics associated with the aggregating to a resource based on a certain value for a certain metric exceeding a threshold in the aggregated metrics, wherein the resource is identified from the schema associated with the metrics, wherein providing further includes translating the aggregated metrics into a target data format associated with the resource, wherein the threshold is defined in the schema.

A system, comprising:

• a server that comprises a processor;
• and
• the processor executes instructions that cause the processor to perform operations comprising:
• configuring agents to collect metrics from terminals using on a schema that defines data types and event types, wherein the metrics comprising usage events and error events for terminal data available on the terminals;
• wherein the metrics comprise a heartbeat signal for a corresponding terminal;
• wherein the usage events and error events comprise software component versions of the terminals, and whether a particular terminal is out-of-service, available for full service, available for card only transactions, available for cash only transactions, a given software component is unable to process a particular transaction, or whether the particular terminal is closed;
• deploying each agent to a corresponding terminal each agent activated and executed on the corresponding terminal and each agent registered with a corresponding operating system (OS) of the corresponding terminal to receive event information, wherein the event information at least includes a periodic signal indicating normal operation of the corresponding terminal;
• receiving the metrics from the agents for the terminals based on the corresponding terminal data available on the corresponding terminals, wherein the metrics are aggregated based on specific events identified in the terminal data using the schema that maps data formats to the data types, wherein receiving further includes selectively aggregating into aggregated metrics;
• and
• providing the aggregated metrics to at least one resource defined in the schema based on a specific value for a certain metric exceeding a threshold defined in the schema, wherein providing further includes translating the aggregated metrics into a target data format associated with the resource, wherein the threshold is defined in the schema.