Agnostic data collection platform

A method, comprising:

• initiating a data collector;
• posting, by the data collector, a registration message to a broker;
• receiving, by the data collector, an acknowledgement message posted by an agent with the broker;
• obtaining, by the data collector, managed data from a data provider of a managed device;
• formatting, by the data collector, the managed data as a formatted managed data;
• and
• posting, by the data collector, a data message comprising the formatted managed data to the broker for delivery by the broker to the agent.

A system, comprising:

• a server comprising a processor and a non-transitory computer-readable storage medium having executable instructions;
• a managed device comprising a device processor and a device non-transitory computer-readable storage medium having device executable instructions;
• the device executable instructions when executed by the device processor from the device non-transitory computer-readable storage medium cause the device processor to perform first operations comprising:
• posting a registration message to a broker, wherein the registration message comprising a first identifier for the device executable instructions and a second identifier for the managed device;
• receiving an acknowledgement message posted by the executable instructions with the broker;
• obtaining managed data from a data provider of the managed device;
• formatting the managed data as formatted managed data;
• posting a data message to the broker, wherein the data message comprising the formatted managed data;
• and
• receiving a second acknowledgement message posted by the executable instructions with the broker;
• the executable instructions when executed by the processor from the non-transitory computer-readable storage medium cause the processor to perform operations comprising:
• receiving the registration message posted with the broker by the second executable instructions;
• posting the acknowledgment message to the broker;
• obtaining the first identifier and the second identifier from the registration message;
• linking the first identifier with the second identifier;
• receiving the data message posted with the broker by the second executable instructions;
• posting the second acknowledgement message to the broker;
• obtaining the second identifier that is associated with the managed device and linked to the first identifier that is associated with the second executable instructions based on the data message;
• obtaining the managed data from the data message;
• and
• sending the managed data with a header comprising the second identifier over a one-way and encrypted connection to an endpoint device.