SA_1 and SA_2 can already log to the same DB and you can see from what SA the logging is coming. So using XML for that seems a bit odd.
The idea of master/slave is something we're "working" on however with a different idea behind it. The idea is that a master will do a check and combine the result with the check result of one or more slaves and based on that you can have an alert. Something like if my website is down for ALL then send an alert, if it's only down for ONE then send alert. (ALL = master and all configured slaved - ONE = master + at least one slave) Dirk. Don't forget to vote for Servers Alive in the annual Sunbelt Target Awards http://www.sunbelt-software.com/targetawards/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Tuesday, April 06, 2004 2:39 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] XML output Here's a bizarre possibility: XML was intended (among other things) to replace the confusing world of EDI standards, by providing a common method for data interchange. ie: sending the SA data to another piece of software for importation. What if it was possible for SA Prime to hit SA Double Prime's internal XML server, import the data from the last round of checks, then spew forth the combined data to a single unified interchange db and status db? Scenario: I have my primary SA running in our DC with 145+ checks. It writes output to the interchange db, the status db, and runs a custom Access macro to update a running times db for uptime calculations. I have my secondary SA running in a remote office checking only the connection to the DC and if SA is running at the DC. I COULD have the secondary DC create it's own seperate interchange db and status db, or I could try to point both at the same db, BUT it would be really cool if the primary SA could get the seconday's data from it, then just write both data sets at the same time to the dbs. Thus creating a Master/Slave scenario. What do you think? Michael Shook Technical Analyst Saddle Creek Corporation 723 Joe Tamplin Industrial Blvd Macon GA 31217 478 742 8740 ext. 105 (work) 478 256 9318 (mobile) 478 742 7917 (fax) [EMAIL PROTECTED] http://www.saddlecrk.com >>> [EMAIL PROTECTED] 04/06/04 03:15AM >>> But why as standard from the app, if it's possible using the HTML template? We could provide a sample XML template for the HTML output... Dirk. Don't forget to vote for Servers Alive in the annual Sunbelt Target Awards http://www.sunbelt-software.com/targetawards/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brett Hanson Sent: Tuesday, April 06, 2004 12:28 AM To: [EMAIL PROTECTED] Subject: Re: [SA-list] XML output I already use XML output (fudged of course), but would like to see XML output as standard from the application. Here is the template I use: <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="template.xsl"?> <Check_Information LastCheck="<sa_currentlongdate> <sa_currentlongtime>" Version="<sa_version>" Cycles="<sa_cycles>" CycleStart="<sa_cyclestart>" CycleStop="<sa_cyclestop>"> <sa_report sort=status,prettyname> <sa_groupheader> <Group GroupName="<sa_group_name>" GroupUpEntries="<sa_group_up_entries>" GroupDownEntries="<sa_group_down_entries>" GroupMaintenanceEntries="<sa_group_maintenance_entries>"> </sa_groupheader> <Check> <HostName><sa_hostname></HostName> <PrettyName><sa_prettyname></PrettyName> <Status src="images/<sa_status>.gif"><sa_status></Status> <ChangeDate><sa_statuschangedate></ChangeDate> <ChangeTime><sa_statuschangetime></ChangeTime> <Description><sa_checkdescription></Description> <CheckResponse><sa_checkresponse></CheckResponse> <Threshold><SAIF SA_CHECK IS PING><sa_threshold></SAIF><SAIF SA_CHECK NOT PING>N/A</SAIF></Threshold> <HostID><sa_hostid></HostID> <UID><sa_uid></UID> <RoundTrip><sa_roundtrip></RoundTrip> <AvgRoundTrip><sa_stats_avgrtrip></AvgRoundTrip> <MaxRoundTrip><sa_stats_maxrtrip></MaxRoundTrip> <MinRoundTrip><sa_stats_minrtrip></MinRoundTrip> <UpCycles><sa_stats_upcycles></UpCycles> <UpTime><sa_stats_uptime></UpTime> <DownCycles><sa_stats_downcycles></DownCycles> <DownPercent><sa_stats_downtime></DownPercent> <MaintenanceCycles><sa_stats_maintenancecycles></MaintenanceCycles> <MaintenancePercent><sa_stats_maintenancetime></MaintenancePercent> <TotalCycles><sa_stats_totalcycles></TotalCycles> <NonDownTime><sa_stats_nondowntime></NonDownTime> <OnStatusTime><sa_onstatustime></OnStatusTime> </Check> <sa_groupfooter> </Group> </sa_groupfooter> </sa_report> </Check_Information> Regards, Brett Hanson Agrium --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
