|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
FreeBSD monitoring tool
Hi,
we made a first public release of the FreeBSD monitoring solution (it's cross-platform, but we consider FreeBSD as one of our primary platform) and I'm looking for those, who interested to give it a try and come back with the feedback. You're only required to register and install the monitoring part on your server - FreeBSD 7.* and higher (which is just 1-2 minutes - depending on how fast you are) and provide your feedback (as much as you'd like). We looking to build a proper, useful full coverage monitoring solution for FreeBSD and need your feedback. Those who interested - please, let me know or, if the moderator will allow, I drop the link here. Kind regards, Alexander. |
|
|||
Ok, from what I was told, I can post the link as well: http://10bees.com
Please, let me know on your feedback - it's very important and highly appreciated - here or using the contacts on the site, whatever works better for you. Thanks. Last edited by J65nko; 23rd May 2013 at 02:50 PM. Reason: Turn URL into proper link |
|
|||
Please note that the install of these monitoring tools comes in the form of a FreeBSD package. Right now I don't have the opportunity to check whether this package has been verified/approved by a FreeBSD ports committer.
From pkg_add(1): Code:
WARNING Since the pkg_add command may execute scripts or programs contained within a package file, your system may be susceptible to ``trojan horses'' or other subtle attacks from miscreants who create dangerous package files. You are advised to verify the competence and identity of those who pro- vide installable package files. For extra protection, use the -M flag to extract the package file, and inspect its contents and scripts to ensure it poses no danger to your system's integrity. Pay particular attention to any +INSTALL, +POST-INSTALL, +DEINSTALL, +POST-DEINSTALL, +REQUIRE or +MTREE_DIRS files, and inspect the +CONTENTS file for @cwd, @mode (check for setuid), @dirrm, @exec, and @unexec directives, and/or use the pkg_info(1) command to examine the package file.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
Quote:
We do have a port as well, which is used to make a package and I hope it will be accepted by a FreeBSD team - any help here will be appreciated. Regarding the security - you can verify what the package will be doing by using a Code:
pkg_add --dry-run 10bees.tbz If any comments or other details required - just let me know, I'm happy to clarify! |
|
|||
Hi,
just to bring an update – we relaunched the service a while ago and recently rolled out an updated version with most of the concerns addressed. You can find the details in our blog (blog.10bees.com), created to keep our customers up to date with the major updates and changes. The platform is matured and if you are looking for a FreeBSD hosted monitoring solution - please, give it a try and drop us an e-mail if anything we can do for you. |
|
|||
Quote:
I see your point. The primary goal for doing this is to make sure that the dashboard (quite a JS & CSS intensive page) will be delivered in a proper way, and we decided to join a 37signals approach (signalvnoise.com/posts/3097-developing-for-old-browsers-is-almost-a-thing-of-the-past). Let us address this - what is the browser you are using? I'm guessing it could be some non-standard WebKit wrapper? |
|
||||
I use Opera 12, the latest version available for Linux (which is still supported). Not that this really matters, since no browser other than IE/Firefox/Chrome/Safari will work...
IMHO It's always best to assume the user's browser will work, unless you have a good reason to think otherwise, for example you know a version has a specific bug, or a certain feature is missing (it's often easy to detect this). so blacklist, rather than whitelist. Even then, it may just be a good idea to just display a warning, and let the user continue. *Maybe*, the user knows what he/she is doing, or just *maybe*, you detection script is broken, or *maybe* something changes in browsers, etc...
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
|||
Makes perfect sense. I'm registering this as an improvement suggestion on your behalf via our support system; if you send me your mail via personal messages, I will associate this with you and you will be personally notified on the progress.
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
system monitoring advice | frcc | OpenBSD Security | 8 | 23rd January 2013 10:12 PM |
Network Monitoring Software | Nato85 | OpenBSD Packages and Ports | 3 | 18th July 2012 07:01 PM |
ZFS Performance monitoring | replaysMike | FreeBSD General | 1 | 14th November 2009 09:32 AM |
How to: DMESG Monitoring | damien-NF | FreeBSD Installation and Upgrading | 2 | 4th August 2009 11:30 PM |
pf NAT monitoring | cerulean | FreeBSD General | 1 | 20th October 2008 12:27 PM |