I am writing a connector for clintSVR and Splunk. Splunk is a software for machine data and it is very easy to generate dashboard reports using its google like search function. I can create the following dashboard reports by using the SplitSkillReport and SplitSkillStatus data. If you already have Splunk installed, you can create your own dashboard reports whatever you want. I will release the next version of clintSVR and write more posts on this feature.
Archive for the ‘Daily Usage’ Category
I want to implement a front-end application for AvayaCDR. I have no plan so far because I know it is difficult to write such front-end application especially when CDR data is in customised format. I found someone using Splunk for Cisco CDR and implemented a Splunk app, this triggered me to use Splunk for my AvayaCDR program.
I plan to implement a Splunk connector. Such connector parses the incoming CDR streams, assigns each field with it’s name (when CDR fields are assigned with meaningful names, Searching and Reporting in Splunk becomes strait-forward.) and formats a new CDR record that can be recognised by Splunk. The AvayaCDR then forwards the new CDR data records to Splunk (using TCP), Splunk then performs indexing and allows users to perform Searching and Reporting. Dashboard reports for telecom charging can be created by Splunk when the new CDR data records contains charging information. Sample screen dumps attached.
I want to publish CMS data to Internet and enable users to use iPhone or Android devices to access the real time reports. To get real time data from clintSVR is easy, but the difficult part to me is to write an iPhone or Android application. I implemented an XMPP library before and I just thinking if I can use the library to write a bot module which allows XMPP clients to get the CMS data. I will write this module and include it in the next release of clintSVR. I did a prototype like this