Giter Site home page Giter Site logo

Log parsing clarification about pgmetrics HOT 4 OPEN

rapidloop avatar rapidloop commented on August 18, 2024
Log parsing clarification

from pgmetrics.

Comments (4)

mdevan avatar mdevan commented on August 18, 2024 1

Would it be possible to add a small section to the docs highlighting what extensions are needed for what feature? Perhaps even showing the ideal/expected settings associated for each.

That sounds useful, will add. Thanks for the suggestion!

from pgmetrics.

mdevan avatar mdevan commented on August 18, 2024

Currently, pgmetrics can only parse local log files that are actually present as files in the filesystem.

In case of remote servers, you'll have to first fetch the log files (over scp/rsync or similar) to the server where pgmetrics is running, and then invoke pgmetrics. In future, we plan to support an scp-like syntax for the --log-file/--log-dir options.

Syslog/journald also will have to be pulled out into a file somehow before invoking pgmetrics. Not sure if we'll be adding support for this in the future though. Note that the extracted file should have lines that match the "log_line_prefix" configuration setting.

and seemingly associated info in the output, like Slow Queries

pgmetrics currently collects (1) autovacuum runs, (2) deadlocks and (3) auto_explain query plans from log files. Slow queries output comes from pg_stat_statements.

from pgmetrics.

tomswartz07 avatar tomswartz07 commented on August 18, 2024

you'll have to first fetch the log files (over scp/rsync or similar) to the server where pgmetrics is running

That's a reasonable workaround for the time being. Thanks for the info.

pgmetrics currently collects (1) autovacuum runs, (2) deadlocks and (3) auto_explain query plans from log files. Slow queries output comes from pg_stat_statements.

Ah, thanks for clarifying. The docs were not super clear on this front, it seemed to imply that there were some magic that grabbed log lines from log_min_duration_statement no explicit mention of pg_stat_statements for that.

Would it be possible to add a small section to the docs highlighting what extensions are needed for what feature? Perhaps even showing the ideal/expected settings associated for each.

Thanks again for the very nice project!

from pgmetrics.

tomswartz07 avatar tomswartz07 commented on August 18, 2024

Thanks very much @mdevan

Feel free to close this now, or if you prefer to keep it opened until such docs have been added, that's fine too.

Cheers

from pgmetrics.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.