Main: Insight

Updated

Main: Insight

Overview

Use this page to understand what LoadGen Insight collects and why it matters. The Insight overview is the informational front door for the infrastructure monitoring area, sitting in the Main section of the navigation menu alongside the other module overviews. It draws the moving parts as one diagram, sequences the work as a lifecycle, and links into the pages where each piece is configured.

Insight answers the question "what was the infrastructure doing while that happened?". LoadGen Insight agents run on the machines in your environment and report their health and counters back to the platform, so a slow transaction in a load test or a failed monitoring session can be lined up against CPU, memory, and other machine-level metrics from the same moment. Without that layer you know a user experience degraded; with it you can say which machine ran out of headroom.

This page changes nothing and requires no configuration to open. The capability cards are navigation into the Insight pages, and those pages keep their own licence and role gates.

Main: Insight, full page

Key concepts

  • Insight agent - Software installed on a monitored machine that connects to the platform and reports machine metrics. An agent shown as Offline or Needs Onboarding contributes no data, leaving a gap in anything downstream that depends on it. (related: Insight: Dashboard)
  • Machine group - A logical collection of monitored machines sharing one configuration, so monitoring settings, thresholds, and WMI collection are applied per group rather than machine by machine. (related: Insight: Machine Groups)
  • Needs Onboarding - The staging area holding machines that have connected to the platform but are not yet assigned to a group. Machines are dragged from here into a group to bring them into collection. (related: Insight: Machine Groups)
  • Fleet health - The at-a-glance count of active, offline, and unprovisioned agents, used to confirm data-collection coverage before a test rather than discovering the gap afterwards. (related: Insight: Dashboard)
  • Machine registration - The administrative surface where machines and their API keys are managed, under the Expert-mode Configuration Insight section. (related: Configuration: Insight: Machines)

When to use it

  • When you want machine-level metrics correlated with a load test or a monitoring session and need to know what to install where.
  • When you are checking data-collection coverage before a test, so you do not run a test that produces an unexplainable result.
  • When a machine you expected to see in Insight is missing and you want the registration and grouping chain in one view.
  • When you are planning how to organise a larger estate into machine groups with shared thresholds.
  • When a service level objective depends on infrastructure metrics and you need to confirm the underlying agents are reporting.
  • When you want a launch point into the Insight dashboard, machine groups, or machine registration.

Before you begin

  • No prerequisites for opening this page. It is informational and ungated.
  • Using the module requires the Insight licence module (LG055). Without it, the Insight pages show an activation card instead of the feature. Check your entitlement on Infrastructure: Licensing.
  • A machine must have the Insight agent installed and must have connected to the platform before it appears in the Needs Onboarding area.
  • A machine only contributes data once it has been assigned to a machine group.
  • An Insight datasource must be configured on Configuration: Datasources for collected data to be stored.

Steps

Step 1

Open Insight in the Main section of the left navigation menu.

Expected result: The overview page opens immediately, with the architecture hero at the top. It renders on an appliance with no Insight agents registered yet.

Step 2

Read the architecture hero.

The diagram shows Insight agents on your machines reporting to the platform, and where that telemetry is consumed: alongside load test results, alongside monitoring sessions, and as a source for service level objectives that depend on infrastructure metrics. On the platform map, Insight is drawn as an optional telemetry flow, because the rest of the platform works without it.

Quantities drawn inside the diagram are illustrative and prefixed e.g.; they do not read your configuration.

Main: Insight, architecture hero

Main: Insight, lifecycle strip

Step 3

Follow the lifecycle strip.

The strip lays Insight out as six ordered steps. The underlying chain, as documented across the Insight pages, is:

  1. Point storage at a datasource. Set the Insight datasource on Configuration: Datasources.
  2. Install and register agents. Deploy the Insight agent to the machines you want covered and manage registration and API keys on Configuration: Insight: Machines.
  3. Let them connect. A newly connected machine lands in the Needs Onboarding staging area.
  4. Group them. Create groups and drag machines in on Insight: Machine Groups, applying monitoring settings, thresholds, and WMI collection per group.
  5. Verify coverage. Confirm active, offline, and unprovisioned counts on Insight: Dashboard before you rely on the data.
  6. Use the data. Correlate machine metrics with runs and sessions in the Analyse pages, and feed infrastructure-based service level objectives.

The page's lifecycle strip, From bare machine to dashboards, in six steps, reads: 1 Register (machines or tokens), 2 Group (assign a machine group), 3 Configure (counters, WMI, probes), 4 Collect (metrics into InfluxDB), 5 Watch (Analyse dashboards), 6 Verify (the Data Health matrix). The numbered list above expands those labels (verified).

Step 4

Use the capability cards to enter the module.

Each card names one thing Insight does and links to the page where you do it. Selecting a card is read-only navigation; no agent is changed and no group is created from this page.

Main: Insight, capability cards

Step 5

Read the pulse chips, if present.

This page can surface real agent status counts that the platform already holds. Treat these as orientation only; Insight: Dashboard is the authority for fleet health, with per-group and per-version breakdowns.

Next steps

  • No agents yet? Register machines and issue API keys on Configuration: Insight: Machines.
  • Machines connected but idle? Assign them to a group on Insight: Machine Groups; machines in Needs Onboarding do not contribute data.
  • Checking coverage before a test? Open Insight: Dashboard and confirm the offline and unprovisioned counts are zero.
  • Want server counters during a load test specifically? That is a separate mechanism: configure Configuration: Systems Under Test: Profiles, which collects Windows Performance Counters for the duration of a test.
  • Want to chart Insight data against test data? Use the chart workbench in the Analyse section, which covers Insight as one of its data domains.
  • Want to see the whole platform, not just this module? Open Main: Platform Map.

Verify the result

The page is working correctly when the architecture hero renders as a diagram, the lifecycle strip shows its steps, and the capability cards navigate into the Insight pages. Nothing is saved here, so there is no state to confirm. If a capability card opens a page showing an activation card instead of the feature, that is the target page's licence gate rather than a fault on this page.

Troubleshooting

  • Symptom: A capability card opens a page showing an activation card with Activate License and Learn More. Fix: Insight (LG055) is not licensed on this appliance. Check Infrastructure: Licensing. This overview page is ungated by design and describes the module regardless.
  • Symptom: The lifecycle mentions Configuration: Insight: Machines, which is not in your navigation menu. Fix: CONFIGURATION: INSIGHT is an Expert-mode section; switch the sidebar footer toggle to Expert.
  • Symptom: A machine has the agent installed but never appears. Fix: Confirm it can reach the platform and that its API key is valid, then look in the Needs Onboarding area on Insight: Machine Groups.
  • Symptom: A machine appears but reports no data. Fix: It is probably still unassigned. Drag it from Needs Onboarding into a machine group, and confirm an Insight datasource is set on Configuration: Datasources.
  • Symptom: A service level objective based on infrastructure metrics reports NoData. Fix: Check the Insight dashboard for offline agents covering that service; an offline agent produces a gap rather than a breach.
  • Symptom: A quantity in the diagram does not match your environment. Fix: Numbers prefixed e.g. inside the diagram are illustrative examples, not readings of your configuration.
Was this article helpful?
0 out of 0 found this helpful