Skip to content

How to get the logs

Last updated: July 16, 2026

When you contact Layer2 support about a ShArc problem, we usually need two sets of logs:

  1. Log Analytics export – a structured, filterable record of ShArc operations such as jobs, files, and errors. This provides a useful overview and can easily be shared as a CSV file.
  2. Blob storage logs – the full verbose logs, including detailed communication between ShArc and SharePoint. These logs contain information that is not sent to Log Analytics and are often essential for diagnosing a problem.

Please provide both sets of logs unless Layer2 support asks you for only one of them.

Part 1 – Export the logs from Log Analytics

1. Open your Log Analytics workspace

  1. Sign in to the Azure Portal.

  2. Search for Log Analytics Workspaces.

Azure Portal search showing Log Analytics Workspaces in the search results
Search for Log Analytics Workspaces in the Azure Portal.
  1. Open the workspace that belongs to your ShArc server. Its name is your ShArc web server prefix with la- in front of it. For example, if your ShArc server is contoso-sharc, the workspace is named la-contoso-sharc.

Azure Log Analytics workspace whose name starts with la-
Open the Log Analytics workspace associated with your ShArc server.
  1. In the left-hand menu, select Logs. Close the Queries hub window if it opens.

Logs option in the Azure Log Analytics menu and the Queries hub window
Open Logs and close the Queries hub window if necessary.

2. Run the query

If the query editor opens in Simple mode, switch it to KQL mode.

Azure Log Analytics mode selection showing the KQL mode option
Switch the query editor to KQL mode.

Paste the following query into the editor and run it. The query returns all ShArc log messages while filtering out authentication tokens and sign-in requests so that no secrets are included in the export:

union isfuzzy=true ( AppServiceConsoleLogs | where isnotempty(ResultDescription) | where not(ResultDescription matches regex @"\bey[A-Za-z0-9_-]+\b") | where not(ResultDescription has "RequestBody: grant_type=") | order by TimeGenerated asc | serialize | extend IsStart = iff( ResultDescription matches regex @"^(info|warn|fail|dbug|trce|crit):" or ResultDescription matches regex @"^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2} \[", 1, 0) | extend BlockId = row_cumsum(IsStart) | summarize StartTime = min(TimeGenerated), EndTime = max(TimeGenerated), CombinedLog = strcat_array(make_list(ResultDescription, 1000), "\n") by BlockId | project StartTime, EndTime, FileId = "", CombinedLog ), ( ShArcLogs_CL | where isnotempty(LogMessage) | where not(LogMessage matches regex @"\bey[A-Za-z0-9_-]+\b") | where not(LogMessage has "RequestBody: grant_type=") | project StartTime = TimeGenerated, EndTime = TimeGenerated, FileId = tostring(FileId), CombinedLog = LogMessage ) | order by StartTime desc | project StartTime, EndTime, FileId, CombinedLog | limit 500000

3. Set the time range and run the query

  1. At the top of the query editor, set the time range to a period that covers when the problem occurred.

Custom time range picker in Azure Log Analytics
Select a time range that includes the period in which the problem occurred.
  1. Select Run.

4. Export the result as CSV

Select Export or Share, then choose Export to CSV (displayed columns) and save the CSV file.

Azure Log Analytics Share menu showing Export to CSV displayed columns
Export the displayed Log Analytics columns as a CSV file.

Part 2 – Download the verbose logs from Blob Storage

ShArc writes its detailed logs, including the full communication with SharePoint, to Azure Blob Storage. These logs are not available in Log Analytics, so please download them as well.

Where the logs are stored

  • Storage account: Your ShArc storage account. This is normally the same storage account used by ShArc unless a separate logging account was configured for your environment.
  • Container: layer2-logs
  • File names: <your-sharc-server-name>-<date and time>-<id>.txt. ShArc creates one file per server instance per day.
  • Compression: Files older than approximately one hour are automatically compressed, renamed to ...-.txt.gz, and moved to the Cool storage tier. Both .txt and .txt.gz files are valid. Download whichever files cover the time when the problem occurred. Extract the .gz files before viewing them.
  • Format: Each line is a single log entry in JSON format. You can open the extracted .txt files in any text editor.

How to download the logs

Use whichever method is most convenient:

  • Azure Portal: Open the storage account, then go to Containers > layer2-logs. Select the checkboxes of the files that cover the time of the problem. Open the menu or right-click one of the selected files, choose Download, and confirm the download if Azure asks about downloading multiple files.

  • Azure Storage Explorer: Connect to the storage account, open the layer2-logs container, and download the relevant files.

  • AzCopy: This method is recommended when you need to download many files at once.

If AzCopy is not already installed, install it with Windows Package Manager:

winget install Microsoft.Azure.AZCopy.10

Alternatively, download AzCopy for Windows, extract the downloaded archive, and run azcopy.exe from the extracted folder.

After installing AzCopy, open a new terminal so that azcopy is available on your system path.

Sign in with your Azure account. Note that the command is azcopy login, not az login:

azcopy login

Then download the log files for your ShArc server:

azcopy copy "https://<storage-account-name>.blob.core.windows.net/layer2-logs/*" "./sharc-logs" --include-pattern "<your-sharc-server-name>-*"

The --include-pattern "<your-sharc-server-name>-*" parameter downloads both the uncompressed .txt files and the compressed .txt.gz files for your server.

Your Azure account requires the Storage Blob Data Reader role on the storage account. Being a subscription or storage account Owner is not sufficient on its own. The Owner role grants management access, but not access to the blob data. An Owner can assign the required role under the storage account's Access control (IAM) page.

The files are saved in the destination folder specified in the command. In this example, the folder is ./sharc-logs and is created under the directory from which you run the command.

Use an absolute path if you want the files to be saved in a specific location:

azcopy copy "https://<storage-account-name>.blob.core.windows.net/layer2-logs/*" "C:\Temp\sharc-logs" --include-pattern "<your-sharc-server-name>-*"

To download a narrower set of logs, extend the pattern with the date and, optionally, the hour. The timestamp in the file name uses the format yyyy-MM-ddTHH-mm-ss and is recorded in UTC.

For example, the following command downloads all logs from April 3, 2026:

azcopy copy "https://<storage-account-name>.blob.core.windows.net/layer2-logs/*" "./sharc-logs" --include-pattern "<your-sharc-server-name>-2026-04-03T*"

The following command downloads all logs created between 13:00 and 13:59 UTC on April 3, 2026:

azcopy copy "https://<storage-account-name>.blob.core.windows.net/layer2-logs/*" "./sharc-logs" --include-pattern "<your-sharc-server-name>-2026-04-03T13-*"

Only download the files for the day or days on which the problem occurred. You do not need to download the entire container.

Privacy note: The verbose logs may contain file and library URLs. Authentication tokens and sign-in secrets are redacted by ShArc before anything is written to the logs.

Part 3 – Send everything to support

  1. Put the CSV export from Part 1 and the blob log files from Part 2 into a single .zip file. Include any other useful material, such as screenshots or screen recordings.

Example Azure web server metrics screenshot that may be included with the support files
Include any additional information that may help, such as screenshots or web server metrics.
  1. Upload the .zip file using the following link: Upload zipped ShArc log files.

  2. Send an email to support@layer2solutions.com with a subject line in the following format:

ShArc | <your name or company> | <short description of the issue>

In the email, please describe:

  • What you did – the steps you took.
  • What you expected to happen.
  • What actually happened.

This information helps the Layer2 support team reproduce and resolve the issue as quickly as possible.

RELATED ARTICLES