One Sensor software. Four collection roles.
AmrudAi uses one Sensor software across Network, Infrastructure, Flow and Log roles. Intelligent placement connects each workload to an eligible Sensor with the right reachability, permissions and headroom, while keeping your sites, security boundaries and operating policies in control.
The application experience
See the complete workspace. Enlarge any image to inspect its panels, navigation and evidence at actual size.
Complete the operational workflow
Apply defaults at the relevant tenant, site, group or entity scope and show the effective monitoring behavior. An explicit monitoring-profile choice remains distinct from a profile derived from business criticality.
Use bounded adaptive collection and incident-triggered diagnostics within permissions, reachability and resource budgets. Normal monitoring, control and telemetry durability retain priority when an endpoint or Sensor is under pressure.
Stop assigning collectors by hand.
AmrudAi selects the best eligible Sensor using network reachability, collection role, location, spare capacity and your policies. The same Universal Sensor software supports Network, Infrastructure, Flow and Log roles, so you can standardize installation while separating workloads where it makes operational sense.
Access → role → locality → capacity → policy
Reachable · correct role · spare capacity
Reachable · correct role · recovery capacity
Permitted secondary vantage point
The monitoring work lands on an eligible Sensor. Your placement policies and pinned assignments stay in control.
The capability in detail
Use the same Sensor software and management model for Network devices and paths, Infrastructure hosts and Agent ingestion, Flow traffic evidence, and Log events. Configure the role around the work and location instead of operating four separate Sensor products.
AmrudAi selects the best eligible Sensor using real reachability, network proximity, packet loss, protocol compatibility, site affinity and current health. The geographically nearest Sensor is not automatically the right choice.
Keep customer, region, security-zone, credential and allowed-pool policies in the decision. Only authorized Sensors with the required capabilities can receive the work, preserving separation between estates and restricted network segments.
Balance expected collection effort against CPU, memory, storage, queues, polling completion and available failover capacity. Account for the monitoring profile and its cost rather than treating every device or endpoint as an identical unit.
Run collection through bounded worker pools. Give high-volume Flow and Log ingestion dedicated capacity when needed so traffic bursts and event surges do not consume the resources required for routine polling and operational checks.
Choose automatic assignment, recommendation with approval, a manually pinned Sensor or an approved pool. AmrudAi detects sustained imbalance and improves placement under your policy, using stability controls to avoid repeatedly moving devices for minor load changes.
Sensors keep executing their current authorized monitoring work while local capacity remains available. Durable buffering, visible queue age and controlled replay retain operational context through temporary connectivity interruptions.
See roles, assignments, workload, health, maintenance state, queue pressure and collection freshness together. Review placement recommendations and understand why a Sensor is eligible, overloaded, excluded or reserved for resilience.
From information to action
Install the Sensor software, establish its authenticated identity and configure its approved collection role and location.
Choose resources, credentials, profiles and the permitted customer, site, region or Sensor pool.
Use automatic selection or review the recommendation, then activate monitoring through the approved onboarding policy.
Track workload and freshness, preserve spare capacity and rebalance within the controls you have enabled.
Deployment choices and operating controls
Deploy Sensors near the estate they monitor and keep placement decisions aligned with your access, locality, capacity and resilience policies.
Connect the workflow
No. AmrudAi provides one Sensor software with role-based deployment profiles. You can use separate instances for different roles, sites or workload volumes while retaining one operating and management model.
It first checks eligibility, including customer and resource scope, credentials, permitted pools, protocol support and reachability. It then considers locality, health, current and expected work, queue pressure and spare capacity to select an appropriate Sensor.
Yes. Use manual placement or a restricted Sensor pool when the network or operating policy requires it. Placement recommendations do not silently override a manual pin; automatic rebalancing follows the policy you explicitly enable.
An approved mixed profile can handle smaller compatible workloads. Where high-volume Flow, logs, cloud APIs or synthetic work would compete with protected monitoring, assign dedicated role capacity. The decision follows the workload, security and locality requirements.
Core establishes a provisional association with an eligible Sensor during enrollment. Normal monitoring activates through your authorized approval or trusted auto-approval policy, together with the relevant access, entitlement and capacity checks.
Sensors continue their current authorized collection while local capacity remains available, buffer the resulting telemetry and replay it when communication returns. Queue age, storage pressure and remaining capacity stay visible; buffering is not unlimited.
Explore the technology, service dependencies and operating requirements that matter to your team.
Search the complete website · Esc to close · Tab to navigate results