Didactum Monitoring & ScienceLogic SL1 Integration
Complete step-by-step guide for integrating Didactum Monitoring Devices and Sensors into ScienceLogic SL1 via SNMP – including SNMP Credential, Discovery, MIB Import, Device Class, Custom Dynamic Application (Performance & Configuration), SNMP Walker, Event Policy and Alerting.
SL1 Architecture for Didactum: In SL1, the Root OID (also Vendor Number) refers to the unique number assigned to each manufacturer. This is registered with IANA. Each manufacturer creates and organizes OIDs below its Root OID. Didactum's Root OID is .1.3.6.1.4.1.46501 (older firmware) or .1.3.6.1.4.1.39052 (newer models). Dynamic Applications are the core of SL1's monitoring concept: They define which data is collected from a device and how SL1 reacts to this data. The SNMP Walker allows you to "walk" SNMP OIDs on a single device and display real-time values.
- Software: ScienceLogic SL1 (PowerFlow / SL1 12.x)
- Components: Dynamic Applications, Device Classes, PowerPacks, SNMP Walker, Event Policies
- Protocol: SNMP v1 / v2c / v3
- Devices: Didactum Monitoring System 100T / 300T / 500T / 550T
- Sensors: Temperature, Leakage, Humidity, Door Contact, Smoke
1. Prerequisites & System Overview
SL1 System
- ScienceLogic SL1 installed (Appliance, VM or Cloud)
- SL1 Web Interface accessible: <SL1-Server>
- Data Collector (Message Collector) with network access to the Didactum device
- UDP Port 161 outbound for SNMP Polling
- UDP Port 162 inbound for SNMP Traps
- Administrator access (required for Dynamic Application creation)
Didactum Device
- Monitoring System 100T, 300T, 500T or 550T
- SNMP enabled (v2c recommended)
- Device reachable via ICMP from the Data Collector
- MIB file available in the Web Interface
SL1 Architecture for Didactum
[SL1 Web Interface]
|
v
[SL1 Database Server]
|
v
[Data Collector] --SNMP Polling UDP 161--> [Didactum 192.168.1.50]
^ <--SNMP Traps UDP 162---
|
[Dynamic Applications]:
- Didactum Performance DA (Temperature, Leakage, Humidity)
- Didactum Configuration DA (Device Name, Status)
[Device Class]: Didactum Monitoring System
[Event Policies]: Threshold Alarms
2. Enable SNMP on the Didactum Device
Step 1 – Open Web Interface
Open in browser: 192.168.1.50 (adjust to the IP of the Didactum device)
Step 2 – Access SNMP Settings
System Settings → SNMP
Step 3 – Enter the following values
| Field in Didactum Web Interface | Value |
|---|---|
| Enable SNMP | Enabled |
| SNMP Version | v2c (recommended) |
| Community String | didactum_sl1 (do not use "public"!) |
| SNMP Port | 161 |
| Trap Receiver IP | IP of the SL1 Data Collector |
| Trap Port | 162 |
| Trap Version | v2c |
3. Create SNMP Credential in SL1
SL1 uses Credentials to centrally manage access data for SNMP connections.
Navigation
System → Manage → Credentials → Create New Credential → SNMP
SNMPv2c Credential for Didactum
| Field | Value |
|---|---|
| Credential Name | Didactum SNMPv2c |
| SNMP Version | SNMP V2 |
| SNMP Community (Read) | didactum_sl1 |
| Port | 161 |
| Timeout (ms) | 5000 |
| Retries | 3 |
Click Save.
SNMPv3 Credential (optional)
| Field | Value |
|---|---|
| Credential Name | Didactum SNMPv3 |
| SNMP Version | SNMP V3 |
| Security Name | sl1_user |
| Security Level | Auth, Privacy |
| Auth Protocol | SHA |
| Auth Password | Your Auth Password |
| Privacy Protocol | AES-128 |
| Privacy Password | Your Priv Password |
4. Import MIB File (OID Browser)
A MIB file is generic – it is not linked to a specific installed device instance, but applies to all devices of the respective type or manufacturer. The OID Browser in SL1 allows you to browse OIDs and add them directly to Dynamic Applications.
Step 1 – Download MIB from Didactum Web Interface
System Settings → SNMP → "Download MIB File" → didactum.mib
Step 2 – Import MIB into SL1
System → Tools → Import MIB → Select file didactum.mib → Click "Import MIB" → SL1 compiles the MIB and confirms the import
Step 3 – Check MIB in OID Browser
System → Tools → OID Browser
→ Enter in search bar: 46501
→ The Didactum OID hierarchy appears:
1.3.6.1.4.1.46501
└── 5 (sensorTable)
└── 1.1
├── .1 (sensorIndex)
├── .5 (sensorName)
├── .6 (sensorStatus)
└── .7 (sensorValue)
→ Clicking on an OID entry shows description and data type
Step 4 – Add OID directly from Browser to a Dynamic Application
OIDs can be added directly from the OID Browser to a Dynamic Application. In the "Select Action" dropdown, select the desired Dynamic Application, then click "Go".
OID Browser → Select OID .1.3.6.1.4.1.46501.5.1.1.7.101001 → "Select Action" dropdown: "Add to new SNMP Performance Dynamic Application" → Click "Go" → Dynamic Application wizard opens
5. Create Device Class for Didactum
During initial Discovery, SL1 assigns each device to a Device Class based on the SysObjectID. Each SNMP Device Class is linked to a SysObjectID.
Navigation
System → Manage → Device Classes → Create New Device Class
Device Class: Didactum Monitoring System
| Field | Value |
|---|---|
| Device Class Name | Didactum Monitoring System |
| Device Class Category | Environmental Monitoring |
| Device Description | Didactum Environmental Monitoring System – Temperature, Leakage, Humidity |
| SysObjectID | 1.3.6.1.4.1.46501 |
| SNMP Support | Yes |
Second Device Class for newer models (if needed):
| Field | Value |
|---|---|
| Device Class Name | Didactum Monitoring System V2 |
| SysObjectID | 1.3.6.1.4.1.39052 |
Click Save.
6. Configure Discovery Session
Navigation
System → Manage → Discovery Sessions → Create New Discovery Session
Discovery Session: Didactum Device
| Field | Value |
|---|---|
| Discovery Session Name | Didactum Monitor Discovery |
| IP Addresses / CIDR Blocks | 192.168.1.50 |
| SNMP Credentials | Didactum SNMPv2c (from step 3) |
| Collection Server | Select Data Collector |
| Model Devices | Yes |
| Discover Non-SNMP | No (Didactum is SNMP capable) |
Click Save and Run. After the discovery completes, the device appears under:
Registry → Devices → Device Manager → Search for device "192.168.1.50" / "Didactum Monitoring System"
SL1 automatically assigns the device to the previously defined Device Class if the SysObjectID matches.
7. SNMP Walker for OID Verification
The SNMP Walker allows you to "walk" one or more SNMP OIDs on a single device to see a real-time example of the information stored in the OIDs.
Step 1 – Open SNMP Walker
Registry → Devices → Device Manager → Select device "Didactum-Monitor-01" → Tab "Toolbox" → "SNMP Walker"
Step 2 – Query Didactum Sensors
SNMP Walker: OID: .1.3.6.1.4.1.46501.5.1.1 → Click "Walk" → All sensor OIDs are listed with values # Retrieve single temperature value: OID: .1.3.6.1.4.1.46501.5.1.1.7.101001 → Result: e.g. 235 (= 23.5 °C; raw value ÷ 10) # Leakage Status: OID: .1.3.6.1.4.1.46501.5.1.1.7.107001 → Result: 0 (dry) or 1 (water detected)
Step 3 – Add OID directly from Walker to Dynamic Application
From the SNMP Walker, an OID can be added directly to a Dynamic Application. In the "Select Action" dropdown, select the desired Dynamic Application, then click "Go".
SNMP Walker → Click OID .1.3.6.1.4.1.46501.5.1.1.7.101001 → "Select Action": "Add to Didactum Performance DA" → Go
8. Create SNMP Performance Dynamic Application
The Performance Dynamic Application continuously collects numeric measured values (temperature, humidity) and creates trend graphs.
Navigation
System → Manage → Dynamic Applications → Create New Dynamic Application
Step 1 – Create Dynamic Application
| Field | Value |
|---|---|
| Application Name | Didactum Environmental Sensors – Performance |
| Application Type | SNMP Performance |
| Description | Collects measured values of all Didactum sensors via SNMP |
| Poll Frequency | 5 minutes |
| Timeout (ms) | 5000 |
| Retries | 3 |
| Active State | Enabled |
Click Save.
Step 2 – Add Collection Objects for Sensors
Collection Objects define which SNMP OIDs are collected. They are created within a Dynamic Application and determine data type, group number and other properties.
Dynamic Application "Didactum Environmental Sensors – Performance" → Tab "Collections" → Click "Create New"
Collection Object: Temperature Sensor (Raw Value)
| Field | Value |
|---|---|
| Object Name | Temperature Sensor 01 (Raw Value) |
| SNMP OID | .1.3.6.1.4.1.46501.5.1.1.7.101001 |
| Class Type | 4 Performance Gauge |
| Group Number | 1 |
| Description | Raw value ÷ 10 = degrees Celsius. Value 235 = 23.5 °C |
Click Save.
Collection Object: Humidity
| Field | Value |
|---|---|
| Object Name | Humidity Sensor 01 |
| SNMP OID | .1.3.6.1.4.1.46501.5.1.1.7.102001 |
| Class Type | 4 Performance Gauge |
| Group Number | 2 |
| Description | Relative humidity in percent (0–100) |
Collection Object: Leakage Sensor
| Field | Value |
|---|---|
| Object Name | Leakage Sensor 01 |
| SNMP OID | .1.3.6.1.4.1.46501.5.1.1.7.107001 |
| Class Type | 4 Performance Gauge |
| Group Number | 3 |
| Description | Leakage: 0=dry, 1=water detected |
Collection Object: Door Contact
| Field | Value |
|---|---|
| Object Name | Door Contact 01 |
| SNMP OID | .1.3.6.1.4.1.46501.5.1.1.7.104001 |
| Class Type | 4 Performance Gauge |
| Group Number | 4 |
| Description | Door Contact: 0=closed, 1=open |
Collection Object: Smoke Detector
| Field | Value |
|---|---|
| Object Name | Smoke Detector 01 |
| SNMP OID | .1.3.6.1.4.1.46501.5.1.1.7.106001 |
| Class Type | 4 Performance Gauge |
| Group Number | 5 |
| Description | Smoke Detector: 0=OK, 1=Alarm |
Step 3 – Discovery Object for Automatic Assignment
A Discovery Object helps SL1 automatically assign the Dynamic Application to devices. It is a variable that is unique to a specific hardware component and ideally always available when SNMP is running.
Dynamic Application → Tab "Discovery" → "Create New Discovery Object" OID: .1.3.6.1.4.1.46501.5.1.1.7.101001 Test Value: any numeric value Description: Didactum Sensor Value OID – confirms Didactum device → Save
Step 4 – Assign Dynamic Application to Device Class
System → Manage → Device Classes → "Didactum Monitoring System" → Edit → Tab "Dynamic Applications" → "Add Dynamic Application": "Didactum Environmental Sensors – Performance" → Save
9. Create SNMP Configuration Dynamic Application
The Configuration Dynamic Application collects text fields (sensor names, status texts) and displays them in the device profile.
Navigation
System → Manage → Dynamic Applications → Create New Dynamic Application
| Field | Value |
|---|---|
| Application Name | Didactum Environmental Sensors – Configuration |
| Application Type | SNMP Configuration |
| Poll Frequency | 15 minutes |
Collection Objects for Status Texts
Collections → Create New Collection Object
| Object Name | SNMP OID | Class Type |
|---|---|---|
| Sensor Name Temp 01 | .1.3.6.1.4.1.46501.5.1.1.5.101001 | Config String |
| Sensor Status Temp 01 | .1.3.6.1.4.1.46501.5.1.1.6.101001 | Config Integer |
| Sensor Name Leak 01 | .1.3.6.1.4.1.46501.5.1.1.5.107001 | Config String |
| Sensor Status Leak 01 | .1.3.6.1.4.1.46501.5.1.1.6.107001 | Config Integer |
10. Event Policy for Didactum Alarms
Event Policies define when SL1 generates an event from a collected performance value and what severity that event has.
Navigation
Registry → Events → Event Policies → Create New Event Policy
Event Policy: Temperature Warning
| Field | Value |
|---|---|
| Event Policy Name | Didactum Temperature Warning |
| Severity | Major (4) |
| Event Message | Didactum Temperature exceeds warning threshold: %V (raw value; ÷10=°C) |
| Policy Type | Dynamic Application Performance |
| Dynamic Application | Didactum Environmental Sensors – Performance |
| Collection Object | Temperature Sensor 01 (Raw Value) |
| Threshold Type | Greater Than |
| Threshold Value | 280 (= 28.0 °C – raw value × 10) |
Important – Temperature Thresholds:
Didactum delivers temperatures as raw value × 10. 28.0 °C = OID value 280. All SL1 Event Policy threshold values must therefore also be specified × 10.
Event Policy: Temperature Critical
| Field | Value |
|---|---|
| Event Policy Name | Didactum Temperature Critical |
| Severity | Critical (5) |
| Threshold Value | 350 (= 35.0 °C) |
| Event Message | CRITICAL: Didactum Temperature %V – immediate action required! |
Event Policy: Leakage ALARM
| Field | Value |
|---|---|
| Event Policy Name | Didactum LEAKAGE ALARM |
| Severity | Critical (5) |
| Collection Object | Leakage Sensor 01 |
| Threshold Type | Greater Than |
| Threshold Value | 0 (from value 1 = water = Critical) |
| Event Message | LEAKAGE ALARM: Didactum water sensor – Value: %V (1=water detected!) |
Event Policy: Humidity
| Field | Value |
|---|---|
| Event Policy Name | Didactum Humidity High |
| Severity | Major (4) |
| Collection Object | Humidity Sensor 01 |
| Threshold Type | Greater Than |
| Threshold Value | 80 |
| Event Message | Didactum Humidity: %V % (warning threshold 80%) |
Event Policy: Door Contact & Smoke Detector
| Policy Name | Collection Object | Threshold | Severity |
|---|---|---|---|
| Didactum Door Contact Opened | Door Contact 01 | > 0 | Minor (3) |
| Didactum SMOKE DETECTOR ALARM | Smoke Detector 01 | > 0 | Critical (5) |
11. PowerPack for Didactum Integration
PowerPacks contain SNMP Dynamic Applications and Device Classes and can be downloaded from the ScienceLogic Support Site. They enable easy distribution and reuse of monitoring configurations.
Create Didactum PowerPack (for distribution)
System → Manage → PowerPacks → Create New PowerPack Name: Didactum Monitoring System Version: 1.0 Description: Complete SNMP Monitoring for Didactum Environmental Monitoring → Save
Add Content to PowerPack
PowerPack → Click "Add Content" → add the following elements: ✅ Device Class: Didactum Monitoring System ✅ Credential: Didactum SNMPv2c (Template) ✅ Dynamic Application: Didactum Environmental Sensors – Performance ✅ Dynamic Application: Didactum Environmental Sensors – Configuration ✅ Event Policy: Didactum Temperature Warning ✅ Event Policy: Didactum Temperature Critical ✅ Event Policy: Didactum LEAKAGE ALARM ✅ Event Policy: Didactum Humidity High ✅ Event Policy: Didactum Door Contact Opened ✅ Event Policy: Didactum SMOKE DETECTOR ALARM → Save PowerPack
Export PowerPack
PowerPack → "Export" → .em7 file is created → Importable on other SL1 systems: System → Manage → PowerPacks → Import
12. Alerting & Email Notification
Step 1 – Create Action Policy for Email Sending
Registry → Events → Action Policies → Create New Action Policy
| Field | Value |
|---|---|
| Action Policy Name | Didactum Email Alert |
| Action Type | Send Email |
| From | sl1@yourdomain.com |
| To | admin@yourdomain.com |
| Subject | [SL1 Didactum] %E – %D: %M |
| Message | Event: %E\nDevice: %D (%I)\nSeverity: %S\nTime: %T\nMessage: %M |
Step 2 – Configure SMTP Settings
System → Settings → Email Settings SMTP Server: mail.yourdomain.com SMTP Port: 587 Use TLS: Yes From Address: sl1@yourdomain.com Auth User: sl1@yourdomain.com Auth Password: YourPassword → Save → Click "Send Test Email"
Step 3 – Link Event Policy with Action Policy
Registry → Events → Event Policies → Edit "Didactum LEAKAGE ALARM" → Tab "Actions" → "Add Action": Select "Didactum Email Alert" → Trigger: "When event fires" → Save
Repeat for all Didactum Event Policies.
Step 4 – Check Events in Event Console
Registry → Events → Event Console → Filter: Device = Didactum-Monitor-01 → All active events are displayed here
13. SNMP OID Reference
All Didactum OIDs start with .1.3.6.1.4.1.46501 (older firmware) or .1.3.6.1.4.1.39052 (newer models). The sensor ID is appended at the end.
OID Fields per Sensor
| Field | Meaning | Example |
|---|---|---|
| .1.x.SENSOR_ID | Sensor ID | .1.3.6.1.4.1.46501.5.1.1.1.101001 |
| .5.x.SENSOR_ID | Sensor Name | .1.3.6.1.4.1.46501.5.1.1.5.101001 |
| .6.x.SENSOR_ID | Status (0=OK, 1=Alarm, 2=No Signal) | .1.3.6.1.4.1.46501.5.1.1.6.101001 |
| .7.x.SENSOR_ID | Measured Value (current) | .1.3.6.1.4.1.46501.5.1.1.7.101001 |
Sensor Types with OIDs and SL1 Event Policy Thresholds
| Sensor Type | Sensor ID | OID Measured Value | OID Status | SL1 Threshold |
|---|---|---|---|---|
| Temperature Sensor (digital) | 101001 | .1.3.6.1.4.1.46501.5.1.1.7.101001 | .1.3.6.1.4.1.46501.5.1.1.6.101001 | Warning: > 280 / Crit: > 350 (raw value × 10) |
| Temperature Sensor (analog) | 201001 | .1.3.6.1.4.1.39052.5.2.1.7.201001 | .1.3.6.1.4.1.39052.5.2.1.6.201001 | Warning: > 280 / Crit: > 350 (× 10) |
| Water Sensor / Leakage | 107001 | .1.3.6.1.4.1.46501.5.1.1.7.107001 | .1.3.6.1.4.1.46501.5.1.1.6.107001 | Crit: > 0 (from 1 = water detected) |
| Humidity | 102001 | .1.3.6.1.4.1.46501.5.1.1.7.102001 | .1.3.6.1.4.1.46501.5.1.1.6.102001 | Warning: > 80 / Crit: > 90 (direct %) |
| Potential-free Contact | 101003 | .1.3.6.1.4.1.39052.5.1.1.7.101003 | .1.3.6.1.4.1.39052.5.1.1.6.101003 | Warning: > 0 (from 1 = active) |
| Door Contact | 104001 | .1.3.6.1.4.1.46501.5.1.1.7.104001 | .1.3.6.1.4.1.46501.5.1.1.6.104001 | Warning: > 0 (from 1 = open) |
| Smoke Detector | 106001 | .1.3.6.1.4.1.46501.5.1.1.7.106001 | .1.3.6.1.4.1.46501.5.1.1.6.106001 | Crit: > 0 (from 1 = Alarm) |
Find Sensor ID: In the Didactum Web Interface under System Tree → Select Sensor → Details. This ID is appended to the end of the OID.
Temperature Thresholds in SL1: Didactum delivers temperature values as raw value × 10. 28.0 °C = OID value 280. All SL1 Event Policy threshold values must therefore be specified × 10 (280 instead of 28; 350 instead of 35).
MIB Prefix per Model: Older devices use .1.3.6.1.4.1.46501, newer ones possibly .1.3.6.1.4.1.39052. Obtain the exact OIDs from the MIB file of your device.
14. Test & Troubleshooting
SNMP Walker in SL1 Web Interface
Registry → Devices → Device Manager → Didactum-Monitor-01 → Tab "Toolbox" → SNMP Walker → OID: .1.3.6.1.4.1.46501.5.1.1 → Execute Walk → All sensor values appear in the result table
Manually Collect Dynamic Application
Device Manager → Didactum-Monitor-01 → Tab "Dynamic Applications" → Select Dynamic Application → Click "Collect Now" → Collection result appears immediately under "Recent Collections"
Check Device Performance Graphs
Device Manager → Didactum-Monitor-01 → Tab "Performance" → Select "Temperature Sensor 01 (Raw Value)" → Trend graph appears (raw value × 10 = Celsius after conversion)
Error Messages and Solutions
| Problem | Cause & Solution |
|---|---|
| Device after discovery without Device Class | SysObjectID does not match → Check Device Class SysObjectID; run discovery again |
| Dynamic Application collects no data | SNMP Credential wrong; OID not supported → Test with SNMP Walker; check community |
| Temperature value 10× too high in graphs | Correct – this is the raw value. Specify Event Policy threshold × 10 (280, 350) |
| Event Policy never triggers | Dynamic Application not linked to device; threshold too high; DA not active |
| MIB import fails | Missing MIB dependencies → Import standard MIBs (RFC, SNMPv2) first |
| No email on alarm | Check SMTP settings; Action Policy assigned to Event Policy? Send test email |
| Discovery fails | Data Collector has no access; UDP 161 blocked; Credential wrong |
View SL1 Logs
System → Tools → System Logs → Dynamic Application Log → Filter: Application = "Didactum Environmental Sensors – Performance" → Errors and collection results are logged System → Tools → System Logs → Event Log → Filter: Device = Didactum-Monitor-01 → All events of the device are displayed
15. Final Checklist
Didactum Device
- SNMP enabled (v2c or v3)
- Community String set (not "public"): didactum_sl1
- Trap Receiver IP set to SL1 Data Collector
- MIB file downloaded
- snmpwalk from SL1 Data Collector successful
SL1 Configuration
- SNMP Credential "Didactum SNMPv2c" created
- MIB file imported (System → Tools → Import MIB)
- OID Browser: Didactum OIDs visible (enterprises → 46501)
- Device Class "Didactum Monitoring System" created with SysObjectID
- Discovery Session executed: Device appears in Device Manager
- Device received correct Device Class assignment
Dynamic Applications
- Performance DA "Didactum Environmental Sensors – Performance" created
- Collection Objects for Temperature, Leakage, Humidity, Door, Smoke created
- Discovery Object for automatic assignment defined
- DA assigned to Device Class
- "Collect Now": First values collected successfully
- Performance graph shows trend data
Event Policies & Alerting
- Event Policy for Temperature Warning (Threshold 280) created
- Event Policy for Temperature Critical (Threshold 350) created
- Event Policy for Leakage Critical (Threshold > 0) created
- Event Policy for Humidity created
- SMTP settings configured, test email received
- Action Policy "Didactum Email Alert" created
- Action Policy assigned to all Didactum Event Policies
- Test event triggered and email received
PowerPack
- PowerPack "Didactum Monitoring System" created and all elements added
- PowerPack exported as .em7 file (for other SL1 instances)