System health and search capacity

System health confirms what Vyrux can reach, what the last scan read and how long each read took, and whether the background scan is running. Copy diagnostics gives support everything they need in one paste.

System health with the background scan, updates, and what the last scan read.

Updates

New releases of Vyrux are published on Splunkbase. Splunk checks for them by itself, and Updates shows the version installed and whether a newer one is available.

1. Go to Admin, System health and look at Updates.
2. If a new version is available, click Open Manage Apps.
3. Click Update next to Vyrux Security. In Splunk Cloud, the same page installs Splunkbase updates, or your Splunk admin can do it for you.
4. Your settings, history and kept reports stay as they are.

Rules that start at the same time

Splunk can run only so many searches at once, based on the number of CPU cores. Rules written as every 5 minutes all start on the same minutes, so they queue for the same slots and Splunk skips some of them. Data model accelerations queue for those slots too.

Vyrux finds this and proposes a start minute for each rule. A rule that ran every 5 minutes still runs every 5 minutes, over the same search window. Only the minute it starts on changes.

1. Go to Admin, System health.
2. Under Rules that start at the same time, click Show the new schedules to see each rule, its schedule now and the one proposed.
3. Click Send for approval, or Apply if your team does not need a second approver.
4. Each moved rule gets its own entry in the change log, so any one can be rolled back.