webalizer(1)

📦
version 2.23.08 · 3 versions
, in alpine 3.24, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

💖 webalizer(1) — The Webalizer 💖

ok so real talk, this is the manual page for webalizer from The Webalizer, and it is a lot — but we're gonna get through it together bestie, i promise. grab a snack 🍓

✨ NAME ✨

webalizer — a web server log file analysis tool. that's the whole vibe. 👑

🌸 SYNOPSIS 🌸

webalizer [ option ... ] [ log-file ]

webazolver [ option ... ] [ log-file ]

🦋 DESCRIPTION 🦋

okay so The Webalizer is this iconic web server log file analysis program that produces usage statistics in HTML format so you can look at them in a browser. she serves the results in both columnar and graphical format, which lowkey makes interpretation so much easier. stats are presented yearly, monthly, daily and hourly, and she also has the ability to display usage by site, URL, referrer, user agent (browser), username, search strings, entry/exit pages, and country — tho some info may not be available if it's not actually present in the log file being processed. not me reading your logs tho 🙈

She supports CLF (common log format) log files, plus Combined log formats as defined by NCSA and others, and variations of these which she attempts to handle intelligently (main character energy fr). On top of that, The Webalizer supports xferlog formatted (FTP) log files, squid proxy logs and W3C extended format logs. Logs may also be compressed, via gzip (.gz) or, if enabled at compile time, bzip2 (.bz2). If a compressed log file is detected, it will be automatically uncompressed while it is read. 💅 Compressed logs must have the standard gzip extension of .gz or bzip2 extension of .bz2 — no exceptions bestie.

webazolver is normally just a symbolic link to the Webalizer. When run as webazolver, only DNS file creation/updates are performed, and the program will exit once complete. All normal options and configuration directives are available, however many will not be used. In addition, a DNS cache file must be specified. If the number of DNS children processes to use are not specified, the webazolver will default to 5.

This documentation applies to The Webalizer Version 2.23 🎀

🌈 RUNNING THE WEBALIZER 🌈

The Webalizer was designed to be run from a Unix command line prompt or as a crond(8) job. Once executed, the general flow of the program is:

  • A default configuration file is scanned for. A file named webalizer.conf is searched for in the current directory, and if found, its configuration data is parsed. If the file is not present in the current directory, the file /etc/webalizer.conf is searched for and, if found, is used instead. 👀
  • Any command line arguments given to the program are parsed. This may include the specification of a configuration file, which is processed at the time it is encountered.
  • If a log file was specified, it is opened and made ready for processing. If no log file was given, STDIN is used for input. If the log filename - is specified, STDIN will be forced.
  • If an output directory was specified, the program does a chdir(2) to that directory in preparation for generating output. If no output directory was given, the current directory is used.
  • If a non-zero number of DNS Children processes were specified, they will be started, and the specified log file will be processed, creating or updating the specified DNS cache file.
  • If no hostname was given, the program attempts to get the hostname using a uname(2) system call. If that fails, localhost is used. iconic fallback tbh.
  • A history file is searched for in the current directory (output directory) and read if found. This file keeps totals for previous months, which is used in the main index.html HTML document. Note: The file location can now be specified with the HistoryName configuration option.
  • If incremental processing was specified, a data file is searched for and loaded if found, containing the 'internal state' data of the program at the end of a previous run. Note: The file location can now be specified with the IncrementalName configuration option.
  • Main processing begins on the log file. If the log spans multiple months, a separate HTML document is created for each month. 🗓️
  • After main processing, the main index.html page is created, which has totals by month and links to each month's HTML document.
  • A new history file is saved to disk, which includes totals generated by The Webalizer during the current run.
  • If incremental processing was specified, a data file is written that contains the 'internal state' data at the end of this run.

⭐ INCREMENTAL PROCESSING ⭐

The Webalizer supports incremental run capability. Simply put, this allows processing large log files by breaking them up into smaller pieces, and processing these pieces instead. What this means in real terms is that you can now rotate your log files as often as you want, and still be able to produce monthly usage statistics without the loss of any detail — she ate fr fr. 💅

Basically, The Webalizer saves and restores all internal data in a file named webalizer.current. This allows the program to 'start where it left off' so to speak, and allows the preservation of detail from one run to the next. The data file is placed in the current output directory, and is a plain ASCII text file that can be viewed with any standard text editor. Its location and name may be changed using the IncrementalName configuration keyword.

⚠️ Some special precautions need to be taken when using the incremental run capability of The Webalizer. Configuration options should not be changed between runs, as that could cause corruption of the internal data stored. For example, changing the MangleAgents level will cause different representations of user agents to be stored, producing invalid results in the user agents section of the report. If you need to change configuration options, do it at the end of the month after normal processing of the previous month and before processing the current month. You may also want to delete the webalizer.current file as well. 😭

The Webalizer also attempts to prevent data duplication by keeping track of the timestamp of the last record processed. This timestamp is then compared to current records being processed, and any records that were logged previous to that timestamp are ignored. This, in theory, should allow you to re-process logs that have already been processed, or process logs that contain a mix of processed/not yet processed records, and not produce duplication of statistics. The only time this may break is if you have duplicate timestamps in two separate log files… any records in the second log file that do have the same timestamp as the last record in the previous log file processed, will be discarded as if they had already been processed. 💀 There are lots of ways to prevent this however — for example, stopping the web server before rotating logs will prevent this situation. This setup also necessitates that you always process logs in chronological order, otherwise data loss will occur as a result of the timestamp compare. no cap, order matters.

🧚 REVERSE DNS LOOKUPS 🧚

The Webalizer fully supports IPv4 and IPv6 DNS lookups, and maintains a cache of those lookups to reduce processing the same addresses in subsequent runs. The cache file can be created at run-time, or may be created before running the webalizer using either the stand alone webazolver program, or The Webalizer (DNS) Cache file manager program wcmgr. In order to perform reverse lookups, a DNSCache file must be specified, either on the command line or in a configuration file.

In order to create/update the cache file at run-time, the number of DNSChildren must also be specified, and can be anything between 1 and 100. This specifies the number of child processes to be forked, each of which will perform network DNS queries in order to look up the addresses and update the cache.

Cached entries that are older than a specified TTL (time to live) will be expired, and if encountered again in a log, will be looked up at that time in order to 'freshen' them (verify the name is still the same and update its timestamp). The default TTL is 7 days, however may be set to anything between 1 and 100 days. Using the wcmgr program, entries may also be marked as 'permanent', in which case they will persist (with an infinite TTL) in the cache until manually removed. See the file DNS.README for additional information and examples. 🫶

🔥 GEOLOCATION LOOKUPS 🔥

The Webalizer has the ability to perform geolocation lookups on IP addresses using either its own internal GeoDB database, or optionally the GeoIP database from MaxMind, Inc. (www.maxmind.com). If used, unresolved addresses will be searched for in the database and its country of origin will be returned if found.

This actually produces more accurate Country information than DNS lookups, since the DNS address space has additional gcTLDs that do not necessarily map to a specific country (such as .net and .com). It is possible to use both DNS lookups and geolocation lookups at the same time, which will cause any addresses that could not be resolved using DNS lookups to then be looked up in the database, greatly reducing the number of Unknown/Unresolved entries in the generated reports. ✨

The native GeoDB geolocation database provided by The Webalizer fully supports both IPv4 and IPv6 lookups, is updated regularly and is the preferred geolocation method for use with The Webalizer. The most current version of the database can be obtained from our ftp site (ftp://ftp.mrunix.net/). 🦋

💅 COMMAND LINE OPTIONS 💅

okay so The Webalizer has so many knobs and switches, bestie — like, it can change how it behaves and what it spits out, and most of these can be set right on the command line. Some are config-file-only tho, so read the fine print. Below are the command line options, with shoutouts to the matching configuration file keywords. 👑

🌸 General Options 🌸

  • -h — shows every available command line option and then dips. help me help you energy.
  • -v — be verbose. makes the program output informational and Debug messages while it's running.
  • -V — shows the program version and exits. if you also use verbose mode (like -vV), you get extra program-specific info too — super useful when you're sending in bug reports.
  • -d — Debug. shows debugging information for errors and warnings.
  • -i — IgnoreHist. ignores history. USE WITH CAUTION. this makes The Webalizer ignore any previous monthly history file only. incremental data (if present) is still processed.
  • -b — IgnoreState. ignores the incremental data file. USE WITH CAUTION. by ignoring the incremental data file, all previous processing for the current month will be lost and those logs must be re-processed.
  • -p — Incremental. preserves internal data between runs.
  • -q — Quiet. suppresses informational messages. does not suppress warnings or errors.
  • -Q — ReallyQuiet. suppresses all messages including warnings and errors.
  • -T — TimeMe. forces display of timing information at the end of processing.
  • -c file — use configuration file file.
  • -n name — HostName. use the hostname name.
  • -o dir — OutputDir. use output directory dir.
  • -t name — ReportTitle. use name for the report title.
  • -F ( clf | ftp | squid | w3c ) — LogType. specify the log type to process. value can be either clf, ftp, squid or w3c format. if not specified, it defaults to CLF format. FTP logs must be in standard wu-ftpd xferlog format.
  • -f — FoldSeqErr. folds out-of-sequence log records back into analysis by treating them as if they were the same date/time as the last good record. normally, out-of-sequence log records are simply ignored.
  • -Y — CountryGraph. suppress country graph.
  • -G — HourlyGraph. suppress hourly graph.
  • -x name — HTMLExtension. defines the HTML file extension to use. if not specified, defaults to html. do not include the leading period.
  • -H — HourlyStats. suppress hourly statistics.
  • -K num — IndexMonths. specify how many months should be displayed in the main index (yearly summary) table. default is 12 months. can be set to anything between 12 and 120 months (1 to 10 years).
  • -k num — GraphMonths. specify how many months should be displayed in the main index (yearly summary) graph. default is 12 months. can be set to anything between 12 and 72 months (1 to 6 years).
  • -L — GraphLegend. suppress color coded graph legends.
  • -l num — GraphLines. specify number of background lines. default is 2. use zero (0) to disable the lines.
  • -P name — PageType. specify file extensions that are considered pages. sometimes referred to as pageviews.
  • -O name — OmitPage. specify URLs to exclude from being counted as pages.
  • -m num — VisitTimeout. specify the Visit timeout period. specified in number of seconds. default is 1800 seconds (30 minutes).
  • -I name — IndexAlias. use the filename name as an additional alias for index.
  • -M num — MangleAgents. mangle user agent names according to the mangle level specified by num. mangle levels are:
    • 5 — Browser name and major version.
    • 4 — Browser name, major and minor version.
    • 3 — Browser name, major version, minor version to two decimal places.
    • 2 — Browser name, major and minor versions and sub-version.
    • 1 — Browser name, version and machine type if possible.
    • 0 — All information (left unchanged).
  • -g num — GroupDomains. automatically group sites by domain. the grouping level specified by num can be thought of as "the number of dots" to display in the grouping. the default value of 0 disables any domain grouping.
  • -D name — DNSCache. use the DNS cache file name.
  • -N num — DNSChildren. use num DNS children processes to perform DNS lookups, either creating or updating the DNS cache file. specify zero (0) to disable cache file creation/updates. if given, a DNS cache filename must be specified.
  • -j — Enable GeoDB. this enables the internal GeoDB geolocation services provided by The Webalizer.
  • -J name — GeoDBDatabase. use the alternate GeoDB database name name.
  • -w — Enable GeoIP. enables GeoIP (by MaxMind Inc.) geolocation services. if native GeoDB services are also enabled, then this option will have no effect.
  • -W name — GeoIPDatabase. use the alternate GeoIP database name name.
  • -z name — FlagDir. specify location of the country flag graphics and enable their display in the top country table. the directory name is relative to the output directory being used unless an absolute path is given (ie: starts with a leading /).

🙈 Hide Options 🙈

  • -a name — HideAgent. hide user agents matching name.
  • -r name — HideReferrer. hide referrer matching name.
  • -s name — HideSite. hide site matching name.
  • -X — HideAllSites. hide all individual sites (only display groups).
  • -u name — HideURL. hide URL matching name.

📊 Table size options 📊

  • -A num — TopAgents. display the top num user agents table.
  • -R num — TopReferrers. display the top num referrers table.
  • -S num — TopSites. display the top num sites table.
  • -U num — TopURLs. display the top num URLs table.
  • -C num — TopCountries. display the top num countries table.
  • -e num — TopEntry. display the top num entry pages table.
  • -E num — TopExit. display the top num exit pages table.

📝 CONFIGURATION FILES 📝

configuration files are standard ASCII(7) text files that you can create or edit with any standard editor. blank lines and lines that begin with a pound sign (#) are ignored. any other lines are considered configuration lines, and they have the form "Keyword Value", where the Keyword is one of the currently available configuration keywords defined below, and Value is the value to assign to that particular option. any text found after the keyword up to the end of the line is considered the keyword's value, so you should not include anything after the actual value on the line that isn't actually part of the value being assigned. the sample.conf file provided with the distribution contains lots of useful documentation and examples as well. 🫶

🌈 General Configuration Keywords 🌈

LogFile name

use log file named name. if none specified, STDIN will be used.

LogType name

specify log file type as name. values can be either clf, squid, ftp or w3c, with the default being clf.

OutputDir dir

create output in the directory dir. if none specified, the current directory will be used.

HistoryName name

filename to use for the history file. relative to the output directory unless an absolute name is given (ie: starts with /). defaults to webalizer.hist in the standard output directory.

ReportTitle name

use the title string name for the report title. if none specified, use the default of (in english) "Usage Statistics for ".

HostName name

set the hostname for the report as name. if none specified, an attempt will be made to gather the hostname via a uname(2) system call. if that fails, localhost will be used.

UseHTTPS ( yes | no )

use https:// on links to URLS, instead of the default http://, in the 'Top URLs' table.

HTAccess ( yes | no )

enables the creation of a default .htaccess file in the output directory.

Quiet ( yes | no )

suppress informational messages. warning and error messages will not be suppressed.

ReallyQuiet ( yes | no )

suppress all messages, including warning and error messages.

Debug ( yes | no )

print extra debugging information on warnings and errors.

TimeMe ( yes | no )

force timing information at the end of processing.

GMTTime ( yes | no )

use GMT (UTC) time instead of local timezone for reports.

IgnoreHist ( yes | no )

ignore previous monthly history file. USE WITH CAUTION. does not prevent incremental file processing.

IgnoreState ( yes | no )

ignore incremental data file. USE WITH CAUTION. by ignoring the incremental data file, all previous processing for the current month will be lost and those logs must be re-processed.

FoldSeqErr ( yes | no )

fold out-of-sequence log records back into analysis by treating them as if they had the same date/time as the last good record. normally, out-of-sequence log records are ignored.

CountryGraph ( yes | no )

display Country Usage Graph in output report.

CountryFlags ( yes | no )

enable or disable the display of flags in the top country table.

FlagDir name

specifies the directory name where the flag graphics are located. if not specified, the default is in the flags directory directly under the output directory being used. if specified, the display of country flags will be enabled by default. using 'FlagDir flags' is identical to using 'CountryFlags yes'.

DailyGraph ( yes | no )

display Daily Graph in output report.

DailyStats ( yes | no )

display Daily Statistics in output report.

HourlyGraph ( yes | no )

display Hourly Graph in output report.

HourlyStats ( yes | no )

display Hourly Statistics in output report.

PageType name

define the file extensions to consider as a page. if a file is found to have the same extension as name, it will be counted as a page (sometimes called a pageview).

PagePrefix name

allows URLs with the prefix name to be counted as a page type regardless of actual file type. this allows you to treat contents under specified directories as pages no matter what their extension is.

  • OmitPage name — for URLs you straight up do not want counted as pages, no matter what extension they have (or don't have, we're not judging). drop the name and it's gone from the page count, periodt.
  • GraphLegend ( yes | no ) — turns the color coded graph legends on or off. cute little key for your graphs, or hide it if you're being minimal 💅
  • GraphLines num — how many background reference lines show up on the graphs you produce. set it to zero (0) to disable them entirely. default is 2. ✨
  • IndexMonths num — how many months get shown in the main index (yearly summary) table. default is 12 months, and you can set it anywhere between 12 and 120 months (that's 1 to 10 years, bestie, so plan accordingly 😭).
  • YearHeaders ( yes | no ) — enables or disables year headers in the main index (yearly summary) table. if it's enabled, year headers show when the table is displaying more than 16 months worth of data. values are 'yes' or 'no', default is 'yes'. 🎀
  • YearTotals ( yes | no ) — same vibe, but for year totals in the main index (yearly summary) table. if enabled, year totals show when the table is displaying more than 16 months worth of data. values are 'yes' or 'no', default is 'yes'. 👑
  • GraphMonths num — how many months show up in the main index (yearly summary) graph. default is 12 months, and it can be anything between 12 and 72 months (1 to 6 years). lowkey a different range than IndexMonths, don't mix them up fr fr 🫶
  • VisitTimeout num — the visit timeout value, in seconds. default is 1800 seconds (that's 30 minutes). here's the tea: a visit is figured out by looking at the time difference between the current request and the last request from one specific site. if that difference is greater than or equal to the timeout value, the request counts as a new visit. ⭐
  • IndexAlias name — uses name as an extra alias for index.*. stacking aliases like it's a fit check 🌸
  • DefaultIndex ( yes | no ) — enables or disables using 'index.' as a default index name that gets stripped off the end of URLs. important caveat: this does not effect any index names that might be defined with the IndexAlias option. nope, those are separate 💖
  • MangleAgents num — mangles user agent names based on mangle level num. the -M command line switch has the mangle levels and what they mean, go look there iykyk. default is 0, which doesn't mangle user agents at all (they stay exactly as they are, we respect them). 🦋
  • StripCGI ( yes | no ) — decides whether URL CGI variables get stripped from the end of URLs. values can be 'yes' or 'no', and the default is 'yes'. 🧹
  • TrimSquidURL num — lets squid log URLs get reduced in granularity by truncating them after num slashes ('/') that come after the http:// prefix. a setting of one (1) will cause all URLs to be summarized by domain only. the default value is zero (0), which disables any URL modifications and leaves them exactly as found in the log file. not me touching nothing 🙈
  • SearchEngine name variable — lets you specify search engines plus their query strings. name is what gets matched against the referrer string for a given search engine, and variable is the cgi variable that the search engine uses for queries. peep the sample.conf file for example usage with common search engines — it's giving reference material, use it 💅
  • SearchCaseI ( yes | no ) — decides whether search strings are treated case insensitive or not. default is 'yes', which lowercases all search strings (treat as case insensitive). ✨
  • Incremental ( yes | no ) — enables Incremental mode processing. the whole incremental arc, we love to see it 🔥
  • IncrementalName name — the filename to use for incremental data. it's relative to the output directory unless you give an absolute name (ie: starts with '/'). defaults to webalizer.current in the standard output directory. 🎀
  • DNSCache name — filename to use for the DNS cache. relative to the output directory unless an absolute name is given (ie: starts with '/'). 🦋
  • DNSChildren num — how many children DNS processes to run in order to create/update the DNS cache file. specify zero (0) to disable. little worker bees 🐝
  • CacheIPs ( yes | no ) — caches unresolved IP addresses in the DNS database. default is 'no'. ⭐
  • CacheTTL num — DNS cache entry time to live (TTL), counted in days. default is 7 days, and it may be any value between 1 and 100. 👑
  • GeoDB ( yes | no ) — lets native GeoDB geolocation services be enabled or disabled. default value is 'no'. 🌈
  • GeoDBDatabase name — lets you use an alternate GeoDB database name. if you don't specify one, the default database gets used. 🫶
  • GeoIP ( yes | no ) — lets GeoIP (by MaxMind Inc.) geolocation services be enabled or disabled. default is 'no'. heads up though: if native GeoDB geolocation services are also enabled, then this option has no effect (and the native GeoDB services get used instead). GeoDB wins the fight, no cap 💀
  • GeoIPDatabase name — lets you use an alternate GeoIP database name. if not specified, the default database will be used. 🌸

👑 Top Table Keywords 👑

  • TopAgents num — displays the top num User Agents table. use zero to disable. 🎀
  • AllAgents ( yes | no ) — creates a whole separate HTML page with All User Agents. the full roster, we're obsessed ✨
  • TopReferrers num — displays the top num Referrers table. use zero to disable. 💅
  • AllReferrers ( yes | no ) — creates a separate HTML page with All Referrers. 🦋
  • TopSites num — displays the top num Sites table. use zero to disable. 🌟
  • TopKSites num — displays the top num Sites (by KByte) table. use zero to disable. kilobytes said what now 📊
  • AllSites ( yes | no ) — creates a separate HTML page with All Sites. 🌈
  • TopURLs num — displays the top num URLs table. use zero to disable. 🔗
  • TopKURLs num — displays the top num URLs (by KByte) table. use zero to disable. 💜
  • AllURLs ( yes | no ) — creates a separate HTML page with All URLs. ✨
  • TopCountries num — displays the top num Countries in the table. use zero to disable. 🌍
  • TopEntry num — displays the top num Entry Pages in the table. use zero to disable. the main character pages, literally 🚪
  • TopExit num — displays the top num Exit Pages in the table. use zero to disable. the goodbye girls 🚪💨
  • TopSearch num — displays the top num Search Strings in the table. use zero to disable. 🔍
  • AllSearchStr ( yes | no ) — creates a separate HTML page with All Search Strings. 🎀
  • TopUsers num — displays the top num Usernames in the table. use zero to disable. but note: Usernames are only available if you're using http based authentication. no auth, no names, that's just how it is 😭
  • AllUsers ( yes | no ) — creates a separate HTML page with All Usernames. 🫶

🙈 Hide/Ignore/Group/Include Keywords 🙈

  • HideAgent name — hides User Agents that match name. 🫣
  • HideReferrer name — hides Referrers that match name. 🫣
  • HideSite name — hides Sites that match name. 🫣
  • HideAllSites ( yes | no ) — hides all individual sites. this causes only grouped sites to be displayed. we're keeping it anonymous bestie 🙈
  • HideURL name — hides URLs that match name. 🫣
  • HideUser name — hides Usernames that match name. 🫣
  • IgnoreAgent name — ignores User Agents that match name. 🚫
  • IgnoreReferrer name — ignores Referrers that match name. 🚫
  • IgnoreSite name — ignores Sites that match name. 🚫
  • IgnoreURL name — ignores URLs that match name. 🚫
  • IgnoreUser name — ignores Usernames that match name. 🚫
  • GroupAgent name [Label] — groups User Agents that match name. if Label is given, it gets displayed in the 'Top Agent' table (instead of name). and name may be enclosed in quotes. 🌸
  • GroupReferrer name [Label] — groups Referrers that match name. if Label is given, it gets displayed in the 'Top Referrer' table (instead of name). name may be enclosed in quotes. 🌸
  • GroupSite name [Label] — groups Sites that match name. if Label is given, it gets displayed in the 'Top Site' table (instead of name). name may be enclosed in quotes. 🌸
  • GroupDomains num — automatically groups sites by domain. the value num specifies the level of grouping, and honestly you can think of it as the 'number of dots' to be displayed. the default value of 0 disables domain grouping. 🎀
  • GroupURL name [Label] — groups URLs that match name. if Label is given, it gets displayed in the 'Top URL' table (instead of name). name may be enclosed in quotes. 🌸
  • GroupUser name [Label] — groups Usernames that match name. if Label is given, it gets displayed in the 'Top Usernames' table (instead of name). name may be enclosed in quotes. 🌸
  • IncludeSite name — forces inclusion of sites that match name. this takes precedence over the Ignore* keywords. so yes, it overrules them, it's giving main character energy 👑🔥
  • IncludeURL name — forces inclusion of URLs that match name. takes precedence over the Ignore* keywords. ✨
  • IncludeReferrer name — forces inclusion of Referrers that match name. takes precedence over the Ignore* keywords. ✨
  • IncludeAgent name — forces inclusion of User Agents that match name. takes precedence over the Ignore* keywords. ✨
  • IncludeUser name — forces inclusion of Usernames that match name. takes precedence over the Ignore* keywords. ✨

🎀 HTML Generation Keywords 🎀

  • HTMLExtension text — defines the HTML file extension to use. default is html. and please, do not include the leading period! 🚫✨
  • HTMLPre text — inserts text at the very beginning of the generated HTML file. defaults to a standard html 3.2 DOCTYPE record. the opening act, literally 🎬
  • HTMLHead text — inserts text within the <HEAD></HEAD> block of the HTML file. 💅
  • HTMLBody text — inserts text in the HTML page, starting with the <BODY> tag. if you use it, the first line must be a <BODY ...> tag. multiple lines may be specified. ⚠️
  • HTMLPost text — inserts text at the top (before the horiz. rule) of HTML pages. multiple lines may be specified. 🫶
  • HTMLTail text — inserts text at the bottom of the HTML page. the text is top and right aligned within a table column at the end of the report. the little sign-off, so cute 🌸
  • HTMLEnd text — inserts text at the very end of the HTML page. if not specified, the default is to insert the ending </BODY> and </HTML> tags. but if you do use it, then you have to supply these tags yourself. no cap, it's on you then 😭
  • LinkReferrer ( yes | no ) — determines whether the referrers listed in the top referrers table get displayed as plain text, or as a link to the referrer URL. 🔗
  • ColorHit ( rrggbb | 00805c ) — sets the graph's hit-color to the specified html color (no '#' in there!). 🎨
  • ColorFile (rrggbb | 0040ff) — sets the graph's file-color to whatever html color you drop in here (and pls, no # bestie 💅).
  • ColorSite (rrggbb | ff8000) — sets the graph's site-color to the html color you pick (again, no #).
  • ColorKbyte (rrggbb | ff0000) — sets the graph's kilobyte-color to your html color of choice (no #, you know the drill).
  • ColorPage (rrggbb | 00e0ff) — sets the graph's page-color to the specified html color (no #).
  • ColorVisit (rrggbb | ffff00) — sets the graph's visit-color to the specified html color (no #).
  • ColorMisc (rrggbb | 00e0ff) — sets the 'miscellaneous' color for table headers (not graphs, okay?) to the specified html color (no #).
  • PieColor1 (rrggbb | 800080) — sets the pie's first optional color to the specified html color (no #).
  • PieColor2 (rrggbb | 80ffc0) — sets the pie's second optional color to the specified html color (no #).
  • PieColor3 (rrggbb | ff00ff) — sets the pie's third optional color to the specified html color (no #).
  • PieColor4 (rrggbb | ffc480) — sets the pie's fourth optional color to the specified html color (no #).

🗂️ Dump Object Keywords

The Webalizer lets you export processed data to other programs by using tab delimited text files, which is lowkey iconic of it. The Dump* commands specify which files are to be written, and where they go. Slay. ✨

  • DumpPath name — save dump files in directory name. If you don't specify it, the default output directory gets used. Do not put a trailing slash (/) at the end, bestie — just don't. 🙈
  • DumpExtension name — use name as the filename extension for dump files. If you don't give one, the default of tab will be used.
  • DumpHeader (yes | no) — print a column header as the first record of the file.
  • DumpSites (yes | no) — dump the sites data to a tab delimited file.
  • DumpURLs (yes | no) — dump the url data to a tab delimited file.
  • DumpReferrers (yes | no) — dump the referrer data to a tab delimited file. Heads up: this data is only available if you're using a log that contains referrer information (ie: a combined format web log). No referrer info in, no referrer dump out, iykyk.
  • DumpAgents (yes | no) — dump the user agent data to a tab delimited file. Same deal: this data is only available if you're using a log that contains user agent information (ie: a combined format web log).
  • DumpUsers (yes | no) — dump the username data to a tab delimited file. This one is only available if you're processing a wu-ftpd xferlog or a web log that contains http authentication information.
  • DumpSearchStr (yes | no) — dump the search string data to a tab delimited file. And yeah, this data is only available if you're processing a web log that contains referrer information and had search string information present. Very "only if the vibes align" of it tbh.

📁 FILES

  • webalizer.conf — the default configuration file. It gets searched for in the current directory, and if it's not found there, it looks in the /etc/ directory. She's thorough. 💅
  • webalizer.hist — the monthly history file for previous months. (this can be changed!)
  • webalizer.current — the current state data file (for Incremental processing). (this can be changed too 🫶)
  • xxxxx_YYYYMM.html — the various monthly HTML output files that get produced. (the extension can be changed)
  • xxxxx_YYYYMM.png — the various monthly image files used in the reports.
  • xxxxx_YYYYMM.tab — the monthly tab delimited text files. (extension can be changed, yes ma'am)

💀 BUGS

Please report bugs to the author. That's it, that's the whole section. Don't be shy about it — they wanna know. 🐛

Copyright (C) 1997-2013 by Bradford L. Barrett. Distributed under the GNU GPL. See the files "COPYING" and "Copyright", supplied with all distributions, for additional information. Read the fine print bestie, it's giving responsible queen behavior. 👑

👑 AUTHOR

Bradford L. Barrett <brad at mrunix dot net>

That's the whole page, bestie — you made it to the end! 🎀 This was Version 2.23, dated 26-Feb-2013, and you've officially consumed the entire webalizer(1) manual page. No cap, that's a flex. Go make some iconic graphs now. 💖✨🌸

📦 where this page comes from