A method for monitoring a binary process, comprising: monitoring a binary process on a first machine; detecting communication with the binary process by a second application on a second machine, the second application not a binary process; characterized by: determining (410, 440) whether the communication is an incoming process request or an outgoing process request; if it is determined that the communication is an incoming process request: calling a library method to invoke a reflector module; installing the reflector module at an address associated with the detected communication; reading, by the reflector module, one or more parameters contained within the detected communication, the one or more parameters including business transaction information; determining a business transaction name for the distributed business transaction based at least in part from the method parameters; and storing subsequent data captured for performance of that incoming process request associated with the business transaction name; if it is determined that the communication is an outgoing process request: calling a library method configured to invoke a decorator; writing, by the decorator module, outgoing parameters and a business transaction name to the outgoing process request to enable the outgoing process request to be correlated with other process request; and correlating the binary process and the second application as part of a distributed business transaction implemented across the first machine and the second machine formed by correlated process requests. monitoring a binary process on a first machine; detecting communication with the binary process by a second application on a second machine, the second application not a binary process; characterized by: determining (410, 440) whether the communication is an incoming process request or an outgoing process request; if it is determined that the communication is an incoming process request: calling a library method to invoke a reflector module; installing the reflector module at an address associated with the detected communication; reading, by the reflector module, one or more parameters contained within the detected communication, the one or more parameters including business transaction information; determining a business transaction name for the distributed business transaction based at least in part from the method parameters; and storing subsequent data captured for performance of that incoming process request associated with the business transaction name; if it is determined that the communication is an outgoing process request: calling a library method configured to invoke a decorator; writing, by the decorator module, outgoing parameters and a business transaction name to the outgoing process request to enable the outgoing process request to be correlated with other process request; and correlating the binary process and the second application as part of a distributed business transaction implemented across the first machine and the second machine formed by correlated process requests. determining (410, 440) whether the communication is an incoming process request or an outgoing process request; if it is determined that the communication is an incoming process request: calling a library method to invoke a reflector module; installing the reflector module at an address associated with the detected communication; reading, by the reflector module, one or more parameters contained within the detected communication, the one or more parameters including business transaction information; determining a business transaction name for the distributed business transaction based at least in part from the method parameters; and storing subsequent data captured for performance of that incoming process request associated with the business transaction name; calling a library method to invoke a reflector module; installing the reflector module at an address associated with the detected communication; reading, by the reflector module, one or more parameters contained within the detected communication, the one or more parameters including business transaction information; determining a business transaction name for the distributed business transaction based at least in part from the method parameters; and storing subsequent data captured for performance of that incoming process request associated with the business transaction name; if it is determined that the communication is an outgoing process request: calling a library method configured to invoke a decorator; writing, by the decorator module, outgoing parameters and a business transaction name to the outgoing process request to enable the outgoing process request to be correlated with other process request; and correlating the binary process and the second application as part of a distributed business transaction implemented across the first machine and the second machine formed by correlated process requests. calling a library method configured to invoke a decorator; writing, by the decorator module, outgoing parameters and a business transaction name to the outgoing process request to enable the outgoing process request to be correlated with other process request; and correlating the binary process and the second application as part of a distributed business transaction implemented across the first machine and the second machine formed by correlated process requests.