|
Distributed Throughput
Augur is designed to scale from one,
to hundreds of distributed servers,
and one to thousands of users.
Augur's networked design, and optional
configuration levels of abstraction make this possible.
The chart below illustrates how
an Augur server's processing capacity remains
flat as additional event streams are added
— a hallmark of Augur's multi-threaded design.
|
Database
A multi-threaded database
avoids bottlenecks.
So separate event streams can create, clear, and page
alerts independently.
Configuration
Augur's configuration editor is designed
to support administrators from both
"local market"
and national perspectives.
Like a Unix filesystem, every node in the Augur's configuration tree
can be assigned read/write/browse permissions,
separately for the node's owner,
group(s), and "other".
This allows for secure distribution of configuration
responsibilities.
So local administrators can still maintain their own staff,
custom rule trees, non-standard equipment, etc.,
and at the same time, national teams
(NOC, standard equipment experts,
specialized support departments, etc.)
can control national standards and configure
paging for enterprise-wide staff.
|
Documents