Skip to main content
  • 2107 Accesses

Abstract

You need to know about errors on the systems in your environment before they turn into major problems. You also need the ability to see the actions your automation system is performing. This means you’ll need two types of reporting:

  • Log reports that capture bad strings, report them immediately, and ignore the rest

  • Log reports that ignore “okay” strings and report on what’s left

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 49.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Rights and permissions

Reprints and permissions

Copyright information

© 2009 Nate Campi, Kirk Bauer

About this chapter

Cite this chapter

(2009). Generating Reports and Analyzing Logs. In: Automating Linux and Unix System Administration. Apress. https://doi.org/10.1007/978-1-4302-1060-3_9

Download citation

Publish with us

Policies and ethics