Skip to content

Network and infrastructure monitoring

Anosys accepts any signal you can send over HTTP or OpenTelemetry, so you can monitor network devices, servers, containers and device fleets next to your AI and product data.

What people monitor

Area Typical signals
Network devices Interface utilization, packet loss, error rates, firewall and load-balancer counters, DNS latency
Servers and containers CPU, memory, disk, pod restarts, request and error rates, latency percentiles
IoT and edge Sensor readings, device heartbeats, firmware versions, connectivity
Security Connection attempts, targeted ports, unusual sources

Get the data in

%%{init: {"flowchart": {"curve": "linear"}}}%%
graph LR
    A["Devices, SNMP, syslog,<br/>host metrics"] --> B["OpenTelemetry Collector<br/>on your network"]
    C["Scripts and agents"] -->|REST| E["Anosys endpoint"]
    B -->|OTLP/HTTP| E
    E --> F["Dashboards, Auto-Insights,<br/>Alert Builder"]
  1. Create an endpoint of type Networking & Monitoring (or Industrial / Scientific for sensor data).
  2. Pick a method:
    • OpenTelemetry Collector as a gateway: it collects from SNMP, syslog, host metrics and Kubernetes receivers and forwards to Anosys. See OpenTelemetry.
    • REST from your own scripts or device agents. See Send any data.
  3. Name your fields in Collecting → Field Mapping (for example device, interface, site).

For large historical imports, email support@anosys.ai.

Analyze and alert

  • Dashboards → Auto-Insights suggests views for network data, such as threat signals and targeted ports.
  • Visualizations such as World Heatmap, Network Graph, Heatmap and Advanced Time Series suit infrastructure data. See Dashboards.
  • Data Processing → Alert Builder notifies Slack, email or webhooks on thresholds or AI-evaluated conditions. See Alerts.
  • Pipelines roll up high-frequency data and run checks on a schedule.

Next steps