> ## Documentation Index > Fetch the complete documentation index at: https://docs.runconverge.com/llms.txt > Use this file to discover all available pages before exploring further. # Monitoring > Test and monitor your Converge Integration export const IconText = ({name, text, iconSource = "mintlify", iconLocation = "before", iconType = "solid"}) => { const sourceUrl = iconSource === 'local' ? `url('/images/icons/${name}.svg')` : `url('https://mintlify.b-cdn.net/v6.5.1/${iconType}/${name}.svg')`; return <>
{iconLocation === 'before' &&
} {text} {iconLocation === 'after' &&
}
; }; ## Overview Converge provides the following tools to monitor and debug whether your Sources are working correctly: * [Source Logs](#source-logs) * [Source Warnings](#source-warnings) * [Pixel Monitor](#pixel-monitor) *** ## Source Logs Converge stores detailed logs of every event that gets sent to Converge including [event properties](/sources/converge-spec), [profile properties](/sources/source-concepts#profile-properties) and [aliases](/sources/source-concepts#aliases). ### Where to find Source Logs 1. Navigate to the [Sources Tab](https://app.runconverge.com/-/sources) in your Converge dashboard 2. Click on the Source you want to debug pick a source 3. Click on the **Logs** tab to see the logs pick logs 4. Click on any of the Log Lines to inspect the **event properties**, **profile properties**, **aliases**, etc. ### Filter through the logs * **By Event Name**: You can select a subset of events to show in the log by clicking on **Select events** and then ticking the relevant events. * **By Date**: You can use the date picker in the right top corner to select log lines from a particular date range. ### Exporting logs 1. Navigate to the [Sources Tab](https://app.runconverge.com/-/sources) in your Converge dashboard 2. Click on the Source you want to debug pick a source 3. Click on the **Logs** tab to see the logs pick logs 4. You can export your log selection to CSV using the -button in the right top corner. Log entries are limited to 10,000 lines. *** ## Source Warnings Converge will automatically flag when events do not conform with the [Converge event spec](/sources/converge-spec) and give you pointers as to how to modify your events to be compliant with the spec. ### Where to find Source Warnings 1. Navigate to the [Sources Tab](https://app.runconverge.com/-/sources) in your Converge dashboard 2. Click on the Source you want to see logs from pick a source 3. Click on the **Warnings** tab to see the appropriate warnings. Each warning includes information as to what `property` is malformed, as well as detailed log lines to inspect. see warning info *** ## Pixel Monitor ### What is a Pixel Monitor The Pixel Monitor verifies that your Converge tracking pixel is installed and working on your websites. It loads your site in a browser and checks for the Converge tracking script. The monitor will display one of two statuses: * **Pixel Installed**: The Converge pixel was successfully detected on your website * **Pixel Not Found**: The monitor was unable to detect the Converge pixel The monitor loads your site through a **US-based browser**. It may not verify sites that use **geographic redirects** or require **user consent** before loading tracking scripts. ### Where to find the Pixel Monitor 1. Navigate to the [Sources Tab](https://app.runconverge.com/-/sources) in your Converge dashboard 2. Check the **Pixel Monitor** tab for the status of each source. Note that pixel monitor checks can only be performed on client-side sources. pick a source 3. Click on the Source for which you would like to view monitoring details. 4. Access the **Monitors** tab to view pixel monitoring status. Each monitor performs automated checks every 24 hours to verify proper client-side pixel implementation. see monitors ### How to create a Pixel Monitor 1. Click **Create Monitor** to add a new website monitoring configuration. click create a monitor 2. Configure individual monitors for each website where the client-side pixel is deployed. input website url