Paul Bunyan features

:: Paul Bunyan Features  ::

A Logger of Legendary Proportion!

Paul Bunyan offers a wide array of robust functionality.  Click on the features below to see how Paul Bunyan resolves your diagnostic and analysis needs.   To see list of features by Edition – click here

Centralized Logging	Rich Contextual Information
One-to-Many / Many-to-One Connectivity	Powerful Message Filtering
Lightning Speed – Zero Performance Impact	Multi-query Display
Minimal Resource Usage	Import / Export Capabilities
Ships With Release Builds	Security / Privacy
Supports Many Languages and Environments	Message Forwarding
Supports Unicode and ANSI Characters	Open Architecture

Centralized Logging

Log messages spanning threads, processes, languages, machines, and sites all get pulled together for single source viewing. No manual merging of application logs, text files, or databases.

Back to top

One-to-Many / Many-to-One Connectivity

Multiple viewers can simultaneously download log messages from a single message server or conversely a single viewer can be used to download log messages from multiple servers. The same is true with regard to servers forwarding messages to other servers or passing them to message handlers.

Back to top

Lightning Speed – Virtually Zero Impact on Performance

Paul Bunyan is lightning fast and with logging rates above 50K messages/second is virtually undetectable in even the most performance critical applications.

Back to top

Minimal (and Configurable!) Memory, CPU, and Resource Impact

Paul Bunyan uses internal data compression in memory, on disk, and on the wire and does all backend processing on low priority threads. It is extremely resource efficient and is completely configurable with regard to process memory usage and disk space usage.

Back to top

Ships With Release Builds (and With No Royalties!)

Paul Bunyan was designed to be left in and shipped with release builds of code. It is extremely fast, light, and secure. It also requires no modifications to build and/or installation procedures as there are no DLLs or other components to ship (if using the C/C++ API) and it is self disabling on machines where Paul Bunyan is not installed. It is highly advantageous to leave the logging code compiled into shipping applications since enabling it then requires nothing more than installing Paul Bunyan.

Back to top

Supports Wide Array of Programming Languages and Environments

The native API is C and C++ which can be called from many other languages such as Assembly and PASCAL. There is also a COM wrapper that can be invoked from automation clients, ASP (Active Server Pages), VB Script, Visual Basic, and VBA-supporting applications such as Microsoft’s Access, Word, Excel. Additional API extensions are also available as downloadable freeware. Current API extensions include SQL Server, Sybase, InstallShield, and others.

Back to top

Supports Both Unicode and ANSI Character Sets

The C/C++ API and COM interface both fully support the Unicode character set for internationalization usage. It is supported concurrently with the ANSI version of the API so that an application can simultaneously log Unicode and ANSI data regardless of how it is compiled.

Back to top

Rich Contextual Information

Each log message contains fields for message type, timestamps (Source, Local, and GMT), component, context, machine, process, module, file, line number, process id, and thread id.

Back to top

Powerful Message Filtering

Paul Bunyan supports filtering functionality that is very simple to use yet very powerful. Filtering can be used on an inclusive or exclusive basis and can be applied as selectively as desired to any log message field or fields.

Back to top

Multiple Display Queries

Paul Bunyan supports the concept of queries which are essentially filters with associated display parameters. There may be as many queries as desired for selecting, sorting, and viewing log messages in various manners.

Back to top

Import / Export Capability

Log messages can be exported in standard format readable by virtually any import facility. All objects within a workspace can also be imported from one workspace to another.

Back to top

Security / Privacy

Log messages are encrypted immediately upon creation even before they are transmitted to the message server and stay encrypted whether on disk or wire. Further, log messages can be locked up programmatically with message keys at the time of creation and subsequently only downloaded and viewed by users providing that message key so there is no risk of airing sensitive logging in front of clients or competition.

Back to top

Message Forwarding

Log messages can be forwarded from one message server to another. They can be forwarded from one server to many, many to one, and/or cascaded serially. This allows, for instance, messages from multiple internal machines on a site to be forwarded to one central externally reachable location where they can be downloaded or processed by message handlers. It also allows log messages to be routed to machines where they can be processed with local message handlers.

Back to top

Open Architecture (Support for Custom Message Handlers)

Paul Bunyan’s powerful open architecture provides access to log messages via its message handler interface. Message handlers are used for handling events, logging transactions to databases, creating audit trails, translating and forwarding messages to enterprise event handling systems (e.g. Tivoli®, NetIQ®, RoboMon®, or Opalis®), and more.  Diamond Sierra has already released two such products – Ox and Falcon

Back to top