---
title: "Monitor an Edge Filer Using Datadog"
slug: "monitor-an-edge-filer-using-datadog"
updated: 2025-05-29T08:52:38Z
published: 2025-05-29T08:52:38Z
canonical: "kb.ctera.com/monitor-an-edge-filer-using-datadog"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.ctera.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitor an Edge Filer Using Datadog

You can monitor a CTERA Edge Filer using a Datadog agent running on a Windows PC.

The following describes how to monitor a CTERA Edge Filer upload queue.

## Requirements

- CTools is a CTERA toolbox to check, manage, and run bulk operations, and automate tasks across multiple CTERA Edge Filers and Portals. CTools is available from github: [https://github.com/ctera/ctools/releases](https://github.com/ctera/ctools/releases).
- PowerShell on a Windows PC.
- The Datadog agent installed on the Windows PC, as described in [https://docs.datadoghq.com/agent/basic_agent_usage/windows/?tab=standardinstallation](https://docs.datadoghq.com/agent/basic_agent_usage/windows/?tab=standardinstallation).
  - Run the following command: `Start-Process -Wait msiexec -ArgumentList '/qn /i datadog-agent-7-latest.amd64.msi APIKEY="<apikey>" SITE="datadoghq.com" HOSTNAME="<hostname>"'`  

where:  

**SITE** is the website (some licenses default to EU).  

**hostname** is the host to show in Datadog. If this is not configured, it should use the hostname of the datadog-agent machine.  

**apikey** is the appropriate APIKEY.

## Monitoring an Edge Filer

**To monitor and edge filer:**

1. Move **ctools.exe** to `C:\Users\<Username>\Documents\PowerShell`  

where *Username* is your user name. For example, `C:\Users\Administrator.WINSERVER22\Documents\PowerShell`.
2. Create the following script in PowerShell:

```
# Get the folder location for this script
$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Definition

# 1) Generate a CSV
$ctoolsPath = Join-Path $scriptDir "ctools.exe"
$outputCsv = Join-Path $scriptDir "output.csv"
& $ctoolsPath show_status portal.ctera.me admin ctera321 $outputCsv all_tenants False

# 2) Parse the CSV and build JSON objects mapping the required fields

$results = Import-Csv -Path $outputCsv | ForEach-Object {
    # Extract CPU and Mem from "CPU: 0% Mem: 15%" string
    if ($_.'Current Performance' -match 'CPU:\s*(\d+%)\s+Mem:\s*(\d+%)') {
        $cpu = $matches[1]
        $mem = $matches[2]
    } else {
        $cpu = ""
        $mem = ""
    }

    # Add the timestamp first
    [ordered]@{
        timestamp       = (Get-Date -Format "o")
        filerName       = $_.'Filer Name'
        FilesUploading  = [int] $_.'uploadingFiles'
        CloudSyncStatus = $_.'CloudSync Status'
        ADDomainStatus  = $_.'AD Domain Status'
        CPU             = $cpu
        Mem             = $mem
    }
}

# 3) Define the log file path relative to the script directory
$logFile = Join-Path $scriptDir "cloudsync_monitor.log"

# 4) Remove the previous log file if it exists
if (Test-Path $logFile) {
    Remove-Item $logFile
}

# 5) Write each JSON object to the log
foreach ($record in $results) {
    $jsonLine = $record | ConvertTo-Json -Compress -Depth 10
    Add-Content -Path $logFile -Value $jsonLine
}

# 6) Set permissions to allow read access to all users
$acl = Get-Acl $logFile
$accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule("Everyone", "Read", "Allow")
$acl.AddAccessRule($accessRule)
Set-Acl -Path $logFile -AclObject $acl
```
3. Save the script as `cloudsync_monitor.ps1` in `C:\Users\<Username>\Documents\PowerShell`  

where *Username* is your user name. For example, `C:\Users\Administrator.WINSERVER22\Documents\PowerShell`.
          **Note**

          

You can test the script in PowerShell by running the following command: `& "$env:USERPROFILE\Documents\PowerShell\cloudsync_monitor.ps1"`
4. Check **cloudsync_monitor.log** to ensure it is logging expected information, including **filerName**, **FilesUploading**, and **ADDomainStatus**.
5. Configure logging in the Datadog agent.
  1. Modify the `C:\ProgramData\Datadog\datadog.yaml` file by adding or uncommenting `logs_enabled` and setting the value to `true`.
  2. Restart the Datadog agent service using the following command: `restart-service datadogagent -Force` and run the following to ensure that logging is enabled: `agent status | findstr -i "logs"`
  3. Add a logs configuration file:
    1. Create a folder: `mkdir "C:\ProgramData\Datadog\conf.d\cloudsync_monitor_powershell.d\"`
    2. Create and edit the logs configuration file: `notepad C:\ProgramData\Datadog\conf.d\cloudsync_monitor_powershell.d\conf.yaml`
    3. Populate the file with the following:

```
logs:
  - type: file
    path: <Username>\cloudsync_monitor.log
    service: cloudsync_monitor_powershell
    source: powershell
```

where *path* is the full path to the folder and *Username* is your user name. For example, `C:\Users\Administrator.WINSERVER22\Documents\PowerShell`
6. Access the Datadog user interface and add a log source.
  1. Hover over **Logs** and click **Add a log source**.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-NW84CULU.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
  2. Select **Server > Custom Files**.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-CENL0E2Z.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
  3. Populate as follows:  

**Path** – `/var/log/cloudsync_monitor.log`  

**Service** – `cloudsync_monitor_powershell`  

**source** – `powershell`
  4. Save by clicking **Explore your logs**.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-V86H0390.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
7. Verify that logs entries are being written by running the following script: `&amp; "$env:USERPROFILE\Documents\PowerShell\cloudsync_monitor.ps1"` and in the Datadog user interface hover over **Logs** and click **Live Tail**.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-GFHWA779.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
8. In the Datadog user interface, create **Measures** (*FilesUploading*) and **Facets** (*ADDomainStatus*):
  1. Hover over **Logs** and click **Explorer**.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-SPPTA2WK.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
  2. Click on a log event.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-JAGYAYU0.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)  

The event details are displayed.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-2RH2LZBV.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
  3. Click `FilesUploading`  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-W5ONQVRQ.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
  4. In the event details, click **Create facet for @FilesUploading**, select the **Measure** tab and click **Add**.
  5. Click `ADDomainStatus` in the event details, and then click **Create facet for @ADDomainStatus**, select the **Measure** tab and click **Add**.
9. In the Datadog user interface, create the monitor for the upload count.
  1. Navigate to **Monitors > New Monitor**.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-EN2IAWEB.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
  2. Click **Logs**.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-VE04LG4B.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
  3. Add the following search query: `service:cloudsync_monitor_powershell @FilesUploading:&lt;n&gt;`  

where *n* is the number of files you want monitored.
  4. Click **all logs** and select `FilesUploading (@FilesUploading)` from the drop-down menu.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-RPFLC1NN.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
  5. Click **Everything** and select `filerName (@filerName)` from the drop-down menu.
  6. In the **Set alert conditions** section set the trigger to `above or equal to`.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-MWGEOQSN.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
  7. Set the **Alert threshold** to `n` and **If data is missing for 5 Minutes** to **Show OK**, where n is the alert threshold. For example setting **Alert threshold** to `1` means that the alert is based on receiving one log event with an uploadCount of 1.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-EAAIQIE0.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
  8. In the **Configure notifications & automations** section define the warning notification. For example:  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-91NSHUQU.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
  9. Set **Aggregation** to **Multi Alert** and verify that it is using the **@filerName** condition value.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-FDVVGWV7.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A22Z&se=2026-11-11T05%3A28%3A22Z&sr=c&sp=r&sig=aOPnDDgiKRk0Yn7KOx4bQFch3trHr89mZqqO7SQELr8%3D)
10. Use the Windows **Task Scheduler** to schedule the script to run at the required interval, for example, every two minutes.