Skip to main content
Tools & automation projects
Tools & automation

Magento Black Box

Bring technical evidence together to guide a Magento diagnosis.

I am developing a read-only Magento diagnostic tool for use on a Linux server or in Docker. It gathers observations about the application, PHP and services, then produces reports to guide performance investigations and compare two sets of records.

How the tool works

Input to analyse

Magento installation and technical environment

  1. Observe
  2. Diagnose
  3. Compare

Output

Technical report and investigation leads

My role
Design and development
Status
Tool in development
Technologies and scope
PythonMagento 2DiagnosisDockerPerformance
The need

Use observations to decide where to investigate further

Magento performance investigations span several layers: application, PHP, cache, indexing and services. Magento Black Box brings targeted observations into one report, with their sources and the points still to verify.

A diagnosis that goes beyond reading code

A performance issue may require examining resources, indexers, cron or declared services. The tool brings these clues together to prepare a more focused technical investigation.

A portable Python engine

I design the collection, interpretation rules and reports. The engine uses Python's standard library and can be distributed as an executable archive, with separate workflows for Linux and Docker.

The workflow

Define the scope, collect and interpret

  1. Choose useful observations

    Reading files provides an initial foundation. Additional probes can supplement the diagnosis according to the available access and the questions to investigate.

  2. Collect without starting Magento

    The engine reads selected information and queries services within the requested scope. It does not start the Magento application and retains the sources of its observations.

  3. Read alerts alongside their coverage

    Reports present observations, investigation leads and unverified checks. Comparing records then makes it possible to track changes across a comparable scope.

Features being developed

Several technical layers in one view

Application and deployment

The diagnosis brings together the Magento version, Composer metadata, declared configurations and selected deployment markers.

PHP, resources and services

Optional probes supplement collection with PHP versions, visible resources and explicitly declared SQL, Redis or search services.

Cron, indexing and background processing

Indexer states, cron scheduling samples and visible processes provide clues about background processing to investigate.

A targeted code review

An optional local analysis examines a sample of module and theme XML, PHP and PHTML files. It identifies declarations and constructs for manual review.

Design decisions

Readable evidence, even when the diagnosis is partial

Keep unknowns visible

Unavailable information or incomplete collection remains marked as unverified. Declared configuration and the state actually observed retain separate labels in the report.

Compare two diagnoses

JSON exports allow observations and coverage to be compared between two sets of records from the same environment. The report distinguishes changing alerts from evidence that has become unavailable.

The output

A diagnosis to review, share and compare

  • A text report for a quick review of alerts
  • A standalone HTML report with detailed evidence
  • A JSON record and a comparison of two diagnoses

In development

SEO audit toolkit

Turn SEO findings into an action plan tailored to the website.

PythonSEOAnalysis across different CMS platforms

In development

WordPress recovery toolkit

Structure the recovery of a hacked WordPress website, from analysis to relaunch.

PythonWordPressAutomation

Your project

Let's build the tool missing from your workflow.

Start with a concrete example: a repetitive task, a file or an analysis to produce. We will look at the available data and the expected result to define a custom tool.