Welcome to SysOrb knowledge base. Her you will find detailed explanation on questions regarding SysOrb. The list is under continues development and new articles will be added. You can follow the links below or enter a "key word" to search all of the articles.
- Agent crashes
- Automatic rescan of all nodes in a domain
- Bandwidth consumption estimate
- Basic database tuning
- Can I customize the reports in SysOrb?
- Disabling specific checks
- Does SysOrb support SNMP traps?
- Explanation of the score keeper strategy.
- How does HTTP Netcheck work in SysOrb?
- How to automatically update alert group on all nodes to “As domain”
- How to backup SysOrb database
- How to change time interval value of agent_checkin_delay
- How to move the SysOrb server to a new server
- How to quickly set downtime on an agent
- I cannot get all of the "performance counters/cache" entries to appear in SysOrb what should I do?
- Migrating MIB information from one SysOrb installation to another
- Migrating the configuration of a Windows SysOrb server from 32 to 64 bits
- No empty blocks in meta database.
- Script to get a list of nodes which have no AlertGroup
- SysOrb agent is not checking in to the Sysorb server
- SysOrb agent stops checking in from a windows server with very long system uptime
- SysOrb server shuts down unexpectedly
- System uptime no longer updates on windows
- Unable to monitor hardware (fans, disks, temperatures etc.) on Windows
- Upgrading SysOrb on Windows
- Uploading a SysOrb database to Evalesco
- What does KiB and MiB mean?
- What is IPMI ?
- Windows agent late for check-in every hour
Bandwidth consumption estimate
As the agent performs checks on servers and transmits the results back to the central monitoring server, it consumes only very little bandwidth. The amount of bandwidth required is determined by two factors
- The check interval - the more frequent checks, the more results and therefore more data to send
- The number of active checks - the more checks to send results for, the more data we send
There is a little bit of overhead to establish the agent check-in at the configured check-in interval, but this is insignificant compared to the transmission of the check data in all normal configurations.
Furthermore, if the agents check in to a satellite and the satellite forwards the results to a master, the exact amount of data will also be somewhat affected - but all in all the amount of data in need of transmission still follows the amount of check data gathered.
As a rule of thumb, for checks configured to run on 30 second intervals, you should expect to see
one byte per second per check
being used for agent check data transmissions.
So, if you have 100 agents, each with 100 checks and each check is configured to be run every 30 seconds, the total averaged network data utilization will be roughly equivalent to:
100 [agents] * 100 [checks] * 1 [byte per second per check] = 10 [kB per second]
So a fairly sizable network of servers can be monitored with 100 checks per server using a total of around 100kbps or 0.1% of an old 100Mbit ethernet.