PMIECONF(1)

🦋 NAME 🦋

okay bestie, welcome to pmieconf(1) 💖 — display and set configurable pmie rule variables. that's the whole job. she shows u the rules, she lets u tweak the variables, she slays. 👑

---

✨ SYNOPSIS ✨

pmieconf [-cFv?]  [-f file] [-r rulepath] [command [args...]]

---

🌸 DESCRIPTION 🌸

so pmieconf is a utility for viewing and configuring variables from generalized pmie(1) rules. the set of generalized rules gets read in from rulepath, and the output file that pmieconf produces is a valid input file for pmie. no cap, it just works like that. 🫶

---

💅 OPTIONS 💅

here's the command line options, bestie. all of them. i'm not skipping a single one, that's not the vibe:

• -c — when u run this from automated pmie setup processes, this option adds a specific message and timestamp saying "yep, this is that case." unless it gets over-ridden by the -f flag, the default configuration file to be written or updated when the -c flag is given and pmieconf is run by the root user is $PCP_VAR_DIR/config/pmie/config.default. this is also the default configuration file used by the pmie service, see pmie_daily(1). > heads up bestie: this flag is not appropriate when u use the tool interactively. 🙈
• -f file, --config=file — any rule modifications that come out of pmieconf messing with variable values will be written to file. the default value of file depends on the user ID — for the root user (when the -c flag is not also given, see above) the file is $PCP_SYSCONF_DIR/pmie/config.default. for other users the default is $HOME/.pcp/pmie/config.pmie. 💾
• -F, --force — forces the pmieconf output file to be created (or updated), and then pmieconf immediately exits. like, does the thing, leaves, iconic. 🚪💨
• -r rulepath, --rules=rulepath — lets u change the source of the generalized pmie rules. rulepath is a colon-delimited list of pmieconf(5) rule files and/or subdirectories. the default value for rulepath is $PCP_VAR_DIR/config/pmieconf. using this option overrides the PMIECONF_PATH environment variable, which does a similar thing. 🗂️
• -v, --verbose — enable verbose mode. associated variables will be displayed. this is the complete list of variables which affects any given rule (by default, global variables are not displayed with the rule). so like, verbose mode is the one that spills all the tea. 🍵
• -?, --help — display usage message and exit. classic. ✌️

the pmieconf commands let u display or modify info about the various rules and configurable variables. and if u don't hand it any pmieconf commands on the command line, pmieconf just prompts u for commands interactively. she's chatty like that. 💬

---

🎀 COMMAND LANGUAGE 🎀

here's the pmieconf command language, described for u:

• help [ { . | all | global | <rule> | <group> } [<variable>] ] — with no arguments, the help command displays the syntax for all of the available pmieconf commands. with one argument, a description of one or more of the generalized rules is displayed. with two arguments, a description of a specific variable relating to one or more of the generalized rules is displayed. 💡
• rules [ enabled | disabled ] — display the name and short summary for all of the generalized rules found on rulepath. each of the rule names can be used in place of the keyword <rule> in this command syntax description. the enabled and disabled options can be used to filter the set of rules displayed to just those which are enabled or disabled respectfully. 📋
• groups — display the name of all of the rule groups that were found on rulepath. each of the group names can be used in place of the keyword <group> in this command syntax description, which applies the command to all rules within the rule group. 👯
• status — display status information relating to the current pmieconf session, including a list of running pmie processes which are currently using file. 🩺
• enable { . | all | <rule> | <group> } — enables the specified rule or group of rules. an enabled rule is one which will be included in the pmie configuration file generated by pmieconf. any enabled "actions" will be appended to the rule's "predicate", in a manner conforming to the pmie syntax ("actions" can be viewed using the list global command, described below). ✨
• disable { . | all | <rule> | <group> } — disables the specified rule or group of rules. if the rule was previously enabled, it will be removed from the pmie configuration file generated by pmieconf, and hence no longer evaluated when pmie is restarted (using pmieconf does not affect any existing pmie processes using file). 🙅♀️
• list { . | all | global | <rule> | <group> } [<variable>] — display the values for a specific rule variable; or for all variables of a rule, a rule group, all rules, or the global variables. 👀
• modify { . | all | global | <rule> | <group> } <variable> <value> — enable, disable, or otherwise change the value for one or more rule variables. this value must be consistent with the type of the variable, which can be inferred from the format of the printed value — e.g. strings will be enclosed in double-quotes, percentages have the ``%'' symbol appended, etc. > note that certain rule variables cannot be modified through pmieconf — "predicate" and "help", for example. no touching those bestie. 🚫
• undo { . | all | global | <rule> | <group> } [<variable>] — applicable only to a variable whose value has been modified — this command simply reverts to the default value for the given variable. the "nvm bestie" of commands. ↩️
• quit — save any changes made to file and then exit pmieconf. 💾👋
• abort — exit pmieconf immediately without saving any changes to file. chaotic but valid. 💀

each of the commands above can be shortened by simply using the first character of the command name, and also ``?'' for help. 💅

use of the all keyword causes the command to be applied to all of the rules. the global keyword refers to those variables which are applied to every rule. such variables can be changed either globally or locally, for example:

pmieconf> modify global delta "5 minutes"
pmieconf> modify memory delta "1 minute"

this causes all rules to now be evaluated once every five minutes, except for rules in the "memory" group which are to be evaluated once per minute. literally the whole system on a schedule, obsessed. ⏰

the ``.'' character is special to pmieconf — it refers to the last successfully used value of all, global, <rule> or <group>. 🎯

---

🌈 EXAMPLES 🌈

specify that all of the rules in the "memory" group should be evaluated:

pmieconf> modify memory enabled yes

change your mind, and revert to using only the "memory" rules which were enabled by default:

pmieconf> undo memory enabled

specify that notification of rules which evaluate to true should be sent to syslogd(1):

pmieconf> modify global syslog_action yes

specify that rules in the "per_cpu" group should use a different holdoff value to other rules:

pmieconf> help global holdoff
  rule: global  [generic parameters applied to all rules]
   var: holdoff
  help: Once the predicate is true and the action is executed,
     this variable allows suppression of further action
     execution until the specified interval has elapsed.
     A value of zero enables execution of the action if
     the rule predicate is true at the next sample. Default
     units are seconds and common units are "second", "sec",
     "minute", "min" and "hour".

pmieconf> modify per_cpu holdoff "1 hour"

lower the threshold associated with a particular variable for a specified rule:

pmieconf> l cpu.syscall predicate
  rule: cpu.syscall  [High aggregate system call rate]
    predicate =
         some_host (
          ( kernel.all.syscall $hosts$ )
            > $threshold$ count/sec * hinv.ncpu $hosts$
         )

pmieconf> m . threshold 7000

pmieconf> l . threshold
  rule: cpu.syscall  [High aggregate system call rate]
       threshold = 7000

look at her go. main character energy fr. 🔥

---

🗂️ FILES 🗂️

• $PCP_VAR_DIR/config/pmieconf/*/* — generalized system resource monitoring rules
• $PCP_SYSCONF_DIR/pmie/config.pmie — default super-user settings for system resource monitoring rules
• $HOME/.pcp/pmie/config.pmie — default user settings for system resource monitoring rules

---

🌱 ENVIRONMENT 🌱

the environment variable PMIECONF_PATH has a similar function to the -r option described above, and if set will be used provided no -r option is presented. 🫶

---

💜 PCP ENVIRONMENT 💜

environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. on each installation, the file /etc/pcp.conf contains the local values for these variables. the $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). ⚙️

---

🫶 SEE ALSO 🫶

PCPIntro(1), pmie(1), pmie_check(1) and pmieconf(5).

---

and that's the whole page bestie, ty for coming to my ted talk 💖 this one came straight from the Performance Co-Pilot crew (PCP) — PMIECONF(1), the manual page. go configure ur rules, u got this. 🎀✨