1. Pattern
1.1. Application Pattern Type
1.1.1. Run Order
1.1.2. Operating System
1.2. variables
1.2.1. Syntax
1.3. Neebula Discovery Language - NDL
2. Probe
2.1. Unix or Linux
2.1.1. Linux Red Hat 6 and above
2.1.2. Ubuntu 12 and above
2.1.3. CentOS 6 and above
2.1.4. Port
2.1.4.1. 22
2.2. Windows
2.2.1. Port
2.2.1.1. 135
2.2.2. WMI service
2.3. SNMP
2.3.1. Port
2.3.1.1. 161
2.3.2. MIB
3. Kubernete
3.1. Cluster
3.1.1. Pod
3.1.1.1. Image
3.1.1.1.1. Docker Container
4. Discovery extended capabilities
4.1. ECC queue
4.1.1. Messages
4.1.1.1. Input
4.1.1.1.1. from a MID Server to the instance
4.1.1.1.2. Sensor
4.1.1.2. Output
4.1.1.2.1. from the instance to a MID server
4.1.1.2.2. probe
5. File-based Discovery
6. Event
6.1. Plugin
6.1.1. com.glideapp.itom.snac
6.2. role
6.2.1. evt_mgmt_admin
6.2.1.1. evt_mgmt_operator
6.2.1.1.1. evt_mgmt_user
6.2.2. evt_mgmt_integration
6.3. table
6.3.1. em_event
6.3.1.1. evt_mgmt.flap_frequency
6.3.1.1.1. Flap frequency (frequency an alert must reoccur to enter the flapping state). An alert enters the flapping state if its flap count meets or exceeds this property within the time period defined by the flap interval property.
6.3.1.1.2. Default
6.3.1.2. Bucket field
6.3.1.2.1. Latency issues for receiving events
6.3.1.3. State
6.3.1.3.1. Ready
6.3.1.3.2. Processed
6.3.1.3.3. Ignored
6.3.1.3.4. Error
6.3.2. em_alert
6.3.2.1. Auto Close
6.3.2.1.1. evt_mgmt.alert_auto_close_interval
6.3.2.2. Quick response
6.3.2.2.1. Run Remediation
6.3.2.2.2. Launch Application
6.3.2.3. State
6.3.2.3.1. Open
6.3.2.3.2. Reopen
6.3.2.3.3. Flapping
6.3.2.3.4. Close
6.3.2.4. Severity
6.3.2.4.1. Critical
6.3.2.4.2. Major
6.3.2.4.3. Minor
6.3.2.4.4. Warning
6.3.2.4.5. OK
6.3.2.4.6. Clear
6.4. Event Rule
6.4.1. Event Filter
6.4.2. Transform and Compose Alert Output
6.4.2.1. map event fields to alert fields
6.4.2.2. Code
6.4.2.2.1. regex
6.4.3. Threshold
6.4.4. Binding
6.4.4.1. default class
6.4.5. identifiers
6.4.5.1. Message Key
6.4.5.1.1. Source, Type, Node, Resource, and Metric Name
6.4.5.1.2. cmdb_ci_hardware
6.5. Alert Management Rules
6.5.1. Alert Filter
6.5.2. avoid de duplication of alerts for the same event
6.5.3. Actions
6.5.3.1. Remediation Subflows
6.5.3.1.1. task
6.5.3.1.2. Incident
6.5.3.1.3. Knowledge Article
6.5.3.1.4. Change
6.5.3.1.5. Alert
6.5.3.1.6. Password
6.5.3.2. Remediation Workflows
6.5.3.2.1. Application Remediation
6.5.3.3. Launch Applications
6.6. Alert Correlation Rules
6.6.1. Primary alert
6.6.1.1. An alert that matches this filter is the representative of it's correlated alerts. To see the correlated alert under it, double click the alert in the alert console.
6.6.2. Secondary alert
6.6.2.1. An alert that matches this filter is not shown in the alert console.
6.7. connector
6.7.1. connector Definitions
6.7.1.1. AWS CloudWatch Metrics
6.7.1.2. Azure Metrics
6.7.1.3. HPOM
6.7.1.4. Hyperic
6.7.1.5. IBM Netcool
6.7.1.6. Icinga2
6.7.1.7. NagiosXI
6.7.1.8. NNMi
6.7.1.9. OMi
6.7.1.10. Op5
6.7.1.11. Opsview
6.7.1.12. PRTG
6.7.1.13. SAP Solman
6.7.1.14. SCOM
6.7.1.15. Solarwinds
6.7.1.16. vCenter
6.7.1.17. vRealize
6.7.1.18. Zabbix
6.7.2. default schedule
6.7.2.1. evt_mgmt.connector.minimum_schedule
6.7.2.1.1. 120 seconds
6.7.3. Groovy
7. cmdb_ci_computer
7.1. cmdb_ci_server
8. cmdb_ci_appl
8.1. cmdb_ci_app_server
8.1.1. cmdb_ci_app_server_tomcat
9. MID Server
9.1. Connection
9.1.1. ECC Queue
9.1.1.1. Persistent connection
9.2. role
9.2.1. mid_server
9.3. port
9.3.1. 443
9.4. OS
9.4.1. Windows
9.4.1.1. Best Practice
9.4.1.2. permission
9.4.1.2.1. local Administrator
9.4.1.3. versions
9.4.1.3.1. Windows Server 2008
9.4.1.3.2. Windows Server 2012
9.4.1.3.3. Windows Server 2016
9.4.1.4. .NET Framework
9.4.1.4.1. 4.0
9.4.1.4.2. 4.5
9.4.1.4.3. 4.6
9.4.1.4.4. 4.7
9.4.2. Unix or Linux
9.5. Cluster
9.5.1. Failover
9.5.2. Load Balance
9.6. Incompatible The MID Server and instance do not belong to the same release
9.7. Version indicators
9.7.1. Red
9.7.2. Yellow
9.7.3. Green
9.7.3.1. Compatible, but an upgrade is recommended.
9.7.3.2. Compatible
9.7.4. Gray
9.7.4.1. Incompatible. The instance cannot detect the version
9.8. properties
9.8.1. mid.buildstamp
9.8.2. mid.version.override
9.8.3. mid.pinned.version
9.9. Extension
9.9.1. Operational Intelligence Metrics
9.9.2. MID Web Server
9.10. Supported applications
9.10.1. Cloud Management
9.10.2. Discovery
9.10.3. EventManagement
9.10.4. OperationalIntelligence
9.10.5. Orchestration
9.10.6. ServiceAnalytics
9.10.7. ServiceMapping
10. Best Practice
11. CMDB
11.1. Tables
11.1.1. cmdb
11.1.1.1. cmdb_ci
11.1.1.1.1. cmdb_ci_hardware
12. Ports
13. Phases
13.1. 01-Scanning
13.2. 02-Classifying
13.2.1. fail/error
13.2.1.1. No results returned from probe
13.2.1.1.1. Wrong Credentials
13.2.2. Reclassify a CI
13.2.2.1. Downgrade
13.2.2.2. Upgrade
13.2.2.3. Switch
13.3. 03-Identifying
13.4. 04-Exploring
14. Dashboard
14.1. CMDB health
14.1.1. KPI
14.1.1.1. Correctness
14.1.1.2. Compliance
14.1.1.3. Classification
14.2. Event Management
14.2.1. Discovered Business service
14.2.2. Technical service
14.2.3. Business service
14.2.4. Alert group
15. License
15.1. 01.Standard
15.1.1. Discovery
15.1.2. Event management
15.2. 02.Professional
15.2.1. Operational intelligence
15.2.2. Orchestration
15.3. 03.Enterprise
15.3.1. Service mapping
15.3.2. Cloud management
15.3.2.1. manage hybrid clouds
16. Discovery Configuration
16.1. Completeness
16.1.1. Recommended
16.2. CI schedule manager
16.2.1. Discovered Devices
16.2.2. Errors
16.2.3. Required
16.2.4. Unidentified IPs
16.2.5. CI Schedules
16.2.6. Running schedules