New Feature Request: Getting file from client/etc hobbit-clients directory... 🔗 link

A centralized monitor system is really a nice thing to have but it could
be also a nice feature to be able to get files from clients just like
the client could get files in the etc directory of hobbit server...

Writing the database and weblogic clients I've put in options to include
other configuration files in the main config file for those clients.
This was a feature needed by my database administrator and sap
administrator group (will also be used by my weblogic administrators) so
that each of them can edit their warning/alert levels without having to
go through a big config file or affecting others database warning/alert
level. For now i'm getting the file manually but it could be nice if the
server could get files from the clients (limited for example to the
client/etc directory for security reason) just like the client do with
the server...

Francesco

Francesco Duranti a écrit :

The "download" feature outlined in "man 1 bb" should do that.

NAME
       bb - Hobbit client communication program
[...]
download FILENAME
              Download a file from the Hobbit servers' download directory.


Regards,

-- 
Charles Goyard - user-98f9625a7a59@xymon.invalid - (+33) 1 45 38 01 31

Charles Goyard a écrit :

Forget about that, I need more coffee %-).

-- 
Charles Goyard - user-98f9625a7a59@xymon.invalid - (+33) 1 45 38 01 31

On Wed, Aug 30, 2006 at 08:27:27PM +0200, Francesco Duranti wrote:

[snip section about using this for server admins to manage the Hobbit config]

I don't like that, for several reasons.

1) Stability. If one of your users makes a mistake in the configuration
   file that is uploaded, it could affect all of your monitoring. Hobbit
   client- and alert-configuration uses pattern-matching a lot, so
   allowing anyone to modify the configuration requires a lot of care;
   they can easily affect the configuration of other hosts.

2) Security. Same reasons as 1), except that you also have to consider
   the possibility of someone deliberately sabotaging your configuration
   instead of just making an accidental mistake. If I want to do
   something bad to your hosts, being able to disable your monitoring
   system is really nice. An anonymous upload function could be abused
   for this purpose.

3) There are lots of other ways of accomplishing this. You can use the
   local client-configuration option (keep all of the client
   configuration files on the client), or there's ftp/rsync/scp/nfs etc.
   to allow exchanging of files between two systems. And they have much
   better access controls than Hobbit does. Unless there's a good reason
   for it, I try not to re-invent things.

If you really want this, there is nothing that stops you from adding a
custom section to the client message - just put it at the bottom of the
Hobbit client script - and then over on the server grab the client
message and extract the configuration file from that.


Regards,
Henrik

I like to suggest in future version of hobbit to replace Tigra with other 
java script menu system like YUI.
This is my personal opinion, YUI has more to offer in term of menu 
capabilities while Tigra is free to offer basic menu fuctions.

I like to hear Henrik's and others  comment on this subject.

References :
http://www.softcomplex.com/products/tigra_menu/
http://developer.yahoo.com/yui/

T.J. Yang

I like to suggest in future version of hobbit to replace Tigra with other 
java script menu system like YUI.
This is my personal opinion, YUI has more to offer in term of menu 

capabilities while Tigra is free only on   basic menu fuctions.

I like to hear Henrik's and others  comment on this subject.

References :
http://www.softcomplex.com/products/tigra_menu/
http://developer.yahoo.com/yui/

T.J. Yang

On Thu, Aug 31, 2006 at 06:54:09AM -0500, T.J. Yang wrote:

I'm fairly indifferent to which system is used. The only requirements
I have are that

a) they must be licensed with an Open Source compatible license
   (Tigra is public domain, YUI is BSD)
b) they are easy to integrate into the Hobbit web/ templates
c) they are easy to distribute and install.

Since I don't have any real need to switch, I don't really care much
about looking into what it would take to swicth. If someone else is willing to work on it, that would be fine.

So to sum up, since the web/ template-files really are considered configuration files that you may change - feel free to modify them to
suit whatever needs you have. If you think the modifications are
generally useful, you might want to contribute them to the project.
I think the new Shire repository would be an excellent place to begin placing such modified template-files.


Regards,
Henrik