The only agent that thinks for itself

Autonomous Monitoring with self-learning AI built-in, operating independently across your entire stack.

Unlimited Metrics & Logs
Machine learning & MCP
5% CPU, 150MB RAM
3GB disk, >1 year retention
800+ integrations, zero config
Dashboards, alerts out of the box
> Discover Netdata Agents

Centralized metrics streaming and storage

Aggregate metrics from multiple agents into centralized Parent nodes for unified monitoring across your infrastructure.

Stream from unlimited agents
Long-term data retention
High availability clustering
Data replication & backup
Scalable architecture
Enterprise-grade security
> Learn about Parents

Fully managed cloud platform

Access your monitoring data from anywhere with our SaaS platform. No infrastructure to manage, automatic updates, and global availability.

Zero infrastructure management
99.9% uptime SLA
Global data centers
Automatic updates & patches
Enterprise SSO & RBAC
SOC2 & ISO certified
> Explore Netdata Cloud

Deploy Netdata Cloud in your infrastructure

Run the full Netdata Cloud platform on-premises for complete data sovereignty and compliance with your security policies.

Complete data sovereignty
Air-gapped deployment
Custom compliance controls
Private network integration
Dedicated support team
Kubernetes & Docker support
> Learn about Cloud On-Premises

Powerful, intuitive monitoring interface

Modern, responsive UI built for real-time troubleshooting with customizable dashboards and advanced visualization capabilities.

Real-time chart updates
Customizable dashboards
Dark & light themes
Advanced filtering & search
Responsive on all devices
Collaboration features
> Explore Netdata UI

Monitor on the go

Native iOS and Android apps bring full monitoring capabilities to your mobile device with real-time alerts and notifications.

iOS & Android apps
Push notifications
Touch-optimized interface
Offline data access
Biometric authentication
Widget support
> Download apps

The future of infrastructure observability

See our strategic direction across AI-native observability, full-stack signals, operational intelligence, and enterprise platform maturity.

AI-native observability
Full-stack signal coverage
Operational intelligence
Enterprise platform maturity
Agent releases every 6 weeks
Cloud continuous delivery
> Explore Product Roadmap

Best energy efficiency

True real-time per-second

100% automated zero config

Centralized observability

Multi-year retention

High availability built-in

Zero maintenance

Always up-to-date

Enterprise security

Complete data control

Air-gap ready

Compliance certified

Millisecond responsiveness

Infinite zoom & pan

Works on any device

Native performance

Instant alerts

Monitor anywhere

AI-native observability

Continuous delivery

Open source foundation

80% Faster Incident Resolution

AI-powered troubleshooting from detection, to root cause and blast radius identification, to reporting.

True Real-Time and Simple, even at Scale

Linearly and infinitely scalable full-stack observability, that can be deployed even mid-crisis.

90% Cost Reduction, Full Fidelity

Instead of centralizing the data, Netdata distributes the code, eliminating pipelines and complexity.

See and Map Your Entire Network

Live topology, flow analytics, and SNMP device and trap monitoring — unified with your full-stack observability.

Control Without Surrender

SOC 2 Type 2 certified with every metric kept on your infrastructure.

Integrations

800+ collectors and notification channels, auto-discovered and ready out of the box.

800+ data collectors
Auto-discovery & zero config
Cloud, infra, app protocols
Notifications out of the box
> Explore integrations
Real Results
46% Cost Reduction

Reduced monitoring costs by 46% while cutting staff overhead by 67%.

— Leonardo Antunez, Codyas

Zero Pipeline

No data shipping. No central storage costs. Query at the edge.

From Our Users
"Out-of-the-Box"

So many out-of-the-box features! I mostly don't have to develop anything.

— Simon Beginn, LANCOM Systems

No Query Language

Point-and-click troubleshooting. No PromQL, no LogQL, no learning curve.

Enterprise Ready
67% Less Staff, 46% Cost Cut

Enterprise efficiency without enterprise complexity—real ROI from day one.

— Leonardo Antunez, Codyas

SOC 2 Type 2 Certified

Zero data egress. Only metadata reaches the cloud. Your metrics stay on your infrastructure.

Full Coverage
800+ Collectors

Auto-discovered and configured. No manual setup required.

Any Notification Channel

Slack, PagerDuty, Teams, email, webhooks—all built-in.

Built for the People Who Get Paged

Because 3am alerts deserve instant answers, not hour-long hunts.

Every Industry Has Rules. We Master Them.

See how healthcare, finance, and government teams cut monitoring costs 90% while staying audit-ready.

Monitor Any Technology. Configure Nothing.

Install the agent. It already knows your stack.
From Our Users
"A Rare Unicorn"

Netdata gives more than you invest in it. A rare unicorn that obeys the Pareto rule.

— Eduard Porquet Mateu, TMB Barcelona

99% Downtime Reduction

Reduced website downtime by 99% and cloud bill by 30% using Netdata alerts.

— Falkland Islands Government

Real Savings
30% Cloud Cost Reduction

Optimized resource allocation based on Netdata alerts cut cloud spending by 30%.

— Falkland Islands Government

46% Cost Cut

Reduced monitoring staff by 67% while cutting operational costs by 46%.

— Codyas

Real Coverage
"Plugin for Everything"

Netdata has agent capacity or a plugin for everything, including Windows and Kubernetes.

— Eduard Porquet Mateu, TMB Barcelona

"Out-of-the-Box"

So many out-of-the-box features! I mostly don't have to develop anything.

— Simon Beginn, LANCOM Systems

Real Speed
Troubleshooting in 30 Seconds

From 2-3 minutes to 30 seconds—instant visibility into any node issue.

— Matthew Artist, Nodecraft

20% Downtime Reduction

20% less downtime and 40% budget optimization from out-of-the-box monitoring.

— Simon Beginn, LANCOM Systems

Pay per Node. Unlimited Everything Else.

One price per node. Unlimited metrics, logs, users, and retention. No per-GB surprises.

Free tier—forever
No metric limits or caps
Retention you control
Cancel anytime
> See pricing plans

What's Your Monitoring Really Costing You?

Most teams overpay by 40-60%. Let's find out why.

Expose hidden metric charges
Calculate tool consolidation
Customers report 30-67% savings
Results in under 60 seconds
> See what you're really paying

Your Infrastructure Is Unique. Let's Talk.

Because monitoring 10 nodes is different from monitoring 10,000.

On-prem & air-gapped deployment
Volume pricing & agreements
Architecture review for your scale
Compliance & security support
> Start a conversation

Monitoring That Sells Itself

Deploy in minutes. Impress clients in hours. Earn recurring revenue for years.

30-second live demos close deals
Zero config = zero support burden
Competitive margins & deal protection
Response in 48 hours
> Apply to partner

Per-Second Metrics at Homelab Prices

Same engine, same dashboards, same ML. Just priced for tinkerers.

Community: Free forever · 5 nodes · non-commercial
Homelab: $90/yr · unlimited nodes · fair usage
> Get the Homelab Plan

$1,000 Per Referral. Unlimited Referrals.

Your colleagues get 10% off. You get 10% commission. Everyone wins.

10% of subscriptions, up to $1,000 each
Track earnings inside Netdata Cloud
PayPal/Venmo payouts in 3-4 weeks
No caps, no complexity
> Get your referral link
Cost Proof
40% Budget Optimization

"Netdata's significant positive impact" — LANCOM Systems

Calculate Your Savings

Compare vs Datadog, Grafana, Dynatrace

Savings Proof
46% Cost Reduction

"Cut costs by 46%, staff by 67%" — Codyas

30% Cloud Bill Savings

"Reduced cloud bill by 30%" — Falkland Islands Gov

Enterprise Proof
"Better Than Combined Alternatives"

"Better observability with Netdata than combining other tools." — TMB Barcelona

Real Engineers, <24h Response

DPA, SLAs, on-prem, volume pricing

Why Partners Win
Demo Live Infrastructure

One command, 30 seconds, real data—no sandbox needed

Zero Tickets, High Margins

Auto-config + per-node pricing = predictable profit

Homelab Ready
Free Video Course

8-episode Netdata tutorial by LearnLinux.tv

76k+ GitHub Stars

3rd most starred monitoring project

Worth Recommending
Product That Delivers

Customers report 40-67% cost cuts, 99% downtime reduction

Zero Risk to Your Rep

Free tier lets them try before they buy

AI Support Assistant, Available 24/7

Nedi has access to all official documentation, source code, and resources. Ask any question about Netdata—responds in your language.

Deployment & configuration
Troubleshooting & sizing
Alerts & notifications
Evidence-based answers
> Ask Nedi now

Never Fight Fires Alone

Docs, community, and expert help—pick your path to resolution.

Learn.netdata.cloud docs
Discord, Forums, GitHub
Premium support available
> Get answers now

60 Seconds to First Dashboard

One command to install. Zero config. 850+ integrations documented.

Linux, Windows, K8s, Docker
Auto-discovers your stack
> Read our documentation

Level Up Your Monitoring

Real problems. Real solutions. 112+ guides from basic monitoring to AI observability.

76,000+ Engineers Strong

615+ contributors. 1.5M daily downloads. One mission: simplify observability.

Per-Second. 90% Cheaper. Data Stays Home.

Side-by-side comparisons: costs, real-time granularity, and data sovereignty for every major tool.

See why teams switch from Datadog, Prometheus, Grafana, and more.

> Browse all comparisons
Edge-Native Observability, Born Open Source
Per-second visibility, ML on every metric, and data that never leaves your infrastructure.
Founded in 2016
615+ contributors worldwide
Remote-first, engineering-driven
Open source first
> Read our story
Promises We Publish—and Prove
12 principles backed by open code, independent validation, and measurable outcomes.
Open source, peer-reviewed
Zero config, instant value
Data sovereignty by design
Aligned pricing, no surprises
> See all 12 principles
Edge-Native, AI-Ready, 100% Open
76k+ stars. Full ML, AI, and automation—GPLv3+, not premium add-ons.
76,000+ GitHub stars
GPLv3+ licensed forever
ML on every metric, included
Zero vendor lock-in
> Explore our open source
Build Real-Time Observability for the World
Remote-first team shipping per-second monitoring with ML on every metric.
Remote-first, fully distributed
Open source (76k+ stars)
Challenging technical problems
Your code on millions of systems
> See open roles
Meet the Team Behind Netdata
Conferences, meetups, and tradeshows where you can see Netdata in action and talk to the engineers who build it.
Live demos and deep dives
Book 1-on-1 meetings
Talks and panel sessions
Event recaps and photos
> See all events
Talk to a Netdata Human in <24 Hours
Sales, partnerships, press, or professional services—real engineers, fast answers.
Discuss your observability needs
Pricing and volume discounts
Partnership opportunities
Media and press inquiries
> Book a conversation
Your Data. Your Rules.
On-prem data, cloud control plane, transparent terms.
Trust & Scale
76,000+ GitHub Stars

One of the most popular open-source monitoring projects

SOC 2 Type 2 Certified

Enterprise-grade security and compliance

Data Sovereignty

Your metrics stay on your infrastructure

Validated
University of Amsterdam

"Most energy-efficient monitoring solution" — ICSOC 2023, peer-reviewed

ADASTEC (Autonomous Driving)

"Doesn't miss alerts—mission-critical trust for safety software"

Community Stats
615+ Contributors

Global community improving monitoring for everyone

1.5M+ Downloads/Day

Trusted by teams worldwide

GPLv3+ Licensed

Free forever, fully open source agent

Why Join?
Remote-First

Work from anywhere, async-friendly culture

Impact at Scale

Your work helps millions of systems

HPE Proliant icon

HPE Proliant

HPE Proliant

Plugin: go.d.plugin Module: snmp

Overview

Monitor HPE Proliant (network device) with Netdata over SNMP. Netdata recognizes the device automatically by its sysObjectID (recognized across 1 device identifiers) and collects the metrics this profile declares — on top of the generic SNMP baseline — with no manual OID configuration.

Netdata’s SNMP collector matches the device to the hpe-proliant.yaml profile via sysObjectID/sysDescr, then polls the OIDs it declares.

This integration is supported on all platforms.

This integration supports multiple instances configured side-by-side.

Default Behavior

Auto-Detection

Auto-detected as HPE Proliant via sysObjectID/sysDescr.

Limits

The default configuration for this integration does not impose any limits.

Performance Impact

The default configuration for this integration is not expected to impose a significant performance impact on the system.

Setup

You can configure the snmp collector in two ways:

MethodBest forHow to
UIFast setup without editing filesGo to Nodes → Configure this node → Collectors → Jobs, search for snmp, then click + to add a job.
FileIf you prefer configuring via file, or need to automate deployments (e.g., with Ansible)Edit go.d/snmp.conf and add a job.

Important

UI configuration requires paid Netdata Cloud plan.

Prerequisites

SNMP access

SNMP must be enabled on the device and reachable from the Netdata Agent acting as the site’s SNMP hub.

Configuration

Options

Configure the SNMP collector with the device hostname and SNMP credentials. See the SNMP collector reference for all options.

via UI

Configure the snmp collector from the Netdata web interface:

  1. Go to Nodes.
  2. Select the node where you want the snmp data-collection job to run and click the :gear: (Configure this node). That node will run the data collection.
  3. The Collectors → Jobs view opens by default.
  4. In the Search box, type snmp (or scroll the list) to locate the snmp collector.
  5. Click the + next to the snmp collector to add a new job.
  6. Fill in the job fields, then click Test to verify the configuration and Submit to save.
    • Test runs the job with the provided settings and shows whether data can be collected.
    • If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.

via File

The configuration file name for this integration is go.d/snmp.conf.

The file format is YAML. Generally, the structure is:

update_every: 1
autodetection_retry: 0
jobs:
  - name: some_name1
  - name: some_name2

You can edit the configuration file using the edit-config script from the Netdata config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/snmp.conf
Examples

There are no configuration examples.

Metrics

On top of the generic SNMP baseline (the Generic SNMP Device integration — interfaces, system, IP/TCP/UDP, host resources), this HPE Proliant profile adds the metrics below. Each is collected only where the device exposes the matching OID — inclusion means the profile requests it; availability depends on the device model and software.

155 metrics in 21 groups; each row is a chart context usable in alerts.

GroupMetrics
Hardware / ASR5
Hardware / Battery2
Hardware / Bus1
Hardware / CPU3
Hardware / Disk1
Hardware / Fan2
Hardware / Memory9
Hardware / Power2
Hardware / PowerSupply4
Hardware / Sensor2
Hardware / StorageController1
Hardware / Temperature2
Network / IP28
Network / Interface52
Network / TCP12
Network / UDP6
System / CPU1
System / Disk13
System / ErrorLog1
System / FileSystem6
System / Uptime2

Hardware / ASR

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHeAsrCondition{status}deviceOverall condition of the ASR feature
snmp.device_prof_cpqHeAsrNetworkAccessStatus{status}deviceStatus of the ASR network access feature
snmp.device_prof_cpqHeAsrPost{status}deviceWhether the ASR timer passed the server Power-On Self-Test
snmp.device_prof_cpqHeAsrRebootCount{reboot}deviceNumber of ASR reboots that have occurred on the server since last manual reboot
snmp.device_prof_cpqHeAsrStatus{status}deviceOverall status of the ASR feature

Hardware / Battery

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHeSysBatteryCondition{status}per battery_indexOverall condition of the battery
snmp.device_prof_cpqHeSysBatteryStatus{status}per battery_indexStatus of the battery

Hardware / Bus

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHeSysUtilEisaBusMin%deviceEISA bus utilization as a percentage of the theoretical maximum during the last minute

Hardware / CPU

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqSeCpuExtSpeedMHzper cpu_index, cpu_max_threads, cpu_cores, cpu_primaryExternal frequency of the processor bus in megahertz
snmp.device_prof_cpqSeCpuSpeedMHzper cpu_index, cpu_max_threads, cpu_cores, cpu_primaryCurrent internal speed of the processor in megahertz
snmp.device_prof_cpqSeCpuStatus{status}per cpu_index, cpu_max_threads, cpu_cores, cpu_primaryStatus of the processor

Hardware / Disk

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqDaPhyDrvCurrentTemperatureCelper drive_cntrl_idx, drive_indexTemperature of the physical drive in degrees Celsius

Hardware / Fan

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHeThermalCpuFanStatus{status}deviceStatus of the processor fan(s) in the system
snmp.device_prof_cpqHeThermalSystemFanStatus{status}deviceStatus of the fan(s) in the system

Hardware / Memory

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHeCorrMemLogCondition{status}deviceOverall condition of the correctable memory error log feature
snmp.device_prof_cpqHeCorrMemLogStatus{status}deviceOverall status of the correctable memory error log feature
snmp.device_prof_cpqHeCorrMemTotalErrs{error}deviceNumber of correctable memory errors that have occurred
snmp.device_prof_cpqHeResMem2ModuleCondition{status}per mem_board_indexCurrent status of the correctable memory errors for this memory module
snmp.device_prof_cpqSiMemModuleCellStatus{status}per mem_board_index, mem_module_index, mem_module_technology, mem_module_typeCurrent status for this memory module
snmp.device_prof_cpqSiMemModuleECCStatus{status}per mem_board_index, mem_module_index, mem_module_technology, mem_module_typeCurrent status of correctable memory errors for this memory module
snmp.device_prof_cpqSiMemModuleFrequencyMHzper mem_board_index, mem_module_index, mem_module_technology, mem_module_typeMemory module frequency in megahertz
snmp.device_prof_cpqSiMemModuleSizeByper mem_board_index, mem_module_index, mem_module_technology, mem_module_typeModule memory size in kilobytes
snmp.device_prof_cpqSiMemModuleSpeednsper mem_board_index, mem_module_index, mem_module_technology, mem_module_typeModule memory speed in nanoseconds

Hardware / Power

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHeFltTolPwrSupplyStatus{status}deviceStatus of the fault tolerant power supply
snmp.device_prof_cpqHePowerMeterCurrReadingWdeviceCurrent power meter reading in watts

Hardware / PowerSupply

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHeFltTolPowerSupply{present}per power_supply_index, chassis_numIndicates the presence of a power supply
snmp.device_prof_cpqHeFltTolPowerSupplyCapacityMaximumWper power_supply_index, chassis_numMaximum capacity of the power supply in watts
snmp.device_prof_cpqHeFltTolPowerSupplyCapacityUsedWper power_supply_index, chassis_numCurrently used capacity of the power supply in watts
snmp.device_prof_cpqHeFltTolPowerSupplyStatus{status}per power_supply_index, chassis_numCurrent status of the power supply

Hardware / Sensor

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHeTemperatureCelsiusCelper temperature_indexCurrent temperature sensor reading in degrees celsius
snmp.device_prof_cpqHeTemperatureCondition{status}per temperature_indexTemperature sensor condition

Hardware / StorageController

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqDaCntlrCondition{status}per controller_indexCondition of the device controller

Hardware / Temperature

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHeThermalCondition{status}deviceOverall condition of the system’s thermal environment
snmp.device_prof_cpqHeThermalTempStatus{status}deviceStatus of the system’s temperature sensors

Network / IP

Metric (chart context)UnitScopeDescription
snmp.device_prof_ipSystemStatsHCInBcastPkts{packet}/sper ipversionThe number of IP broadcast datagrams received
snmp.device_prof_ipSystemStatsHCInForwDatagrams{forward}/sper ipversionInput datagrams for which this entity was not their final IP destination and for which this entity attempted to find a route to fo…
snmp.device_prof_ipSystemStatsHCInMcastOctetsbit/sper ipversionThe total number of octets received in IP multicast datagrams
snmp.device_prof_ipSystemStatsHCInMcastPkts{packet}/sper ipversionThe number of IP multicast datagrams received
snmp.device_prof_ipSystemStatsHCInOctetsbit/sper ipversionOctets received in input IP datagrams
snmp.device_prof_ipSystemStatsHCInReceives{packet}/sper ipversionInput IP datagrams received
snmp.device_prof_ipSystemStatsHCOutBcastPkts{packet}/sper ipversionThe number of IP broadcast datagrams transmitted
snmp.device_prof_ipSystemStatsHCOutForwDatagrams{packet}/sper ipversionThe number of datagrams for which this entity was not their final IP destination and for which it was successful in finding a path…
snmp.device_prof_ipSystemStatsHCOutMcastOctetsbit/sper ipversionThe total number of octets transmitted in IP multicast datagrams
snmp.device_prof_ipSystemStatsHCOutMcastPkts{packet}/sper ipversionThe number of IP multicast datagrams transmitted
snmp.device_prof_ipSystemStatsHCOutOctetsbit/sper ipversionThe total number of octets in IP datagrams delivered to the lower layers for transmission
snmp.device_prof_ipSystemStatsHCOutRequests{packet}/sper ipversionThe total number of IP datagrams that local IP user-protocols including ICMP supplied to IP in requests for transmission
snmp.device_prof_ipSystemStatsHCOutTransmits{packet}/sper ipversionThe total number of IP datagrams that this entity supplied to the lower layers for transmission
snmp.device_prof_ipSystemStatsInAddrErrors{error}/sper ipversionInput IP datagrams discarded due to invalid IP address in header
snmp.device_prof_ipSystemStatsInDiscards{error}/sper ipversionThe number of input IP datagrams for which no problems were encountered to prevent their continued processing, but were discarded
snmp.device_prof_ipSystemStatsInHdrErrors{error}/sper ipversionDiscarded input IP datagrams due to errors in their IP headers
snmp.device_prof_ipSystemStatsInNoRoutes{errors}/sper ipversionInput IP datagrams discarded because no route could be found to transmit them to their destination
snmp.device_prof_ipSystemStatsInTruncatedPkts{error}/sper ipversionInput IP datagrams discarded due to datagram frame not carrying enough data
snmp.device_prof_ipSystemStatsInUnknownProtos{error}/sper ipversionLocally-addressed IP datagrams received successfully but discarded due to an unknown or unsupported protocol
snmp.device_prof_ipSystemStatsOutDiscards{error}/sper ipversionThe number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but wer…
snmp.device_prof_ipSystemStatsOutFragCreates{fragment}/sper ipversionThe number of output datagram fragments that have been generated as a result of IP fragmentation
snmp.device_prof_ipSystemStatsOutFragFails{error}/sper ipversionThe number of IP datagrams that have been discarded because they needed to be fragmented but could not be
snmp.device_prof_ipSystemStatsOutFragOKs{packet}/sper ipversionThe number of IP datagrams that have been successfully fragmented
snmp.device_prof_ipSystemStatsOutFragReqds{packet}/sper ipversionThe number of IP datagrams that would require fragmentation in order to be transmitted
snmp.device_prof_ipSystemStatsOutNoRoutes{error}/sper ipversionThe number of locally generated IP datagrams discarded because no route could be found to transmit them to their destination
snmp.device_prof_ipSystemStatsReasmFails{error}/sper ipversionThe number of failures detected by the IP re-assembly algorithm
snmp.device_prof_ipSystemStatsReasmOKs{packet}/sper ipversionThe number of IP datagrams successfully reassembled
snmp.device_prof_ipSystemStatsReasmReqds{fragment}/sper ipversionThe number of IP fragments received that needed to be reassembled at this interface

Network / Interface

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqNicIfPhysAdapterAlignmentErrors{frame}/sper adapter_nameFrames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check
snmp.device_prof_cpqNicIfPhysAdapterBadReceives{frame}/sper adapter_nameFrames that were received by the adapter but which had an error
snmp.device_prof_cpqNicIfPhysAdapterBadTransmits{frame}/sper adapter_nameFrames that were not transmitted by the adapter because of an error
snmp.device_prof_cpqNicIfPhysAdapterCarrierSenseErrors{frame}/sper adapter_nameThe number of times that the carrier sense signal from the physical layer interface was not asserted or was de-asserted during tra…
snmp.device_prof_cpqNicIfPhysAdapterCondition{status}per adapter_nameThe condition of this physical adapter
snmp.device_prof_cpqNicIfPhysAdapterDeferredTransmissions{frame}/sper adapter_namePackets whose transmission was delayed on its first attempt because the medium was busy
snmp.device_prof_cpqNicIfPhysAdapterExcessiveCollisions{frame}/sper adapter_namePackets that, due to excessive collisions, are not transmitted successfully
snmp.device_prof_cpqNicIfPhysAdapterFCSErrors{frame}/sper adapter_nameFrames received on a particular interface that are an integral number of octets in length but do not pass the FCS check
snmp.device_prof_cpqNicIfPhysAdapterFrameTooLongs{frame}/sper adapter_nameA count of frames received on a particular interface that exceed the maximum permitted frame size
snmp.device_prof_cpqNicIfPhysAdapterGoodReceives{frame}/sper adapter_nameSuccessfully received frames by the physical adapter
snmp.device_prof_cpqNicIfPhysAdapterGoodTransmits{frame}/sper adapter_nameSuccessfully transmitted frames by the physical adapter
snmp.device_prof_cpqNicIfPhysAdapterInOctetsbit/sper adapter_nameTraffic received on the physical adapter
snmp.device_prof_cpqNicIfPhysAdapterInternalMacReceiveErrors{frame}/sper adapter_nameA count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error
snmp.device_prof_cpqNicIfPhysAdapterInternalMacTransmitErrors{frame}/sper adapter_nameFrames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error
snmp.device_prof_cpqNicIfPhysAdapterLateCollisions{frame}/sper adapter_nameA late collision is one that occurred 64 bytes or more into the packet
snmp.device_prof_cpqNicIfPhysAdapterMultipleCollisionFrames{frame}/sper adapter_namePackets that are involved in multiple collisions and are subsequently transmitted successfully
snmp.device_prof_cpqNicIfPhysAdapterOutOctetsbit/sper adapter_nameTraffic sent on the physical adapter
snmp.device_prof_cpqNicIfPhysAdapterSingleCollisionFrames{frame}/sper adapter_namePackets that are involved in a single collision and are subsequently transmitted successfully
snmp.device_prof_cpqNicIfPhysAdapterSpeedbit/sper adapter_nameAn estimate of the interface current bandwidth
snmp.device_prof_cpqNicIfPhysAdapterState{status}per adapter_nameThe fault tolerant state of this adapter
snmp.device_prof_cpqNicIfPhysAdapterStatus{status}per adapter_nameThe physical adapter status
snmp.device_prof_ifAdminStatus{status}per interface, interfaceCurrent administrative state of the interface
snmp.device_prof_ifHighSpeedbit/sper interface, interfaceEstimate of the interface’s current bandwidth
snmp.device_prof_ifNumber{interface}deviceNumber of network interfaces regardless of their current state present on this system
snmp.device_prof_ifOperStatus{status}per interface, interfaceCurrent operational state of the interface
snmp.device_prof_ipIfStatsHCInBcastPkts{packet}/sper interface_index, ipversionThe number of IP broadcast datagrams received
snmp.device_prof_ipIfStatsHCInDelivers{packet}/sper interface_index, ipversionThe total number of datagrams successfully delivered to IP user-protocols including ICMP
snmp.device_prof_ipIfStatsHCInForwDatagrams{forward}/sper interface_index, ipversionThe number of input datagrams for which this entity was not their final IP destination and for which this entity attempted to find…
snmp.device_prof_ipIfStatsHCInMcastOctetsbit/sper interface_index, ipversionThe total number of octets received in IP multicast datagrams
snmp.device_prof_ipIfStatsHCInMcastPkts{packet}/sper interface_index, ipversionThe number of IP multicast datagrams received
snmp.device_prof_ipIfStatsHCInOctetsbit/sper interface_index, ipversionThe total number of octets received in input IP datagrams, including those received in error
snmp.device_prof_ipIfStatsHCOutBcastPkts{packet}/sper interface_index, ipversionThe number of IP broadcast datagrams transmitted
snmp.device_prof_ipIfStatsHCOutForwDatagrams{packet}/sper interface_index, ipversionThe number of datagrams for which this entity was not their final IP destination and for which it was successful in finding a path…
snmp.device_prof_ipIfStatsHCOutMcastOctetsbit/sper interface_index, ipversionThe total number of octets transmitted in IP multicast datagrams
snmp.device_prof_ipIfStatsHCOutMcastPkts{packet}/sper interface_index, ipversionThe number of IP multicast datagrams transmitted
snmp.device_prof_ipIfStatsHCOutOctetsbit/sper interface_index, ipversionThe total number of octets in IP datagrams delivered to the lower layers for transmission
snmp.device_prof_ipIfStatsHCOutRequests{packet}/sper interface_index, ipversionThe total number of IP datagrams that local IP user-protocols including ICMP supplied to IP in requests for transmission
snmp.device_prof_ipIfStatsHCOutTransmits{packet}/sper interface_index, ipversionThe total number of IP datagrams that this entity supplied to the lower layers for transmission
snmp.device_prof_ipIfStatsInAddrErrors{error}/sper interface_index, ipversionThe number of input IP datagrams discarded because the IP address in their IP header’s destination field was not a valid address t…
snmp.device_prof_ipIfStatsInDiscards{error}/sper interface_index, ipversionThe number of input IP datagrams for which no problems were encountered to prevent their continued processing, but were discarded
snmp.device_prof_ipIfStatsInHdrErrors{error}/sper interface_index, ipversionThe number of input IP datagrams discarded due to errors in their IP headers
snmp.device_prof_ipIfStatsInNoRoutes{error}/sper interface_index, ipversionThe number of input IP datagrams discarded because no route could be found to transmit them to their destination
snmp.device_prof_ipIfStatsInTruncatedPkts{error}/sper interface_index, ipversionThe number of input IP datagrams discarded because the datagram frame didn’t carry enough data
snmp.device_prof_ipIfStatsInUnknownProtos{error}/sper interface_index, ipversionThe number of locally-addressed IP datagrams received successfully but discarded because of an unknown or unsupported protocol
snmp.device_prof_ipIfStatsOutDiscards{error}/sper interface_index, ipversionThe number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but wer…
snmp.device_prof_ipIfStatsOutFragCreates{fragment}/sper interface_index, ipversionThe number of output datagram fragments that have been generated as a result of IP fragmentation
snmp.device_prof_ipIfStatsOutFragFails{packet}/sper interface_index, ipversionThe number of IP datagrams that have been discarded because they needed to be fragmented but could not be
snmp.device_prof_ipIfStatsOutFragOKs{packet}/sper interface_index, ipversionThe number of IP datagrams that have been successfully fragmented
snmp.device_prof_ipIfStatsOutFragReqds{packet}/sper interface_index, ipversionThe number of IP datagrams that would require fragmentation in order to be transmitted
snmp.device_prof_ipIfStatsReasmFails{error}/sper interface_index, ipversionThe number of failures detected by the IP re-assembly algorithm
snmp.device_prof_ipIfStatsReasmOKs{packet}/sper interface_index, ipversionThe number of IP datagrams successfully reassembled
snmp.device_prof_ipIfStatsReasmReqds{fragment}/sper interface_index, ipversionThe number of IP fragments received that needed to be reassembled at this interface

Network / TCP

Metric (chart context)UnitScopeDescription
snmp.device_prof_tcpActiveOpens{transition}/sdeviceTCP connections transitioning from CLOSED to SYN-SENT
snmp.device_prof_tcpAttemptFails{failure}/sdeviceFailed TCP connection attempts
snmp.device_prof_tcpCurrEstab{connection}deviceCurrent TCP connections in ESTABLISHED or CLOSE-WAIT state
snmp.device_prof_tcpEstabResets{reset}/sdeviceTCP connections reset from ESTABLISHED/CLOSE-WAIT
snmp.device_prof_tcpHCInSegs{packet}/sdeviceTCP segments received
snmp.device_prof_tcpHCOutSegs{packet}/sdeviceTCP segments sent
snmp.device_prof_tcpInErrs{error}/sdeviceTCP segments received with errors
snmp.device_prof_tcpInSegs{packet}/sdeviceTCP segments received
snmp.device_prof_tcpOutRsts{reset}/sdeviceTCP segments sent with RST flag
snmp.device_prof_tcpOutSegs{packet}/sdeviceTCP segments sent
snmp.device_prof_tcpPassiveOpens{transition}/sdeviceTCP connections transitioning from LISTEN to SYN-RCVD
snmp.device_prof_tcpRetransSegs{retransmit}/sdeviceTCP segments retransmitted

Network / UDP

Metric (chart context)UnitScopeDescription
snmp.device_prof_udpHCInDatagrams{packet}/sdeviceUDP datagrams received
snmp.device_prof_udpHCOutDatagrams{packet}/sdeviceUDP datagrams sent
snmp.device_prof_udpInDatagrams{packet}/sdeviceUDP datagrams received
snmp.device_prof_udpInErrors{error}/sdeviceUDP datagrams received but couldn’t be delivered (not due to missing app)
snmp.device_prof_udpNoPorts{error}/sdeviceUDP datagrams received with no app on the destination port
snmp.device_prof_udpOutDatagrams{packet}/sdeviceUDP datagrams sent

System / CPU

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpu_usage%per cpu_unit_indexThe current CPU utilization

System / Disk

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqDaPhyDrvFactReallocs{sector}per drive_cntrl_idx, drive_indexNumber of spare sectors available for remapping at the time the physical drive was shipped
snmp.device_prof_cpqDaPhyDrvHSeekErrs{error}per drive_cntrl_idx, drive_indexTotal number of times the physical disk drive detected a seek error (high)
snmp.device_prof_cpqDaPhyDrvHardReadErrs{error}per drive_cntrl_idx, drive_indexNumber of read errors that could not be recovered by a physical drive’s ECC algorithm or retries
snmp.device_prof_cpqDaPhyDrvHardWriteErrs{error}per drive_cntrl_idx, drive_indexNumber of write errors that could not be recovered by a physical drive
snmp.device_prof_cpqDaPhyDrvRecvReadErrs{error}per drive_cntrl_idx, drive_indexNumber of read errors corrected through physical drive retries
snmp.device_prof_cpqDaPhyDrvRecvWriteErrs{error}per drive_cntrl_idx, drive_indexNumber of write errors corrected through physical drive retries or recovered by a physical drive
snmp.device_prof_cpqDaPhyDrvRefHourshper drive_cntrl_idx, drive_indexTotal number of hours that a physical drive has been in operation since it was stamped
snmp.device_prof_cpqDaPhyDrvSeekErrs{error}per drive_cntrl_idx, drive_indexTotal number of times the physical disk drive detected a seek error (low)
snmp.device_prof_cpqDaPhyDrvSizeByper drive_cntrl_idx, drive_indexSize of the physical drive in megabytes
snmp.device_prof_cpqDaPhyDrvSmartStatus{status}per drive_cntrl_idx, drive_indexS.M.A.R.T status of the physical drive
snmp.device_prof_cpqDaPhyDrvSpinupTimedsper drive_cntrl_idx, drive_indexTime it takes for a physical drive to spin up to full speed in tenths of seconds
snmp.device_prof_cpqDaPhyDrvStatus{status}per drive_cntrl_idx, drive_indexThe status of the physical drive
snmp.device_prof_cpqDaPhyDrvUsedReallocs{sector}per drive_cntrl_idx, drive_indexNumber of sectors of the reallocation area that have been used by the physical drive

System / ErrorLog

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHeCritLogCondition{status}deviceOverall condition of the critical error log feature

System / FileSystem

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHoFileSysAllocUnitsTotal{file}per file_sys_index, file_sys_descrTotal number of files that can be stored on the file system if a limit exists
snmp.device_prof_cpqHoFileSysAllocUnitsUsed{file}per file_sys_index, file_sys_descrNumber of files on the file system
snmp.device_prof_cpqHoFileSysPercentSpaceUsed%per file_sys_index, file_sys_descrPercent of file system space currently in use
snmp.device_prof_cpqHoFileSysSpaceTotalByper file_sys_index, file_sys_descrFile system size
snmp.device_prof_cpqHoFileSysSpaceUsedByper file_sys_index, file_sys_descrMegabytes of file system space currently in use
snmp.device_prof_cpqHoFileSysStatus{status}per file_sys_index, file_sys_descrThreshold status of the file system

System / Uptime

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpqHeSysUtilLifeTimesdeviceTotal time the system has been in full operation in minutes
snmp.device_prof_systemUptimesdeviceTime since the system was last rebooted or powered on.

Alerts

There are no alerts configured by default for this integration.

The observability platform companies need to succeed

Sign up for free

Want a personalised demo of Netdata for your use case?

Contact Sales