---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/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


---

# Verify your log sources

# Verify your log sources {#ariaid-title1}

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

Verify that all your log sources are present and active after Health Log Analytics tagging has assigned a log to a service instance and
components, and has automatically mapped the log to a source.

## Before you begin

Role required: evt_mgmt_admin

## Procedure

1. Navigate to AllHealth Log AnalyticsData InputLog Sources.  
   The Log Sources table provides information about the sources created when you mapped the streaming data. The table lists these sources by service instance.  
   {#hla-log-sources-review__table_wx1_kt1_gnb__entry__2}

   | Column | Description |
   |-|-|
   | Service instance | The service instance. Service instances represent large or complete business processes. A single service instance can consist of multiple components, whereas different service instances can include the same components. |
   | Component | The components comprising the service instance. Components represent small technical parts or business processes. Typically, they represent Configuration Items (CIs). Several components are often clustered together in a single service instance. |
   | Status | The status of the log source: Active or Inactive. The Active status indicates that logs streamed into the system from this source in the last hour. |
   | Created | The creation date and time of this log source. |
   | Last event time | The last time logs streamed into the system from this source. |
   [ ]

   {#hla-log-sources-review__table_wx1_kt1_gnb}
2. Make sure that the system has created all your log sources.
3. Verify the creation, status, and log samples of a specific source in the source record.  
   Note:  
   Because auto-mapping can map log data to multiple sources, be sure to verify this information per source.
4. If a log source is missing, add it.
   1. Navigate to Health Log AnalyticsData InputData Input Mapping.
   2. Use the JavaScript function to manually map a log sample to the correct service instance, component, and source type.  
      For more information, see [Map raw log data](https://www.servicenow.com/docs/ENjBmAW1AM2qvvmJSA_YiQ "Mapping raw log data that streams into your instance determines how the data is handled. Health Log Analytics automatically structures logs, creates metrics for anomaly detection, and presents alerts based on how your data is tagged.").
   3. Navigate back to the Log Sources page and verify that the status of the new log source is Active.

   {#hla-log-sources-review__substeps_anc_fyp_h4b}  
   The system creates a log source.
5. Make sure that the status of all your log sources is Active.  
   If the status of a source is Inactive, double-click it and change it to Active manually.
6. Select Update.
**Related tasks**   

* [Delete a log source](https://www.servicenow.com/docs/_kcISCdKE0jwoD8myS~lMw "Delete a log source with or without its associated log data in Health Log Analytics.")
* [Stop extraction of unneeded log data](https://www.servicenow.com/docs/N_rY673APoTEWMVW68Toqg "If an extracted string of data is not descriptive enough or contains redundant text or information, you can set Health Log Analytics to stop extracting such data from your logs.")
* [Ensure extraction of specific log data](https://www.servicenow.com/docs/kbW5ugyUh7Lu_7W9ed7uow "Set Health Log Analytics to extract specified terms from fields and map them to specific components.")

*[\>]: and then