For arlanix/product-feed 1.0
Support bundle
When something is wrong and the Run History does not explain it, support needs two things: the Arlanix log and a few facts about the installation. The support bundle collects both into one zip, in the admin, without SSH.
Where it is
Stores → Configuration → Arlanix → Support, group Diagnostics. The page lists what the bundle can hold, each with a checkbox, and a Download support bundle button.
What you can include
| Item | Ticked by default | What it adds |
|---|---|---|
| Arlanix log | yes | arlanix.log: the end of var/log/arlanix.log, up to the last 10 MB, cut at a line. If the file was larger, the first line of the entry says so and gives the full size. If there is no log file, the entry says that instead. |
| Magento and PHP | no | In environment.txt: the Magento edition, version and mode, the base URL of every store view, the default locale and timezone; the PHP version, memory limit, execution time limit, operating system and whether zip, curl, xmlwriter and mbstring are loaded. The limits are those of the PHP that built the bundle, php-fpm when downloaded from the admin; the cron runs the feeds under the command-line PHP, whose limits may differ, and the report says so. The limits each run actually had are in the run history, below. |
| Arlanix modules and versions | no | Every Arlanix_* module with its Composer package and version, enabled or disabled; the log level from env.php, and the size and last write of the log file. |
| Cron state | no | From cron_schedule: when any job last finished (whether the cron runs at all), when the Arlanix jobs last ran and finished, how many are pending and how the last 24 hours went. |
| Arlanix configuration (secrets masked) | no | Every stored arlanix* setting at every scope. A value whose path contains password, secret, token, key or credential is shown as ***. Merchant Center credentials and SFTP passwords are kept in their own tables and are never in the bundle. |
| Feed run history (last 7 days) | no | runs.jsonl: the runs of the last seven days, up to 500, newest first, one JSON object per line: the feed or store view, the stage and type, who triggered it, its status and counts, when it started and finished, its peak memory, and the PHP it ran under (version, cli or fpm, the php.ini it loaded, its memory and time limits). A run that failed, ended partial or got stuck also carries its warnings and errors, up to 50. The first line says how far back the file goes and how many of that window's runs it holds. |
Only the log is ticked when the page opens. Tick more to give support more to go on: the more the bundle holds, the sooner the cause is found. The choice is not saved anywhere; it is made each time you download. With nothing ticked the button is disabled.
The first lines of environment.txt say what was included and what was not, so support can see what is missing and ask for it.
Nothing leaves the store by itself
The bundle is a file your browser downloads to your computer, arlanix-support-<date>-<time>.zip. It is built in var/tmp and removed as soon as it has been sent. Nothing is uploaded or sent anywhere; you decide who gets the file.
Sending it to support
Write to support@arlanix.com with the zip attached, the feed identifier if a feed is concerned, and what you expected to happen. If the log is large, the zip is a few megabytes; it is fine to attach.