<!--startmeta
custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/collector/snmp/npm-catalog/integrations/cisco_ironport_email.md"
meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/collector/snmp/npm-catalog/metadata.yaml"
sidebar_label: "Cisco Ironport Email"
learn_status: "Published"
learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations"
keywords: ['cisco', 'ironport', 'email', 'snmp', 'secure email gateway', 'npm']
message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE"
endmeta-->

<!-- markdownlint-disable-file -->

# Cisco Ironport Email


<img src="https://netdata.cloud/img/cisco.svg" width="150"/>


Plugin: go.d.plugin
Module: snmp

<img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" />

## Overview

Monitor Cisco Ironport Email (secure email gateway) with Netdata over SNMP. Netdata recognizes the device automatically by its `sysObjectID` (recognized across 2 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 **cisco-ironport-email.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 Cisco Ironport Email 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:

| Method                | Best for                                                                                 | How to                                                                                                                                 |
|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
| [**UI**](#via-ui)     | Fast setup without editing files                                                         | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **snmp**, then click **+** to add a job. |
| [**File**](#via-file) | If 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:

```yaml
update_every: 1
autodetection_retry: 0
jobs:
  - name: some_name1
  - name: some_name2
```
You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).

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

##### Examples
There are no configuration examples.



## Alerts

There are no alerts configured by default for this integration.



## Metrics

On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco Ironport Email 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.

**66 metrics** in 20 groups; each row is a chart context usable in alerts.

| Group | Metrics |
|---|---|
| Hardware / Disk | 2 |
| Hardware / Fan | 1 |
| Hardware / Power | 2 |
| Hardware / Sensor | 1 |
| Mail / Queue | 4 |
| Mail / Transfer | 1 |
| Network / Bandwidth | 4 |
| Network / DNS | 2 |
| Network / Interface | 4 |
| System / CPU | 2 |
| System / Disk | 1 |
| System / License | 1 |
| System / Memory | 2 |
| System / Resource | 2 |
| System / Security | 1 |
| System / Service | 2 |
| System / Uptime | 2 |
| Web / Cache | 11 |
| Web / HTTP | 20 |
| Web / Throughput | 1 |

### Hardware / Disk

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_raidEvents` | `{event}/s` | device | The total number of RAID events that have occurred since the last appliance power on event |
| `snmp.device_prof_ironport_raidStatus` | `{status}` | per ironport_raid_id | Represents the status of a drive attached to a RAID controller in the appliance |

### Hardware / Fan

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_fanRPMs` | `{revolution}/min` | per ironport_fan_name | Speed in RPMs of the chassis fan |

### Hardware / Power

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_powerSupplyRedundancy` | `{status}` | per ironport_power_supply_name | Status of a collection of one or more power supplies |
| `snmp.device_prof_ironport_powerSupplyStatus` | `{status}` | per ironport_power_supply_name | Status of the power supply |

### Hardware / Sensor

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_degreesCelsius` | `Cel` | per ironport_temperature_name | Temperature reading for the sensor being instrumented |

### Mail / Queue

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_oldestMessageAge` | `s` | device | The number of seconds the oldest message has been in queue |
| `snmp.device_prof_ironport_perCentQueueUtilization` | `%` | device | Percent of total queue capacity used |
| `snmp.device_prof_ironport_queueAvailabilityStatus` | `{status}` | device | Status indicating the current availability of the message queue |
| `snmp.device_prof_ironport_workQueueMessages` | `{message}` | device | Number of messages in the work queue |

### Mail / Transfer

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_mailTransferThreads` | `{thread}` | device | Number of threads that perform some task related to transferring mail. |

### Network / Bandwidth

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_cacheBwidthSavingNow` | `bit/s` | device | Bandwidth savings in the last minute |
| `snmp.device_prof_ironport_cacheBwidthSpentNow` | `bit/s` | device | Bandwidth spent in the last minute |
| `snmp.device_prof_ironport_cacheBwidthTotalNow` | `bit/s` | device | Bandwidth total in the last minute |
| `snmp.device_prof_ironport_cacheTotalBandwidthSaving` | `bit/s` | device | The total bandwidth savings for HTTP |

### Network / DNS

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_outstandingDNSRequests` | `{request}/s` | device | Number of DNS requests that have been sent but for which no reply has been received |
| `snmp.device_prof_ironport_pendingDNSRequests` | `{request}` | device | Number of DNS requests waiting to be sent |

### Network / Interface

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ifAdminStatus` | `{status}` | per interface, interface | Current administrative state of the interface |
| `snmp.device_prof_ifHighSpeed` | `bit/s` | per interface, interface | Estimate of the interface's current bandwidth |
| `snmp.device_prof_ifNumber` | `{interface}` | device | Number of network interfaces regardless of their current state present on this system |
| `snmp.device_prof_ifOperStatus` | `{status}` | per interface, interface | Current operational state of the interface |

### System / CPU

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_cpu_usage` | `%` | device | The current CPU utilization |
| `snmp.device_prof_ironport_perCentCPULoad` | `%` | device | This object provides a general idea of how busy the CPU is according to the appliance software, within the last 5 seconds of ironp… |

### System / Disk

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_perCentDiskIOUtilization` | `%` | device | Disk I/O within the last 5-15 seconds |

### System / License

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_keySecondsUntilExpire` | `s` | per ironport_key_description, ironport_key_is_perpetual | Seconds until the valid Feature Key expires |

### System / Memory

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_memoryAvailabilityStatus` | `{status}` | device | Current status of memory availability |
| `snmp.device_prof_memory_usage` | `%` | device | This object provides a general idea of how much memory is being consumed by the appliance software |

### System / Resource

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_openFilesOrSockets` | `{fd}` | device | This object notes how many files or sockets are open on the appliance. In normal operating conditions, the measurement is taken at… |
| `snmp.device_prof_ironport_resourceConservationReason` | `{status}` | device | Reason the appliance is conserving resources |

### System / Security

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_fipsMode` | `{status}` | device | Indicates whether the appliance is operating in FIPS mode |

### System / Service

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_updateFailures` | `{attempt}/s` | per ironport_update_service_name | The number of failed attempts that have occurred when updating a service. |
| `snmp.device_prof_ironport_updates` | `{attempt}/s` | per ironport_update_service_name | The number of successful attempts that have occurred when updating a service |

### System / Uptime

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_cacheDuration` | `s` | device | The proxy up time |
| `snmp.device_prof_systemUptime` | `s` | device | Time since the system was last rebooted or powered on. |

### Web / Cache

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_cacheDeniedNow` | `{denial}` | device | Cache denial throughput time in the last minute |
| `snmp.device_prof_ironport_cacheDeniedRespTimeNow` | `ms` | device | Cache denial response time in the last minute |
| `snmp.device_prof_ironport_cacheErrRespTimeNow` | `ms` | device | Cache error response time in the last minute |
| `snmp.device_prof_ironport_cacheErrsNow` | `{error}` | device | Cache error throughput time in the last minute |
| `snmp.device_prof_ironport_cacheHitRespTimeNow` | `ms` | device | Cache hit response time in the last minute |
| `snmp.device_prof_ironport_cacheHitsNow` | `{hit}` | device | Hit throughput in the last minute |
| `snmp.device_prof_ironport_cacheMeanByteHitRatio` | `%` | device | The HTTP byte hit ratio |
| `snmp.device_prof_ironport_cacheMeanHitRatio` | `%` | device | The HTTP hit ratio |
| `snmp.device_prof_ironport_cacheMissRespTimeNow` | `ms` | device | Cache miss response time in the last minute |
| `snmp.device_prof_ironport_cacheMissesNow` | `{miss}` | device | Miss throughput in the last minute |
| `snmp.device_prof_ironport_cacheTotalRespTimeNow` | `ms` | device | Cache total response time in the last minute |

### Web / HTTP

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_cacheClientAccepts` | `{socket}/s` | device | The total number of sockets accepted from the clients |
| `snmp.device_prof_ironport_cacheClientErrors` | `{error}/s` | device | The number of HTTP errors caused by client connections. |
| `snmp.device_prof_ironport_cacheClientIdleConns` | `{connection}` | device | The number of connected but idle persistent client connections |
| `snmp.device_prof_ironport_cacheClientMaxConns` | `{connection}` | device | The maximum number of simultaneous client connections that will be allowed |
| `snmp.device_prof_ironport_cacheClientReqDenials` | `{response}/s` | device | The number of responses blocked by access control |
| `snmp.device_prof_ironport_cacheClientRequests` | `{request}/s` | device | The number of HTTP requests received from clients |
| `snmp.device_prof_ironport_cacheClientTotalConns` | `{connection}` | device | The current number of active + idle client connections |
| `snmp.device_prof_ironport_cacheCltReplyErrPct` | `%` | device | The percentage of errors in the HTTP replies to clients |
| `snmp.device_prof_ironport_cacheMeanHitRespTime` | `ms` | device | The HTTP mean response time of Hits |
| `snmp.device_prof_ironport_cacheMeanMissRespTime` | `ms` | device | The HTTP mean response time of Misses |
| `snmp.device_prof_ironport_cacheMeanRespTime` | `ms` | device | The HTTP mean response time |
| `snmp.device_prof_ironport_cacheServerCloseIdleConns` | `{connection}/s` | device | The number of server connections closed due to idle time limits |
| `snmp.device_prof_ironport_cacheServerConnsThresh` | `{connection}` | device | The limit on the number of server connections |
| `snmp.device_prof_ironport_cacheServerErrors` | `{error}/s` | device | The number of HTTP errors while fetching objects |
| `snmp.device_prof_ironport_cacheServerIdleConns` | `{connection}` | device | The number of connected but idle persistent server connections |
| `snmp.device_prof_ironport_cacheServerLimitIdleConns` | `{connection}/s` | device | The number of times the number of idle persistent connections hit the count limit and caused a connection to be closed |
| `snmp.device_prof_ironport_cacheServerRequests` | `{request}/s` | device | The total number of HTTP requests sent to servers |
| `snmp.device_prof_ironport_cacheServerSockets` | `{socket}` | device | The total number of sockets opened from the servers |
| `snmp.device_prof_ironport_cacheServerTotalConns` | `{connection}` | device | The current number of active + idle server connections |
| `snmp.device_prof_ironport_cacheTotalHttpReqs` | `{request}/s` | device | Total number of HTTP requests from clients |

### Web / Throughput

| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
| `snmp.device_prof_ironport_cacheThruputNow` | `{request}` | device | Request throughput in the last minute |
