ARGUSNOC for Meraki — Operationally Driven, Network Operations Centerread-only
⚙ Argus settings · synced across your machines
Lab Features & write controls
Applies toOperationsNetworkSecurity Audit
New / write-capable features start in Lab Testing — live only on lab/test locations. Enable for Production to roll out everywhere; after 7 days it’s archived (shipped).
Lab/Test keywords — a location qualifies only if its name contains one of these as a whole word. Comma-separated:
⏻ Remediable networks WRITE
Applies toSecurity Audit
The only networks Argus may apply fixes to (Action Plans → “Let Argus fix it”). Add your lab/test boxes — everything else is apply-blocked, enforced here and server-side. Production stays untouchable.
Op-targets K
Applies toOperations
The Operations tab is a stack of op-targets — each a named group of devices we watch at a store. Two kinds: VLAN (everything connected on given VLAN(s), e.g. Toast POS) and Roster (named devices at fixed IPs we expect live + on a set VLAN, e.g. Konductor). Reorder, retitle, edit, add — or archive / request delete (no hard delete; request delete signals Joey to remove it for good).
Planned-missing devices
Applies toOperations
Set inline & per-network — in a roster op-target’s table click mark planned on any missing device. Accepted devices show PLANNED not MISSING and don’t break SOLID (that store only).
📡 API endpoint
Applies toOperationsNetworkSecurity Audit
Every Argus REST call goes to this bridge — a read-only proxy. The org API key lives only on the bridge, never in your browser.
REST endpoint:…
Upstream:Meraki Dashboard API v1 — https://api.meraki.com/api/v1