The Teleseer Custom CSV Parser enables uploading a comma-separated value (CSV) formatted file with additional asset information. When a row matches a project asset by IP address or MAC address, that project asset receives either a new tag or an attribute update (when the value corresponds to one of several reserved column names).
The parser supports two CSV formats: Hardware List and Splunk.
Hardware List CSV
- Required Columns (case-insensitive)
machine nameip addressmanufacturer
Note: All three columns must be present in the CSV, but in any given row onlyip addressis required to have a value;machine nameandmanufacturercan be left blank.
How It Works:
- Assets are matched by IP address
- The following columns map to specific asset attributes:
"machine name"→hostname"ip address"→ip(adds but does not overwrite existing values)"manufacturer"→manufacturer
- Any additional columns are added as tags in
column_name: valueformat.
Splunk CSV
- Required Columns (case-insensitive)
osdnsfunctionipmacnt_host
Note: All listed columns must be present in the CSV, but in any given row at least one ofipormacmust have a value; all other columns are optional and can be left blank.
How It Works:
- Assets are matched by IP address or MAC address.
- The following columns map to specific asset attributes:
"os"→OS Name"dns"→hostname"function"→roles"ip"→ip(does not overwrite existing values)"mac"→mac(does not overwrite existing values)"nt_host"→hostname
- If both
dnsandnt_hostare present, they are added as multiple hostnames for the asset. - Any additional columns are added as tags in
column_name: valueformat.
General Notes
- Column headers are case-insensitive.
- Extra columns are never ignored — they are always added as tags in
column_name: valueformat. - IP and MAC values will not overwrite values that already exist on a matched asset.
Example CSVs and Interpretation
Hardware List Example
Interpretation of Hardware List Rows
- Row 1:
- Match: Asset matched by
IP address = 192.168.1.10. - Mapped Fields:
hostname→ Server1manufacturer→ Dell
- Tags Added:
location: Datacenter Arack: Rack 1
- Match: Asset matched by
- Row 2:
- Match: Asset matched by
IP address = 192.168.1.11. - Mapped Fields:
hostname→ Server2manufacturer→ HP
- Tags Added:
location: Datacenter Brack: Rack 2
- Match: Asset matched by
- Row 3:
- Match: Asset matched by
IP address = 192.168.1.12. - Mapped Fields:
hostname→ Server3manufacturer→ Lenovo
- Tags Added:
location: Datacenter Arack: Rack 3
- Match: Asset matched by
- Row 4:
- Match: Asset matched by
IP address = 192.168.1.13. - Mapped Fields:
hostname→ Server4
- Tags Added:
location: Datacenter Brack: Rack 4
- Match: Asset matched by
- Row 5:
- Match: Asset matched by
IP address = 192.168.1.14. - Mapped Fields:
manufacturer→ Framework
- Tags Added:
location: IT Build Bench
- Match: Asset matched by
Splunk Example
Interpretation of Splunk Rows
- Row 1:
- Match: Asset matched by
IP = 192.168.1.11orMAC = 00:1A:2B:3C:4D:5E. - Mapped Fields:
OS Name→ Linuxhostname→ server1.comroles→ Web Servermac→ 00:1A:2B:3C:4D:5E
- Tags Added:
department: ITapp: Apache
- Match: Asset matched by
- Row 2:
- Match: Asset matched by
IP = 192.168.1.12orMAC = 00:1A:2B:3C:4D:5F. - Mapped Fields:
OS Name→ Windowshostname→ server2.comroles→ File Servermac→ 00:1A:2B:3C:4D:5F
- Tags Added:
department: Financeapp: SMB
- Match: Asset matched by
- Row 3:
- Match: Asset matched by
IP = 192.168.1.13orMAC = 00:1A:2B:3C:4D:60. - Mapped Fields:
OS Name→ macOShostname→ server3.comroles→ Dev Servermac→ 00:1A:2B:3C:4D:60
- Tags Added:
department: Engineeringapp: Xcode
- Match: Asset matched by
- Row 4:
- Match: Asset matched by
IP = 192.168.1.14 - Mapped Fields:
hostname→ server4.com
- Tags Added: None
- Match: Asset matched by
- Row 5:
- Match: Asset matched by
MAC = 00:1A:2B:3C:4D:6Y - Mapped Fields:
OS Name→ Linuxhostname→ server5.comroles→ PBX Servermac→ 00:1A:2B:3C:4D:6Y
- Tags Added: None
- Match: Asset matched by