Dirk,
One feature that I think would be wonderful to factor in somewhere for a future
major release:
-Separation of the SA GUI from the SA Engine.
By that I mean: Make it possible to run SA as a service all the time, but
allow the GUI to be run, edit the config, view status of the engine, and exit
without upsetting the service.
Or maybe, get rid of the GUI all together and replace it with a web front-end
(as you mentioned below). That would be HUGE. In that case, I would hope
that the interface between the web browser and the actual engine would be XML
based and fairly well documented so it would be possible for external
applications to create/modify checks.
-Tom
Disclaimer: Comments expressed are my own and not necessarily those of my
employer.
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Bulinckx
Sent: Sunday, November 25, 2007 11:11 AM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Salive roadmap
Those are the main items that I see for the next MAJOR release:
* login-profiles for nt based checks
* real webserver for setup (and probably also for
editing/creating new entries) - with some security features like SSL (https)
and login security
* additional threaded alerts
* additional threaded checks
* mib browser for snmp checks
Some parts that I'm also looking at are:
* VMWare ESX diskspace check (*nix df) <- this
would be an easy one IF we had access (in SSH) to an ESX system (hint hint :-))
* SQL2005 check
* WMI check (for Exchange for example)
* Groups alerts
* splitting the checking/alerting/displaying
And depending on the "success" for the agent-check, the enhancement of the
agents (giving it more checking options and probably also giving it alerting
options)
I'm sure that before we actualy get to the next major release that we will have
much more :-)
Dirk Bulinckx.
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Petr
Bohac
Sent: Sunday, November 25, 2007 6:16 AM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Salive roadmap
Yes, I did it. You might not remember the issue but you were working closely
with me on the problem. Running all the time dbgview, sending you reports ...
Ok, remote agent check is a huge new feature. That's true. I don't expect those
2 features I mentioned to be in 6.1. I mean people proposed some features they
would like to have it in the SA, you said, ok, I'll think about that. Most of
them were really interesting things so I think it will be nice to have a page
(or whatever) with a list of features and short comment with them (might be in
6.5, definitely not in 7, not possible etc) ... nothing more.
Thanks you will think about that ;)
Petr
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Bulinckx
Sent: 24 November 2007 21:46
To: Servers Alive Discussion List
Subject: RE: [SA-list] Salive roadmap
About the stability, did you make the registry change explain on the beta page
for build 2149?
I see about 40 "added" items. For example adding the "remote agent check"
might be one line, but is a huge new feature.
The 2 features you talk about (password manager and mass editing of checks)
will NOT be in v6.1
The current beta is from a feature point of view what will be in v6.1
I'll see for a "roadmap" for the next major release…
Dirk Bulinckx.
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Petr
Bohac
Sent: Saturday, November 24, 2007 6:11 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Salive roadmap
Well I do check the beta page. Alright there's been some updates to the Salive,
I can't say there wasn't, but I think those were mainly bug fixes. Don't get me
wrong I was just asking for some road map or anything because there were so
many requests ...
As for features ... again, there were many requests, password manager, mass
editing of checks etc. ... and actually my main concern is stability. Since we
upgraded from the 5.x to 6.x and 6.1 beta (we were forced, just because of a
bug in the SMPP alerting engine) we lost stability. The SA hangs from time to
time for no reason. The problem wasn't detected so I'm forced to check the SA
service by vbscript. I believe I'm not alone since I do read mailing list.
Thank you
Petr
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Bulinckx
Sent: 24 November 2007 20:21
To: Servers Alive Discussion List
Subject: RE: [SA-list] Salive roadmap
The proposals that were done at that time were not realy GUI improvements. I
"think" we did add a few things that were said at that time. There is a beta
site/page that shows all changes that we did, it's on http://beta.woodstone.nu
(http://beta.woodstone.nu)
Saying "lacks many features" is very vague, can you be more concrete with that?
Dirk Bulinckx.
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Petr
Bohac
Sent: Saturday, November 24, 2007 12:51 PM
To: Servers Alive Discussion List
Subject: [SA-list] Salive roadmap
Hi Dirk,
a couple of weeks ago you asked us what we would like to improve on GUI and
many of us sent a bunch of proposals for a new features. You said that some of
them might be very easily included in future betas (6.1). So I'd like to ask
whether you have some roadmap or some beta status page stating what you are up
to.
I don't really know where is salive going and it might be useful to give us
some info. Indeed is Salive a great product for a great price but it also lacks
many features. At this moment I'm being pushed to look for other alternatives
(IP Monitor, OPS Manager 2007 ...) and there are many reasons like
manageability, reporting, stability ...
Thank you
Petr
--------------------------------------------------------------------------------
This e-mail including any attachment is intended only for the recipient(s)
named. It may contain confidential information and should not be read, copied
or otherwise used by any other person. If you are not a named recipient, please
contact the sender and delete the e-mail from your system. The sender does not
accept any liability for errors or omissions in the content of this message or
for viruses, or any damage due to the e-mail. The recipient is advised to have
appropriate virus check software.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
--------------------------------------------------------------------------------
This e-mail including any attachment is intended only for the recipient(s)
named. It may contain confidential information and should not be read, copied
or otherwise used by any other person. If you are not a named recipient, please
contact the sender and delete the e-mail from your system. The sender does not
accept any liability for errors or omissions in the content of this message or
for viruses, or any damage due to the e-mail. The recipient is advised to have
appropriate virus check software.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
--------------------------------------------------------------------------------
This e-mail including any attachment is intended only for the recipient(s)
named. It may contain confidential information and should not be read, copied
or otherwise used by any other person. If you are not a named recipient, please
contact the sender and delete the e-mail from your system. The sender does not
accept any liability for errors or omissions in the content of this message or
for viruses, or any damage due to the e-mail. The recipient is advised to have
appropriate virus check software.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
