Easier to read with cream paper, a tint, more contrast or larger text? Choose your colours and text, once, for every page.

Preview

DS 2.23: Monitoring systems, security and traffic

This is the first page of the lesson. Read it and have a go at the activities. The rest is in the full lesson.

60 minutes

"It is slow every Monday at nine"

Staff say the system crawls every Monday at nine. By the time a technician looks, it is fine again.

Without records, there is nothing to look at. A technician who monitors can see the Monday rush and say what caused it.

Key words

WordWhat it means
Monitoringwatching a system over time and recording how it behaves
Performancehow fast and how well a system does its work
Loadhow busy a computer is
Trafficthe data moving along a link
Networkcomputers joined together so they can share data
Firewalla barrier that blocks unwanted traffic
Baselinethe normal readings, to compare new ones against
Security controla tool or rule that protects a system, such as a password rule
Bottlenecka part that holds everything else back
Databasean organised store of records you can search

The cells students fill in are left blank in this preview.

By the end of this lesson

Note

I can say what to monitor in hardware, software, database, network and people, and read some basic readings.

Starter

Have a go

Starter

3 questions
Have a go: your answers are marked here and then forgotten. Sign in if you would like your score kept, and to pick up where you left off.Sign in to keep your score

Your answers are marked here and are not kept. A college account keeps every student’s marks.

Five things to analyse

A system is more than its computers. A technician looks at five parts.

Hardware: is the processor, memory or disk full or too hot? Software: do programs crash or show errors? Database: are searches slow, or is it nearly full? Network: is the link slow or dropping data? People: are users stuck, untrained or making the same mistake?

What to watch in each part

PartSigns of troubleExample reading
HardwareHigh load, full disk, high heatLoad above the number of cores
SoftwareCrashes, error messages, slow startSame error logged all day
DatabaseSlow searches, almost fullA report takes minutes
NetworkSlow, dropped data, a very busy linkA link at its limit
PeopleMany tickets on one thing; repeat mistakesTen tickets about one program

The cells students fill in are left blank in this preview.

How busy is the machine?

Command
uptime

A command for the lesson’s lab terminal. It is shown here and not run.

How much memory is used?

Command
free -m | head -2

A command for the lesson’s lab terminal. It is shown here and not run.

How full is the disk?

Command
df -h / | tail -1

A command for the lesson’s lab terminal. It is shown here and not run.

The lesson goes on

10 more parts of this lesson are in the full curriculum, with the tasks, the final check and the labs. A college account gives your students all of it.