Knowledge Base
Knowlegebase articles
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
How to automatically update alert group on all nodes to “As domain”
You would like to automatically update alert group on all nodes to “As domain” instead of doing it manually via the SysOrb web interface.
With SysOrb 3.8 it is possible to set Alert group for an entire domain. The administrator no longer needs to set alert group on each individual node but can set an alert group for an entire domain. This feature ease the configuration of SysOrb significantly and save a lot of time when configuring new domains and nodes.
However existing customers who has upgraded to SysOrb 3.8 from an earlier version of SysOrb will naturally have an alert group assigned to each individually node.
In order to automatically assign the alert group “As domain” to all nodes in a given domain then the following script can be used.
On windows the script should be place the folder: install-dir\SysOrb Server
// Win32 script to recursively update alertGroup value for all nodes in passed // as a parameter // domain and it's subdomains // // Usage: // cscript /nologo agupdate.js "start_domain" group_id // // // // Example: set alert group for all nodes starting from root domain to value 0.3 //("As Domain"): // // agupdate.js "." 0.3 // // // // // // arguments for 'sysorb-tool' utility (SysOrb should be running) var USER="admin" var PASS="admtest" var SERVER="localhost" var PORT="3241" var DOMAIN="." if (WScript.Arguments.Count() < 2) { WScript.echo("Usage: cscript agupdate.js \"start_domain\" alert_group_id"); WScript.Quit(-1); } var startDomain = WScript.Arguments(0); var alertGroupId = WScript.Arguments(1); // Execute 'sysorb-tool' utility var WshShell = new ActiveXObject("WScript.Shell"); var querycmd = "sysorb-tool -s " + SERVER + " -p " + PORT +" -d " + DOMAIN + " -l " + USER + " -P " + PASS + " listnodes -o i -r " + "\"" + startDomain + "\""; //WScript.echo(querycmd); var oExec = WshShell.Exec(querycmd); while (!oExec.StdOut.AtEndOfStream) { var node = oExec.StdOut.ReadLine(); var updatecmd = "sysorb-tool -s " + SERVER + " -p " + PORT +" -d " + DOMAIN + " -l " + USER + " -P " + PASS + " update -i " + node + " alertGroup=\"" + alertGroupId + "\""; WshShell.Exec(updatecmd); } WScript.echo("Done.");