ARMARA Course 03

Course 03 / Module 02

Find out what's already firing on your machine

Inventory the complete curated schedule roster and make an explicit decision for every row without mutating unreliable controls.

Level
Beginner to intermediate
Time
10 minutes
Commands
4
Finish
A 13-row decision worksheet

Video / coming soon

The written lesson is complete now.

Inventory without toggling

The original roster has 13 curated jobs after the disposable test was removed. This sitting records decisions but does not mutate shipped rows.

Use PowerShell and a separate note for the decision worksheet.
01

Read installed background behavior

Run in your terminal
armaraos cron list
Run in your terminal
armaraos cron list --json
Real roster of 13 curated jobs with enabled values and cron expressions
Fresh live output / original roster restored / 24 August 2026

These jobs shipped with the prepared instance. Their background activity is not, by itself, evidence of compromise.

02

Find the fastest loop

armaraos-agent-health-monitor is scheduled every 15 minutes and currently reports enabled. Read your own JSON rather than memorizing a course count, because local state can differ.

03

Notice the money monitors

The roster includes armaraos-budget-threshold-alert and armaraos-daily-budget-digest. The product's own schedules make spending visibility explicit.

04

Write a decision for every row

DecisionUse it when
KeepYou can explain the purpose and want the current behavior.
ReviewThe name or schedule is not enough to justify a change.
Not enabledThe live field is false; preserve that observation.

Add one plain sentence describing each job. Unknown rows remain in review.

05

Keep the broken controls visible

Run in your terminal
armaraos cron disable <ID>
Run in your terminal
armaraos cron enable <ID>

These commands exist, but 0.8.3 did not persist the change for the disposable job. Do not use a success banner as evidence, and do not experiment on curated rows here.

06

Preserve evidence before deletion

Delete is permanent and removes the definition you would need to inspect later. Keep the row and its JSON while you investigate its purpose.

Check it / narrate every row

Finish the decision worksheet.

Run in your terminal
armaraos cron list --json

Read every job's enabled value and your decision aloud. Any unknown purpose remains in review; no mutation is required.

Safety note

Do not delete curated jobs to reduce visual clutter. Deletion removes the definition, and the verified disable control cannot currently be trusted to persist.

Troubleshooting for this sitting
What you seeLikely causeWhat to do
More than 13 rowsAnother job was added.Identify extras by name and context.
Enabled counts differLocal state changed.Trust current JSON.
Purpose is unclearThe name is insufficient.Mark review and preserve it.
Disable reports successThe control may not persist.Verify JSON and do not rely on the banner.

Back to Module 3.1

Next / Module 3.3

Text your agent from your phone: setup, and reading what the wizard wrote

Lesson ready