Status Panel

The status panel answers one question quickly: is anything about this installation in a state I should know about?

Where to find it

Architect Panel → Activity:

• Error Log — what has actually gone wrong
• Activity Log — what has been done, and by whom

Architect Panel → Configuration:

• Site Settings — where configuration the panel comments on is changed

What it reports

• Component versions — the web server, PHP and database server, with advice when an upgrade is worth taking.
• Benchmarking — a measure of how the underlying infrastructure is actually performing.
• Configuration advice — where performance is available from a configuration change rather than more hardware.

Versions are a security matter, not only a features one

The most common reason a platform version notice matters is not a missing feature — it is that the version you are running has since had security fixes. Treat a version notice as something to schedule rather than something to dismiss, even when everything is working.

Benchmark when nothing is wrong

A benchmark taken during an incident tells you the system is slow, which you already knew. A benchmark taken on an ordinary Tuesday gives you the baseline that makes the incident measurement meaningful.

Take one after go-live, and again after any infrastructure change. Two numbers three months apart will tell you more about a gradual degradation than any amount of investigation once users start complaining.

Configuration advice is worth acting on

Where the panel reports that a setting is limiting performance, that is usually a cheap fix — a memory limit, a cache setting, a connection pool. It is worth doing before concluding that the application needs a larger server.

Make it a routine

The panel's value is in the trend, not the snapshot. Look at it monthly when nothing is wrong, and you will notice the version that slipped two releases behind and the benchmark that has drifted. Look at it only during incidents and it becomes a screen you interpret under pressure with no baseline.

Where it fits with the logs

The status panel says whether the platform is healthy. The Error Log says what has gone wrong, and the Activity Log says what people have done. A problem investigation usually starts here and moves to those.

Worked example

A monthly check finds the benchmark 20% slower than the previous month and a note that a database configuration change would help. The change is applied during the next maintenance window, the benchmark returns to its earlier figure, and nobody ever raises a ticket — because the degradation was caught before it reached the point users noticed.

Recommendations

• Check it monthly, not only during incidents.
• Record a benchmark at go-live as your baseline.
• Treat version notices as security work.
• Apply configuration advice before buying hardware.