To be honest I don't think this is a convenient way of getting internal information. I implemented a different approach - a HTTP-JSON interface to the erlrtpproxy internals. It has much better functionality and flexibility.
See bef032953f205af6fb563da3d956b63c055ef9c1 and 88e7dba037a23184713a99345d45ac6fc3bf756c.
To be honest I don't think this is a convenient way of getting internal information. I implemented a different approach - a HTTP-JSON interface to the erlrtpproxy internals. It has much better functionality and flexibility.
See bef032953f205af6fb563da3d956b63c055ef9c1 and 88e7dba037a23184713a99345d45ac6fc3bf756c.