- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Import entities from csv in splunk ITSI
Hi,
I want to import the entities via csv to entity management in Splunk ITSI,
so please help me with this.
Thanks
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @skramp,
if you are talking about this post , i am the post writer, thought to post the question in Splunk community to get support in this.
Below is one of the CSVs i have tried import:
ServiceTitle;ServiceDescription;DependentServices;
Splunk;;SHC | IND;
SHC;;Server1;
IND;;server2;
server1;;;
server2;;;
in the 1st environment it gives:
File preview : 0 total lines
in the 2nd environment, it gets imported successfully, displaying all the rows.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

haha, so you are the same one, awesome!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

In Splunk IT Service Intelligence (ITSI), you can import entities via CSV to Entity Management using the following steps:
Prepare Your CSV File:
- Make sure your CSV file contains the necessary information for each entity, such as title, identifier, and any other relevant fields.
- The CSV file should have a header row with column names.
Access Entity Management:
- Log in to your Splunk instance and navigate to ITSI.
- In the ITSI main menu, go to Configure > Entity Management.
Open Import Wizard:
- Click on Import Entities.
Select CSV File:
- Click on Browse or similar, depending on your system, to locate and select your CSV file.
Map Fields:
- ITSI will attempt to automatically map fields from your CSV file to ITSI entity fields. Review the mapping to ensure accuracy.
- If needed, manually map fields by dragging the appropriate CSV columns to the corresponding ITSI fields.
Preview and Validate:
- Preview the entities to ensure they are correctly mapped and that the data looks accurate.
- Validate the data to check for any errors or missing information.
Complete the Import:
- If everything looks correct, proceed with the import by clicking Finish or a similar button.
- Splunk ITSI will process the CSV file and import the entities into Entity Management.
Verify Import:
- After the import is complete, verify that the entities are visible in the Entity Management interface.
It's important to note that the exact steps and options might vary slightly depending on the version of Splunk ITSI you are using. Always refer to the official Splunk documentation for your specific version for the most accurate and up-to-date information.
For more information:
https://docs.splunk.com/Documentation/ITSI/latest/Entity/ImportCSV#Steps
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am following this to import multiple services along with their dependencies, and below is the sample excel CSV i am trying to import, utf-8 encoded :
Service Title | Service Description | Dependent Services | Splunk | SHC | IND | SHC | Server1 | IND | server2 | server1 | server2 | But when the upload is finished, the file preview shows 0 total lines as in the below screenshot: When i tried to do the same file import in another splunk environment, it went well. Given that i am admin in both environments and both environments with versions as below:
|
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

A few days ago I've seen someone in the Slack Usergroup who also had a problem with ITSI 4.18.1, but just on one of his environments. Can you explain your error a little more specific, do you get an error message or does Splunk only tells you there is no content in your csv? Can you please try to import your csv on a different Splunk environment, maybe which is in a different version? Just to check.
