|
Permissions
With tree-based "read/write/browse" permissions and "user/group/other" ownership, you can define very specific user roles and administrator domains.
Building Blocks
Augur provides abstraction layers so you can create reusable building blocks help you manage large configurations. For example, a list of elements could be stored as a named grouping. Then you can reference that grouping in filters and other places.
GUI and XML
The GUI is Augur's primary configuration tool, but configuration can also be batched via the command line and an XML file.
Anecdotal Evidence
We think Augur is relatively fast to configure. Here is one example: A customer needed to monitor a device that could generate a staggering 2,400 unique event types. It took a well-known consulting company months to create the rule sets for the customer's existing Netcool system. When the customer tapped us, one of our developers built an equivalent Augur rule tree in two weeks.
|
|
Concurrent Editing
Multiple administrators can edit the configuration simultaneously. The tree manager coordinates sessions to prevent conflicts.
No Resets
Changes are automatically distributed to all clients and servers. No resets or downtime required.
Change Log
All changes include a log with the user name, date, and a description. The editor can show you the complete history of each node.
Clippings
You can save any part of the configuration tree as a file, called a clipping. You can email clippings to anyone. That person can load the clipping into their Augur. This is great for support, sharing rule trees, etc.
Take a look at the interface.
|
|