user_guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
user_guide [2007/06/21 12:25] morten |
user_guide [2011/04/08 14:02] (current) faltin [The back-end processes] |
||
|---|---|---|---|
| Line 55: | Line 55: | ||
| - | ===== The back-end processes ===== | + | |
| + | |||
| + | ====== The back-end processes ====== | ||
| NAV has several back-end processes (or services as they are sometimes called) that perform the various data collection, monitoring and administrative/maintenance tasks. Some of the processes are background daemons, while others are just cron jobs. They can all be started and stopped individually by using the **nav** command. | NAV has several back-end processes (or services as they are sometimes called) that perform the various data collection, monitoring and administrative/maintenance tasks. Some of the processes are background daemons, while others are just cron jobs. They can all be started and stopped individually by using the **nav** command. | ||
| Line 77: | Line 79: | ||
| </code> | </code> | ||
| - | All processes run as the unprivileged ''navcron'' - the only exception is the *pping* process, which must be started as *root* to able to create a raw ICMP socket, and will drop privileges and run as the *navcron* user immediately after. | + | All processes run as the unprivileged //navcron// user - the only exception is the //pping// process, which must be started as //root// to able to create a raw ICMP socket, and will drop privileges and run as the //navcron// user immediately after. |
| These are the various services: | These are the various services: | ||
| - | ^ Service ^ Type ^ Description ^ | + | ^ Service ^ Type ^ Description ^ |
| - | | alertengine | Daemon | Parses users' alert profiles and dispatches alerts from the global alert queue accordingly | | + | | [[alertengine]] | Daemon | Parses users' alert profiles and dispatches alerts from the global alert queue accordingly. | |
| - | | cricket | Cron | 3r | + | | [[cricket]] | Cron | 3rd party software that collects statistical data from IP devices through SNMP queries. | |
| + | | [[eventengine]] | Daemon | Processes events posted to NAV's internal event queue. Translates events into alerts to post on the alert queue. | | ||
| + | | [[ipdevpoll]] | Daemon | NAV's main SNMP collection engine. Collects just about everything except statistical data, and stores it in the NAV database. This includes serial numbers, modules, interfaces, routing information etc. | | ||
| + | | [[iptrace]] | Cron | Collects ARP tables from monitored routers and stores in the NAV database. | | ||
| + | | [[logengine]] | Cron | Parses the latest syslog messages from Cisco devices on disk and stores them in the NAV database. | | ||
| + | | [[mactrace]] | Cron | Collects CAM tables and CDP neighbors from switches. This data is used to build the network topology. mactrace also uses the known topology to store CAM entries for client machines on the correct access ports. | | ||
| + | | [[maintengine]] | Cron | Effectuates the maintenance schedule by dispatching maintenance events onto the internal event queue. | | ||
| + | | [[networkDiscovery]] | Cron | Interprets the candidate topology mactrace has stored in the database, and derives the actual physical and vlan topologies of the network in a two-step process. | | ||
| + | | [[pping]] | Daemon | The parallel pinger - sends ICMP echo requests to all IP devices, waits for replies and dispatches boxState events accordingly. The daemon also records ping response time statistics using [[rrdtool]]. | | ||
| + | | [[servicemon]] | Daemon | The service monitor. Monitors services on IP devices, such as SSH, HTTP, SMTP and others, according to the configuration entered in the [[editdb|Edit database web tool]]. Also records service response times using [[rrdtool]]. | | ||
| + | | [[smsd]] | Daemon | Dispatches SMS messages placed on the sms queue by the [[alertEngine]]. Uses dispatcher plugins to dispatch messages through various methods - most commonly by using [[Gammu]] with a locally connected mobile phone. | | ||
| + | | [[thresholdMon]] | Cron | Monitors all known RRD files for exceeded threshold, according to user-configured thresholds, and dispatched threshold events accordingly. | | ||
user_guide.1182428742.txt.gz · Last modified: 2007/06/21 12:25 by morten
Page Tools
