WEBPINGVIS(1)

✨ webpingvis — the manual, but make it cute ✨

okay so bestie, this is webpingvis(1) from the General Commands Manual and it is literally the vibe check your Web server has been begging for. sit down, grab a boba, we're gonna visualize some response times 💅

---

🎀 NAME 🎀

webpingvis — visualize Web server response time ✨

like. that's it. that's the whole job. it makes your Web server's response time go from "numbers in a terminal" to "bars on a screen" and honestly? iconic.

---

🌸 SYNOPSIS 🌸

webpingvis [-CiVz] [-A align] [-a archive] [-h host] [-m max] [-n
pmnsfile] [-O time] [-p port] [-S time] [-T time] [-t interval] [-x
version] [-Z timezone]

look at all those flags bestie, it's giving options buffet 🍓 don't worry, most of them get passed straight to pmview(1) and we'll go through every single one, no cap.

---

🦋 DESCRIPTION 🦋

webpingvis displays a summary of Web server response-time statistics collected from the Performance Co-Pilot (PCP) infrastructure. 💖 The display is modulated by the values of performance metrics retrieved from the target host — and that target host is running pmcd(1) and the pmdawebping(1) Performance Metrics Domain Agent — or, alternatively, from the PCP archive log identified by archive. The display is updated every interval seconds, and the default for that is 2 seconds. ⏱️

As in all pmview(1) scenes (yes queen, this is a pmview scene), when the mouse is moved over one of the bars, the current value and metric information for that bar will be shown in the text box near the top of the display. 🖱️✨ The height of the bars is proportional to the performance metric values relative to the maximum, as controlled by size of the URLs being fetched by pmdawebping(1), and the -m option (scroll down, it's there, i promise 🫶).

The bars in the webpingvis scene represent the following information:

🟢 Size

The green bars indicate the relative sizes of the results returned for each URL in the pmdawebping workload.

💜 Response

For each URL in the pmdawebping workload, the components of the Web server response-time (connect, head and body) and the total response-time is displayed.

To the right, the component and total times are summed over all URLs in the pmdawebping workload. math girlies rise 🙌

🔴 Errors

The four red error bars indicate the number of socket, HTTP, HTML or other errors that occurred in the last iteration of the pmdawebping workload. Any of these errors will terminate the request for a URL. 💀

---

webpingvis uses pmview(1), and so the user interface follows that described for pmview(1), which in turn displays the scene within an Inventor examiner viewer. For generic control of the viewer, see ivview(1).

webpingvis passes most command line options to pmview(1). Therefore, the command line options -A, -a, -C, -h, -n, -O, -p, -S, -t, -T, -x, -Z and -z, and the user interface are described in the pmview(1) man page. (go read it, it's a whole thing 📖)

Options specific to webpingvis are:

• -i — The URL names are not included as labels in the scene by default. The -i option forces them to be included. so basically, -i is the "not me forcing the labels to show up" flag 🙈
• -m max — Change the normalization factor for the response-time bars. The value for max is in units of milliseconds, and should be the expected maximum value for the total response-time aggregated over all URLs in the pmdawebping workload. The default value is 1000 milliseconds. ⭐
• -V — The derived configuration file for pmview(1) is written on standard output. This may be saved and used directly with pmview(1) if the user wishes to customize the display, or modify some of the normalization parameters. main character energy: save it, tweak it, make it yours 💅

---

😭 CAVEATS 😭

bestie. listen. these are the real ones, no cap.

As webpingvis sorts the configured URLs by size, running webpingvis shortly after starting pmdawebping(1) may result in the URLs being sorted incorrectly as they may not have been fetched. like, it's not lying to you, it just hasn't finished waking up yet 🥱

The ~ character may not be parsed correctly by pmview(1). Therefore, if pmdawebping(1) is fetching any URLs containing ~ then webpingvis will not launch. 💀 fr fr, it's just not gonna start.

---

🧚 FILES 🧚

• $PCP_VAR_DIR/pmns/* — default PMNS specification files
• $PCP_VAR_DIR/config/pmlogger/config.webpingvis — pmlogger(1) configuration file that can be used to create a PCP archive suitable for display with webpingvis
• $PCP_VAR_DIR/config/pmchart/Web.Response — A pmchart(1) configuration file for monitoring Web server response time

---

🌈 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(4). it's giving "configuration inception" but make it organized 🫶

---

👑 SEE ALSO 👑

pmcd(1), pmchart(1), pmdawebping(1), pmdumplog(1), pminfo(1), pmlogger(1), pmval(1), pmview(1), weblogvis(1) and webvis(1).

go forth and read, bestie, the whole squad is linked 💖

---

this page came to you courtesy of Performance Co-Pilot, and yes the manual name really is WEBPINGVIS(1) — slay, periodt. 💅✨