LogImport(3)

πŸ’– LogImport(3) πŸ’–

okay bestie, so this is LogImport(3) from the User Contributed Perl Documentation and it's genuinely one of the most useful little pages you'll ever read, no cap.


🌸 NAME 🌸

PCP::LogImport β€” a Perl module for importing performance data to create a Performance Co-Pilot archive. it's giving "data goes in, archive comes out", and we're obsessed. ✨


πŸŽ€ SYNOPSIS πŸŽ€

use PCP::LogImport;

that's it. that's the whole vibe. one line and you're in. πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

So the PCP::LogImport module is holding the language bindings for building Perl applications that import performance data from a file or a real-time source, and then create a Performance Co-Pilot (PCP) archive that's suitable for use with the PCP tools. like, it's literally the glow-up pipeline for your perf data. 😭

And the routines in this module? they're wrappers around the libpcp_import library, plus some of the routines from the libpcp library. so you get all that power without having to rawdog the C API. iconic behaviour, fr fr. πŸ”₯


✨ SEE ALSO ✨

okay this list is LONG but every single one of these is part of the family, so let's go:

and if you still have questions after reading every single one of those (valid, honestly), the PCP mailing list pcp@groups.io can be used for questions about this module. bestie support group behaviour. 🫢

Further details can be found at https://pcp.io β€” go look, it's a whole thing. 🌈


πŸ‘‘ AUTHOR πŸ‘‘

Ken McDonell, <kenj@kenj.id.au>

Copyright (C) 2010 by Ken McDonell. Copyright (C) 2018,2022 Red Hat.

This library is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License, version 2 (see the "COPYING" file in the PCP source tree for further details).


and that's the whole page, babe. πŸ’œ

source/version check: perl v5.42.3, dated 2026-10-19, and yes this is LogImport(3) β€” go forth and import that data, you absolute legend. ⭐
πŸ“¦ where this page comes from