2008-03-23 Sancho Lerena <slerena@gmail.com>
* pandoradb.sql: Upgraded SQL schema for Pandora FMS 2.0
* pandoradb_13_to_20: Moved filename (renamed). This don't work yet.
* README: Deleted. Not used anymore.
git-svn-id: https://svn.code.sf.net/p/pandora/code/trunk@768 c3f86ba8-e40f-0410-aaad-9ba5e7f4b01f
This commit is contained in:
slerena
parent
b343ccdd01
commit
d54269a3ee
|
|
@ -1,3 +1,9 @@
|
|||
2008-03-23 Sancho Lerena <slerena@gmail.com>
|
||||
|
||||
* pandoradb.sql: Upgraded SQL schema for Pandora FMS 2.0
|
||||
|
||||
* pandoradb_13_to_20: Moved filename (renamed). This don't work yet.
|
||||
|
||||
2008-03-19 Manuel Arostegui <marostegui@artica.es>
|
||||
|
||||
* pandora_console.spec: Solved a problem with Suse based
|
||||
|
|
|
|||
|
|
@ -1,143 +0,0 @@
|
|||
Pandora FMS : The Free Monitoring System (v1.3)
|
||||
===============================================
|
||||
|
||||
http://pandora.sourceforge.net
|
||||
|
||||
What is Pandora FMS
|
||||
-------------------
|
||||
|
||||
Pandora watches your systems and applications, and allows you to know the status of any element
|
||||
of those systems. Pandora could detect a network interface down, a defacement in your website,
|
||||
a memory leak in one of your server app, or the movement of any value of the NASDAQ new
|
||||
technology market. If you want, Pandora could send out SMS message when your systems fails...
|
||||
or when Google's value drop below US$ 33.
|
||||
|
||||
Pandora will adjust, like an octopus, to your systems and requirements, because has been
|
||||
designed to be open, modular, multiplattform and easy to customize and use, all integrated into
|
||||
a scalable and distributed architecture.
|
||||
|
||||
Pandora runs on any operating system, with specific agents for each platform gathering data and
|
||||
sending it to a server, it has specific agents for GNU/Linux, AIX, Solaris, HP-UX, BSD/IPSO,
|
||||
and Windows 2000, XP and 2003.
|
||||
|
||||
Pandora can also monitor any kind of TCP/IP service, without the need to install agents, and
|
||||
monitor network systems such as load balancers, routers, switches, operating systems,
|
||||
applications, or simply printers if you need. Pandora also supports SNMP for collecting data
|
||||
and for receiving traps.
|
||||
|
||||
A few examples of common resources monitored by Pandora could be processor load, disk and
|
||||
memory usage, running processes, log files, environmental factors such as temperature, or
|
||||
application values like strings contained in web pages or any possible way to collect data in
|
||||
an automatic way.
|
||||
|
||||
Pandora FMS Features
|
||||
--------------------
|
||||
|
||||
* Lightweigth agents. No need to install adicional software.
|
||||
* Also could use network to collect data on remote systems.
|
||||
* High availability for each component.
|
||||
* Escalable architecture: no liminitation on number of servers you can setup for the same enviroment.
|
||||
* Internal detection on Network Servers in case of failure, automatic takeover of secondary servers.
|
||||
* Stores all data for many weeks or months
|
||||
* Support for implementing redundant and distributed monitoring servers.
|
||||
* Data is stored in a relational database (MySQL).
|
||||
* Automatic database optimization for size, using interpolation and compression algorithms.
|
||||
* Integrated alert systems: send mails, execute scripts, send SMS, or simply write to syslog are a few examples.
|
||||
* Integrated graphical reporting system for any kind of collected data.
|
||||
* SNMP Trap reception with Realtime Console.
|
||||
* Granularity of accesses and user profiles for each group and each user.
|
||||
* Integrated internal auditing for any operation.
|
||||
* Alert filtering to avoid false positives.
|
||||
* Event system with user validation for operation in teams.
|
||||
* Integrated incident system with flows and different profiles.
|
||||
* Any collected value can be displayed as graph or data table.
|
||||
* Alerts can be triggered any kind of event, in many ways.
|
||||
* WebConsole on line HTML contextual help.
|
||||
* Integrated DB management: purge and DB compaction.
|
||||
* Mass configuration/alert manager to copy and distribute agent-module and/or agents/alerts setup to other agents.
|
||||
* Profiles could be personalized using up to eight security attributes without limitation on groups or profiles.
|
||||
* Filters for collected data to avoid bad data.
|
||||
|
||||
What do I need?
|
||||
---------------
|
||||
|
||||
Perl 5.8, Some Perl modules, MySQL4x or higher, PHP5, and some PHP Modules. See the
|
||||
Installation Documentation or go to http://pandora.sourceforge.net
|
||||
|
||||
|
||||
Install
|
||||
-------
|
||||
|
||||
Please visit our online documentation site or download install guides at
|
||||
http://pandora.sourceforge.net.
|
||||
|
||||
|
||||
Quick install guide
|
||||
-------------------
|
||||
|
||||
Install openssh server
|
||||
|
||||
apt-get install ssh
|
||||
|
||||
Download console tarball and uncompress on /tmp/pandora/pandora_console
|
||||
|
||||
cd /tmp
|
||||
tar xvzf /whateveritwere/pandora_console_xxxx.tar.gz
|
||||
|
||||
Install apache, php, mysql (LAMP) and some PHP5 modules:
|
||||
|
||||
apt-get install libapache2-mod-php5 apache2 mysql-server php5-gd php5-mysql pear php5-snmp
|
||||
|
||||
Move pandora_console to /var/www
|
||||
|
||||
mv pandora_console/ /var/www
|
||||
|
||||
Change owner to www-data (apache2 user)
|
||||
|
||||
chown -R www-data /var/www/pandora_console/
|
||||
|
||||
If you're installing your mysql, setup a root password, for example "none"
|
||||
|
||||
mysqladmin password none
|
||||
|
||||
Access with a browser to this machine, in my case, to 192.168.50.126
|
||||
|
||||
http://192.168.50.126/pandora_console
|
||||
|
||||
A webpage should show you a welcome screen to install wizard. Read carefully and press "NEXT"
|
||||
to begin installation and go to step 2.
|
||||
|
||||
Module dependencies are tested here. Probably you need to cold restart your apache
|
||||
|
||||
/etc/init.d/apache2 stop
|
||||
/etc/init.d/apache2 start
|
||||
|
||||
Refresh your browser and you should see that now all dependencies are Ok. Let's go to step #3.
|
||||
|
||||
This screen need to enter data about your database root user (or other with privileges to
|
||||
create databases, table and insert data), and where is placed your Pandora FMS setup.
|
||||
|
||||
Enter mysql user and password (if you're follow this doc, step by step, should be root as user,
|
||||
none as password, and localhost as hostname), and let default values in last two boxes. Let's
|
||||
go to final step.
|
||||
|
||||
This should be done and Pandora Console fully installed. Last step is delete upgrade.php,
|
||||
install.php, all *.sql files:
|
||||
|
||||
rm upgrade.php
|
||||
rm install.php
|
||||
rm *.sql
|
||||
|
||||
And access to your new Pandora FMS console at
|
||||
|
||||
http://192.168.50.126/pandora_console/index.php
|
||||
|
||||
Login with user "admin" and password "pandora"
|
||||
|
||||
License
|
||||
-------
|
||||
|
||||
The project is distributed under the GPL License v2 or later.
|
||||
|
||||
Copyright (C) 2004-2007 Pandora FMS development team
|
||||
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
--------------------------------------------------------------
|
||||
-- Pandora FMS official tables for 1.4 version --
|
||||
-- Pandora FMS official tables for 2.0 version --
|
||||
--------------------------------------------------------------
|
||||
|
||||
CREATE TABLE `taddress` (
|
||||
|
|
@ -189,6 +189,12 @@ CREATE TABLE `talerta` (
|
|||
PRIMARY KEY (`id_alerta`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
|
||||
|
||||
CREATE TABLE `tcompound_alert` (
|
||||
`id` int(11) unsigned NOT NULL auto_increment,
|
||||
`id_aam` int(11) NOT NULL default '0',
|
||||
`operation` enum('NOP', 'AND','OR','XOR','NAND','NOR','NXOR'),
|
||||
PRIMARY KEY (`id`, `id_aam`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
|
||||
|
||||
CREATE TABLE `talerta_agente_modulo` (
|
||||
`id_aam` int(11) unsigned NOT NULL auto_increment,
|
||||
|
|
@ -211,56 +217,18 @@ CREATE TABLE `talerta_agente_modulo` (
|
|||
`disable` int(4) default '0',
|
||||
`time_from` TIME default '00:00:00',
|
||||
`time_to` TIME default '00:00:00',
|
||||
`id_agent` int(11) default NULL,
|
||||
`monday` tinyint(3) default '0',
|
||||
`tuesday` tinyint(3) default '0',
|
||||
`wednesday` tinyint(3) default '0',
|
||||
`thursday` tinyint(3) default '0',
|
||||
`friday` tinyint(3) default '0',
|
||||
`saturday` tinyint(3) default '0',
|
||||
`sunday` tinyint(3) default '0',
|
||||
`recovery_notify` tinyint(3) default '0',
|
||||
PRIMARY KEY (`id_aam`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
|
||||
|
||||
CREATE TABLE tnotification (
|
||||
`id` int(11) unsigned NOT NULL auto_increment,
|
||||
`name` varchar(255) default '',
|
||||
`description` varchar(255) default '',
|
||||
`id_alerta` int(11) NOT NULL default '0',
|
||||
`id_agent` int(11) NOT NULL default '0',
|
||||
`al_f1` varchar(255) default '',
|
||||
`al_f2` mediumtext NOT NULL,
|
||||
`al_f3` mediumtext NOT NULL,
|
||||
`alrec_f1` varchar(255) default '',
|
||||
`alrec_f2` mediumtext NOT NULL,
|
||||
`alrec_f3` mediumtext NOT NULL,
|
||||
`recovery_notify` tinyint(3) default '0',
|
||||
`disabled` tinyint(3) default '0',
|
||||
`last_fired` datetime NOT NULL default '0000-00-00 00:00:00',
|
||||
PRIMARY KEY (`id`),
|
||||
KEY `tnotif_indx_1` (`id_alerta`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
|
||||
|
||||
CREATE TABLE `tnotification_component` (
|
||||
`id` int(11) unsigned NOT NULL auto_increment,
|
||||
`id_notification` int(11) NOT NULL default '0',
|
||||
`id_agente_modulo` int(11) NOT NULL default '0',
|
||||
`dis_max` double(18,2) default NULL,
|
||||
`dis_min` double(18,2) default NULL,
|
||||
`alert_text` varchar(255) default '',
|
||||
`time_threshold` int(11) NOT NULL default '0',
|
||||
`last_fired` datetime NOT NULL default '0000-00-00 00:00:00',
|
||||
`max_alerts` int(4) NOT NULL default '1',
|
||||
`min_alerts` int(4) NOT NULL default '0',
|
||||
`times_fired` int(11) NOT NULL default '0',
|
||||
`module_type` int(11) NOT NULL default '0',
|
||||
`internal_counter` int(4) default '0',
|
||||
`disabled` int(4) default '0',
|
||||
`time_from` TIME default '00:00:00',
|
||||
`time_to` TIME default '00:00:00',
|
||||
`monday` tinyint(3) default '0',
|
||||
`tuesday` tinyint(3) default '0',
|
||||
`wednesday` tinyint(3) default '0',
|
||||
`thursday` tinyint(3) default '0',
|
||||
`friday` tinyint(3) default '0',
|
||||
`saturday` tinyint(3) default '0',
|
||||
`sunday` tinyint(3) default '0',
|
||||
PRIMARY KEY (`id`),
|
||||
KEY `tnotifcom_indx_1` (`id_notification`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
|
||||
|
||||
CREATE TABLE `tattachment` (
|
||||
`id_attachment` bigint(20) unsigned NOT NULL auto_increment,
|
||||
`id_incidencia` bigint(20) NOT NULL default '0',
|
||||
|
|
@ -463,6 +431,8 @@ CREATE TABLE `trecon_task` (
|
|||
`status` tinyint(4) NOT NULL default '0',
|
||||
`interval_sweep` int(10) unsigned NOT NULL default '0',
|
||||
`id_network_server_assigned` int(10) unsigned NOT NULL default '0',
|
||||
`extended_info` varchar(250) default NULL,
|
||||
`extended_value` varchar(250) default NULL,
|
||||
PRIMARY KEY (`id_rt`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
|
||||
|
||||
|
|
@ -527,7 +497,6 @@ CREATE TABLE `ttrap` (
|
|||
PRIMARY KEY (`id_trap`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
|
||||
|
||||
|
||||
CREATE TABLE `tusuario` (
|
||||
`id_usuario` varchar(60) NOT NULL default '0',
|
||||
`nombre_real` varchar(125) NOT NULL default '',
|
||||
|
|
@ -690,4 +659,16 @@ CREATE TABLE `tquicksession` (
|
|||
`timestamp` datetime NOT NULL default '0000-00-00 00:00:00',
|
||||
`pwdhash` varchar(250) NOT NULL default '',
|
||||
PRIMARY KEY (`id`)
|
||||
);
|
||||
);
|
||||
|
||||
CREATE TABLE `tserver_export_data` (
|
||||
`id` int(20) unsigned NOT NULL auto_increment,
|
||||
`id_export_server` int(10) unsigned default NULL,
|
||||
`agent` varchar(100) NOT NULL default '',
|
||||
`type` varchar(50) NOT NULL default '',
|
||||
`module` varchar(100) NOT NULL default '',
|
||||
`value` varchar(100) NOT NULL default '',
|
||||
`timestamp` datetime NOT NULL default '0000-00-00 00:00:00',
|
||||
PRIMARY KEY (`id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue