TeleFlow Monitor

TeleFlow Monitor

From TeleFlow

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
-
TeleFlow Monitor is a small GUI executable that enables a system administrator to view the current operations of a TeleFlow system, and provide some administration. This application is currently in the process of becoming web-based using PHP.
+
TeleFlow Monitor is a small GUI executable that enables a system administrator to view the current operations of a TeleFlow system, and provide some administration. You can also query for Monitor data via a simple HTTP request.
==XML Update==
==XML Update==
-
Plan: The TeleFlow Monitor XML Request interface and will be added to the TeleFlow Server as an update. It will be accessible by any service using a simple request like:
+
Plan: The TeleFlow Server XML Monitor interface accepts an HTTP request and returns an XML document containing the current status of every application instance running under TeleFlow Server. Here is an example of a request:
-
:<tt>http://localhost:5038?Request=TFMonitor</tt>
+
:<tt>http://127.0.0.1:5051?Request=SEND_UPDATE</tt>
An example XML document would look list this:
An example XML document would look list this:
-
<xml>
 
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
-
<TFMonitor>
+
<TFMonitor logFolder="C:\TeleFlowRelay\log\" startTime="20130426162427">
-
<TFPort Id="1" Port="1" Restarts="0/-1" AppFile="app01.tap"
+
<TFApp msgNo="22199092" appID="1001" appName="SIPmgr" appFile="SIP_Service_Manager.TAP" Port="-1" currentTAM="Service_Manager_Main" stepNumber="2" stepName="FINISH" status="Failed" license="Unlicensed" restarts="0" restartMax="0" callerID="" calledID="">
-
Flowchart="Start.tam" Step="123" StepName="Wait">Data Ready</TFPort>
+
<SysData/>
-
<TFPort Id="2" Port="2" Restarts="1/-1" AppFile="app01.tap"
+
</TFApp>
-
Flowchart="GetID.tam" Step="321" StepName="Play File">Name: Sally</TFPort>
+
<TFApp msgNo="57605060" appID="1002" appName="Ans01" appFile="PlaceCallTest.TAP" Port="24" currentTAM="PlaceCallTest" stepNumber="2" stepName="FINISH" status="Finished" license="Licensed" restarts="0" restartMax="0" callerID="" calledID="">
-
<TFPort Id="3" Port="3" Restarts="0/-1" AppFile="app01.tap"
+
<SysData>FAILURE</SysData>
-
Flowchart="Start.tam" Step="123" StepName="Wait">Data Ready</TFPort>
+
</TFApp>
-
...
+
<TFApp msgNo="58653648" appID="1003" appName="Ans02" appFile="ANSWERTESTSIP.tap" Port="25" currentTAM="AnswerTestSIP" stepNumber="116" stepName="Wait for Call" status="Normal" license="Licensed" restarts="0" restartMax="0" callerID="" calledID="">
-
<TFPort Id="99" Port="99" Restarts="5/5" AppFile="app01.tap"
+
<SysData> </SysData>
-
Flowchart="Done.tam" Step="123" StepName="Wait">STOPPED</TFPort>
+
</TFApp>
 +
<TFApp msgNo="59702224" appID="1004" appName="Ans03" appFile="ANSWERTESTSIP.tap" Port="26" currentTAM="AnswerTestSIP" stepNumber="116" stepName="Wait for Call" status="Normal" license="Licensed" restarts="0" restartMax="0" callerID="" calledID="">
 +
<SysData> </SysData>
 +
</TFApp>
</TFMonitor>
</TFMonitor>
-
</xml>
 
- 
- 
-
==Questions for Developers==
 
-
Would it be possible just to copy paste the current binary TF info, and re-express it as text, while promoting the TCP/IP access to HTTP? That way, functionality is added, and nothing is lost for older installations of TeleFlow.
 
- 
-
If development of the XML could initially '''just''' include the restarts in order to start testing with, it would be straightforward for developers to build integrated web environments for monitoring. This would provide the most basic ability to have a web page access the status of TeleFlow, and allow a manager to take action. TF Sentinel was created to do this last year, but the binary system for passing info back and forward could not be properly byte aligned in order to achieve this.
 
- 
-
This feature opens the product to web developers, and a tight integration of TeleFlow and Web applications will be more readily available to new adopters of TeleFlow.
 

Revision as of 23:44, 26 April 2013

TeleFlow Monitor is a small GUI executable that enables a system administrator to view the current operations of a TeleFlow system, and provide some administration. You can also query for Monitor data via a simple HTTP request.

XML Update

Plan: The TeleFlow Server XML Monitor interface accepts an HTTP request and returns an XML document containing the current status of every application instance running under TeleFlow Server. Here is an example of a request:

http://127.0.0.1:5051?Request=SEND_UPDATE

An example XML document would look list this:

<?xml version="1.0" encoding="UTF-8"?> <TFMonitor logFolder="C:\TeleFlowRelay\log\" startTime="20130426162427"> <TFApp msgNo="22199092" appID="1001" appName="SIPmgr" appFile="SIP_Service_Manager.TAP" Port="-1" currentTAM="Service_Manager_Main" stepNumber="2" stepName="FINISH" status="Failed" license="Unlicensed" restarts="0" restartMax="0" callerID="" calledID=""> <SysData/> </TFApp> <TFApp msgNo="57605060" appID="1002" appName="Ans01" appFile="PlaceCallTest.TAP" Port="24" currentTAM="PlaceCallTest" stepNumber="2" stepName="FINISH" status="Finished" license="Licensed" restarts="0" restartMax="0" callerID="" calledID=""> <SysData>FAILURE</SysData> </TFApp> <TFApp msgNo="58653648" appID="1003" appName="Ans02" appFile="ANSWERTESTSIP.tap" Port="25" currentTAM="AnswerTestSIP" stepNumber="116" stepName="Wait for Call" status="Normal" license="Licensed" restarts="0" restartMax="0" callerID="" calledID=""> <SysData> </SysData> </TFApp> <TFApp msgNo="59702224" appID="1004" appName="Ans03" appFile="ANSWERTESTSIP.tap" Port="26" currentTAM="AnswerTestSIP" stepNumber="116" stepName="Wait for Call" status="Normal" license="Licensed" restarts="0" restartMax="0" callerID="" calledID=""> <SysData> </SysData> </TFApp> </TFMonitor>

Retrieved from "http://teleflow.org/wiki/index.php5?title=TeleFlow_Monitor"