Customizing Monitoring

Monitoring in Nexus is configurable in three places: the Monitoring settings dialog on the Monitoring page itself, the app-wide Settings view, and the per-widget settings of each monitoring widget you place on the dashboard or a panel.

1. Monitoring settings on the Monitoring page

On a PC with more than one GPU, the GPU tab of the Monitoring page shows a Change link next to the GPU name. It opens the Monitoring settings dialog:

  • GPU - choose which GPU's stats appear across the dashboard. The default option reads Automatic - uses followed by the GPU it currently resolves to, and integrated GPUs are marked (integrated).
  • Timeline events - "Choose which events appear above the graph." A master Show events on the graph toggle, then one toggle per event kind (app opens, admin elevations, USB attach/detach, privacy events, custom events).

A PC with one GPU has no dialog to open; the same timeline-event toggles are in Settings, next.

2. Settings > Monitoring & Diagnostics

In Settings, the Monitoring & Diagnostics tab holds the app-wide monitoring preferences:

  • Features - Monitoring ("Collect sensor history to disk. Widgets keep showing live values while this is off.") and Diagnostics ("Watch for hardware issues and send health alerts.").
  • Sensor Temperature - Celsius (°C) or Fahrenheit (°F). This is the "Unit for CPU, GPU, and other hardware temperatures. Outdoor weather keeps its own unit in the Weather widget."
  • Timeline events - the same event toggles as the Monitoring page's dialog, so you can manage them from either place.

The CPU temperature sensor and GPU temperature sensor pickers sit in the Lighting & Cooling tab. These pin which temperature sensor stands in as "the" CPU or GPU temperature everywhere one is shown or used, including as the default source for new fan curves. Each option shows its live reading, the automatic pick is marked (default), and Reset to defaults clears both overrides.

Two related format settings live in Settings under Appearance: Time format (12-hour or 24-hour) and Number format, both of which apply to monitoring readouts too.

3. Monitoring widget settings

Monitoring gauges on the dashboard home and on panel layouts are configured per widget. Depending on the widget's size and style, its settings expose:

  • Sensors - pick the source per slot: first a device category (Quick, CPU, GPU, Memory, Memory Modules, Motherboard, Network, Storage, SSD SMART, FPS, Battery, Cooler, EC, PSU - only categories your hardware actually reports are offered), then the specific Sensor.
  • Design - the gauge style used to draw the value.
  • Label - Auto, Hide, or Custom with a Custom label field.
  • Range - Adaptive scaling, or Fixed with your own Min and Max, for gauges that support a range.

See Panel Widgets & Layout for placing and arranging the widgets themselves.

4. Fan roles feed the CPU and GPU charts

The fan-speed line on the Monitoring page's CPU and GPU charts averages all system fans until you tell Nexus which fans belong to which component. On the Cooling page, click the icon on a fan card (Mark fan device) and choose Generic fan, CPU, or GPU. Marked fans give the CPU and GPU tabs a precise per-role fan speed.

Note

Monitoring view state, including your dashboard layout, is stored per profile. If you use multiple profiles, each can keep its own monitoring setup, or you can share one across profiles from Settings > Profiles.