Using logging hooks for real-time log analysis
Formal Metadata
| Title | Using logging hooks for real-time log analysis |
|
| Alternative Title | Use logging hooks for real-time log analysis |
|
| Title of Series | |
| Number of Parts | 25 |
| Author | |
| Contributors | |
| License | CC Attribution - NonCommercial - ShareAlike 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Ottawa, Canada |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | If you want to know right now what your server has been doing
When problems arise, every DBA wants to know what the database has been up to. If your best idea so far has been to parse the log files or load the CSV logs into another database, you might want to learn about a better way.
With logging hooks, you can attach data sinks directly to the PostgreSQL server log stream and analyze logging events as they happen. Many useful applications arise this way: put log data into another PostgreSQL database for ad hoc querying store log data in Hadoop for analytics throw log data into a graphing system generate alerts directly from logging events
I'll show you how to put these things together and use them in practice. |
|
