---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Import a data input to a target instance

# Import a data input to a target instance {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Import a Health Log Analytics data input configuration that you've
exported from another instance as an update
set.

## Before you begin

For an overview of this feature, see [Migrating Health Log Analytics data input configurations between instances](https://servicenow-prod.fluidtopics.net/h8zgh5ncl977JqJF4yCXKQ "Export a Health Log Analytics data input and source types configuration as an update set and import it to a different ServiceNow instance. In the target environment, you can use the migrated data input for streaming and processing log data. This functionality saves time and reduces possible errors by avoiding the need to configure the settings again on the target instance.").

Before performing this procedure, export the data input to an update set. For more
information, see [Export a data input configuration](https://servicenow-prod.fluidtopics.net/3r01urrlEb83r5tH1ZuZvQ "Export the configuration of a Health Log Analytics data input with or without the related source types to an update set. You can then import the update set to the target environment.").

Role required: admin

## Procedure

1. On the target instance, import the update set that contains the data input configuration.
   1. Navigate to AllSystem Update SetsRetrieved Update Sets.
   2. In the Related Links, select Import Update Set from XML.
   3. Select Choose file and open the update set XML file from the Downloads folder.
   4. Select Upload.  
      The update set is uploaded to the instance and appears in the Retrieved Update Sets list in the Loaded state.
   {#hla-data-input-import__substeps_ums_2ns_v5b}
2. Identify and address errors in the update set.
   1. In the Retrieved Update Sets list, open the update set record.
   2. Select Preview Update Set Batch to detect errors.  
      The Batch Update Set Preview dialog indicates failure, which is expected behavior.
   3. Close the dialog and resolve the errors in the Update Set Preview Problems related list.  
      For more information, see [Preview a
      remote update set](https://www.servicenow.com/docs/access?context=t_PreviewARemoteUpdateSet&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US).  
      You can ignore errors that start with 'Could not find a record in \[table\]' for the following tables:
      * aws_credentials
      * azure_sas_credentials
      * azure_service_principal
      * basic_auth_credentials
      * cmdb_ci_service_auto - Service instance
      * ecc_agent - MID
      * ecc_agent_cluster - MID Server Cluster
      * kafka_ssl_credentials
      * sn_occ_data_input_preprocess_example
      * sn_occ_data_input_preprocess_example_row
      * sn_occ_gcp_credentials
      * sn_occ_mapper_example
      * sn_occ_source_type_examples
      * sn_occ_source_type_structure_data
      {#hla-data-input-import__ul_mx2_z1z_v5b}
   4. Select the errors that you ignored and then select the Select All check box.
   5. From the Actions on selected rows... drop-down menu, choose Accept remote update.
   6. In the Preview Problems for Batch related list, select all remaining errors and accept the remote update as explained in the earlier steps.
   {#hla-data-input-import__substeps_fxq_bks_v5b}
3. When all errors in the update set have been resolved, select Commit Update Set Batch.  
   The imported data input appears on the Data Inputs list. The import includes mapping settings and all other relevant configuration.
4. In the imported data input, configure the following.  
   * The MID Server to which the logs stream.
   * Credentials.  
     Note:  
     Whether you need to configure credentials depends on the data input that you've imported. For example, you must configure Amazon Web Services (AWS) credentials for Amazon CloudWatch and Amazon S3 data inputs.
   * (Optional) The service instance to which to bind the log data.

   {#hla-data-input-import__ul_cmz_smg_y5b}

   For more information, see the configuration documentation for the relevant
   data input: [Set up data inputs for Health Log Analytics manually](https://servicenow-prod.fluidtopics.net/~9C8cvT1lkIgNfh78QVxGQ "Set up your Health Log Analytics data inputs for Health Log Analytics manually. Data input configuration is an essential step in setting up the Health Log Analytics application.").

## Result

You can begin using the data input for streaming and processing log data.

*[\>]: and then