I think I may have found part of the problem. When you use the "table" command it actually creates a HTML tag. When you use the xyseries it creates an id tag but its done with tags instead. So in my example the SplunkJS code is looking for a "" tag but its getting stripped off by the xyseries command. So now the question is : Is there a SplunkJS set of commands that will do the same thing and the TableView command set. I'm looking for something like DivView commands set. This way I can tell the systemm to locate the tage with the "id="blahblah" option. My only other option is to see if the xyseries command can build its tables using the "real" " HTML tag instead of a bunch of "" tags. Also if anyone can tell me if raw javascript will work. Something like this: function GetElementInsideContainer(containerID, childID) { var elm = document.getElementById(childID); var parent = elm ? elm.parentNode : {}; return (parent.id && parent.id === containerID) ? elm : {}; } var e = GetElementInsideContainer("div1", "edit2"); alert(e.html); ... View more

Thanks for the response... But I think I can configure the clients (Universal forwarders) to send data to both Server-1 and Server-2 at the same time. I dont want to get in a situation where a link or server goes down for a while and when the systems return Server-1 has mas more records than Server-2. That's why I want a true replicating daemon that can log into both systems and verify that the pools of data on Server-1 and Server-2 are identical ... (100% of the time). All this with only two servers... 🙂 If this product cant support that than maybe I'll try to install all of the pieces of the clustering setup on the two servers i currently have. Server-1 --- /opt/splunk-master -- using ports 9000-9010 --- /opt/splunk-search-head -- using ports 9020-9030 --- /opt/splunk-peer -- using ports 9040-9050 Server-2 --- /opt/splunk-search-head -- using ports 9020-9030 --- /opt/splunk-peer -- using ports 9040-9050 Maybe something like this would work.. ... View more