feat: support for availability checks from multiple agents #3318

New issue

Open

opened 2026-05-15 01:31:26 +00:00 by mfreeman451 · 0 comments

mfreeman451 commented

2026-05-15 01:31:26 +00:00

Owner

Is your feature request related to a problem?

We need to be able to support network sweeps/scans from multiple agents.

Scenario:

Customer has agent-a deployed in segmented OT network
Customer has agent-b deployed in intranet

Customer wants to test availability of a device from both agents, the idea being that access to a device (tcp/ICMP checks) should fail (or be blocked by network ACLs) from the segmented OT network, but should be allowed through the intranet.

Customer wants the ability to assign primary is_available to a particular agent. Customer also wants to expose availability checks from both agent in the device details view. We need to also include metadata in the device record that includes where the availability check came from, so basically additional fields for every agent that includes the agent name and the is_available = true|false, and we need to also update the Armis northbound integration so we can choose which is_available field we want to use. Right now the Armis northbound integration just uses the is_available field, but we need to be able to choose which agent we want to use to update the Armis tag with. In this particular customer use case, the customer is trying to update Armis records to show if a device is isolated or not, if the device is not available from the particular agent, that means the device is isolated and that the network ACLs are in-place and working.

Our other or original option was to just assign different agents to different partitions, and then import two sets of devices into the inventory, one for each partition assigned to the two different agents. The downside to this approach is we double up the inventory and it becomes difficult for users/operators to understand what they're looking. We have a new group of users that primary wants to use ServiceRadar to see if devices are actually online and don't necessarily care whether or not the device is isolated.

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

**Is your feature request related to a problem?** We need to be able to support network sweeps/scans from multiple agents. Scenario: Customer has agent-a deployed in segmented OT network Customer has agent-b deployed in intranet Customer wants to test availability of a device from both agents, the idea being that access to a device (tcp/ICMP checks) should fail (or be blocked by network ACLs) from the segmented OT network, but should be allowed through the intranet. Customer wants the ability to assign primary `is_available` to a particular agent. Customer also wants to expose availability checks from both agent in the device details view. We need to also include metadata in the device record that includes where the availability check came from, so basically additional fields for every agent that includes the agent name and the is_available = true|false, and we need to also update the Armis northbound integration so we can choose which is_available field we want to use. Right now the Armis northbound integration just uses the `is_available` field, but we need to be able to choose which agent we want to use to update the Armis tag with. In this particular customer use case, the customer is trying to update Armis records to show if a device is isolated or not, if the device is not available from the particular agent, that means the device is isolated and that the network ACLs are in-place and working. Our other or original option was to just assign different agents to different partitions, and then import two sets of devices into the inventory, one for each partition assigned to the two different agents. The downside to this approach is we double up the inventory and it becomes difficult for users/operators to understand what they're looking. We have a new group of users that primary wants to use ServiceRadar to see if devices are actually online and don't necessarily care whether or not the device is isolated. **Describe the solution you'd like** A clear and concise description of what you want to happen. **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. **Additional context** Add any other context or screenshots about the feature request here.