---
title: "Issue Section Attributes"
canonical: "https://docs.infoblox.com/space/NCSG/23199804/Issue%20Section%20Attributes"
format: markdown
---
> Macro (inline-media-image)

  
 Use one or more optional Issue Sections to generate custom NetMRI issues based on criteria encountered in the processing of the script. NetMRI uses Issues to quantify and report problems and events across the network. In the **Network ****Analysis ****–> ****Issues** tab, the **Network**** Scorecard** shows the results of the daily analysis process and all issues generated for the latest time period. Issues can also be filtered. More than one Issue may be referenced within a CCS script. They can use variable and template definitions to define patterns of interest, and they can both use filter expressions to further examine output to decide when something must be done (the Issue is reported). Three types of Issues are reported by NetMRI, along with a special fourth CCS Issue classification.

- **Errors** are important issues that may affect the smooth operation of the network. Generally, such issues are clear signs that something is wrong.
  - **Warnings** are intermediate level issues that should be addressed after the errors have been corrected. A warning may not be a real problem, depending on the design and operation of the network.
- **Info** issues are provided for information, and typically alert you to minor events that may or may not indicate a problem.
- **CCS** issues are directly related to the execution of a CCS script. CCS uses the Issues page for notification after a script executes. An example is **Invalid**** User**** Account**, which reports the mistaken use of a non-Admin user account or an incorrect login for a device.

Issue sections support the following attributes:

| **Attribute** | **Status** | **Purpose** |
| --- | --- | --- |
| `Issue:` | (required) | issue name |
| `Issue-ID:` | (required) | system-wide unique issue ID |
| `Issue-Severity:` | (required) | "Error", "Warning" or "Info" |
| `Issue-Template:` | (required*) | identifies patterns in the output stream |
| `Issue-Filter:` | (required*) | defines when the issue should be generated |
| `Issue-Details:` | (required) | detailed issue data |
| `Issue-Description:` | (optional) | issue description |
| `Issue-Variables:` | (optional) | define/store values extracted from output stream |

*Issue-Template *and/or* Issue-Filter must exist in a Trigger section.

The list of attributes in the Issues section declares the issue that will be generated should a positive match occur, which will appear in the **Network** **Analysis** **–>** **Issues** page and in configured notifications.

# Issue:

**Used** **In:** Issue sections 

**Status:** Mandatory

Defines the custom issue (previously defined in the NetMRI set) to be generated should a positive match result. This title appears as the banner for the Issue when it appears in NetMRI.

**Example**

All text after the `Issue`: statement defines the Issue type:

`Issue: Process All User Accounts`

# Issue-Description:

**Used** **In:** Script sections 

**Status:** Optional

Defines the description for a custom issue.

**Example**

`Issue-Description: The new firewall rule fails to be written when attempting provisioning by SDC. Check your device configuration and admin permissions.`

# Issue-Details:

**Used** **In:** Issue sections 

**Status:** Mandatory

The mandatory` Issue-Details` attribute defines the name/value pairs to be included in the description of the issue that gets generated. These names are established when the issue template is originally created in the **Configuration** **Management** **–>** **Job** **Management** side tab **–>** **Custom** **Issues** page.

**Example**

`Issue-Details:`

`Host $IPAddress `

`Name $Name`

# Issue-Filter:

**Used** **In:** Issue sections 

**Status:** Mandatory

CCS requires the` Issue-Filter` attribute if the `Issue-Template` attribute is not provided in the script. The` Issue-Filter` applies additional criteria to determine if the issue should be generated. It uses the same logical operators as for `Script-Filters` and other attributes.

**Example**

Note the use of Boolean operators in the filter attribute:

`Issue-Filter:`

`$nofireissue ne "yes" and`

`($do_domain eq "yes" and $have_new_domain ne "yes") or `

`($do_nameserver eq "yes" and $have_new_nameserver ne "yes") or `

`($do_netbios_ns eq "yes" and $have_new_netbios_ns ne "yes") or `

`($do_tacacs eq "yes" and $have_new_tacacs ne "yes") or `

`($do_tftp eq "yes" and $have_new_tftp ne "yes") or`

`($do_time eq "yes" and $have_new_time ne "yes")`

# Issue-ID:

**Used** **In:** Script sections 

**Status:** Mandatory

The `Issue-ID` value must be defined in NetMRI's Custom Issue list (**Config** **Management** **–>** **Job** **Management** tab **–>** **Custom** **Issues**) before it can be called out by a CCS script.

**Example**

`Issue-ID: InvalidUserAccount`

# Issue-Severity:

**Used** **In:** Issue sections 

**Status:** Mandatory

The` Issue-Severity` attribute defines the importance of the issue in the script. Valid choices are Error, Warning and Info. `Issue-Severity` influences the generated Issue's position in the NetMRI Issues List due to the penalty weights assigned by the appliance. For example, a severity of Error yields a placement with other critical Errors closer to the top of the Issues List than Warnings and Informational Issues.

**Example**

`Issue-Severity: Error`

# Issue-Template:

**Used** **In:** Issue sections 

**Status:** Mandatory

A text snippet that defines the syntax to match against the output for the issue reporting. When NetMRI's CCS scripting engine receives the output from the executed command sequence, it interprets the data against the template, which acts as a regular expression to determine whether the pattern matches or does not.

**Example**

`Issue-Template:`

`username $username password 0 .*`

This example shows Cisco but can be for any vendor supported by NetMRI.

# Issue-Variables:

**Used** **In:** Issue sections 

**Status:** Optional

You can define variables for matching in the `Issue-Variables` attribute. Doing so helps build the patterns of interest that the script searches for in the output. CCS interprets the` Issue-Variables` and `Issue-Template` attributes as regular expressions that are applied to the output stream. Many CCS scripts will not define` Issue-Variables` attributes as frequently as other attribute types. The below example declares a Boolean statement that if a set of three well-known variables are set to a certain state (`$nofireissue` does not equal "Yes," and the variables `$do_domain eq "yes"` equals "Yes" and `$have_new_domain` does not equal "Yes," then an issue will be reported.

**Example**

`Issue-Filter:`

`$nofireissue ne "yes" and`  
` ($do_domain eq "yes" and $have_new_domain ne "yes")`