Ceburu Log Management – Probe Installation and Setup
Ceburu supports both WinRM and non-WinRM configurations for log management.
This flexibility allows seamless integration in varied environments and supports multi-probe (dual probe) architectures for redundancy and scalability.
1. Prerequisites for WinRM-based setup
Before installation, ensure:
WinRM is enabled on Probe, Forwarder, and Collector systems (for WinRM-based setup).
Network connectivity is available between these components.
Administrator privileges are available on the installation machine.
- Go to
https://portal.ceburu.com/and log in - On the left-hand menu, scroll down and click More Features

3. You will be redirected to https://portal.ceburuai.com where the Log Management module will open.
4. Click on the Download icon located in the dashboard.
5. Download and install the Ceburu Probe on the designated probe machine by following the on-screen installation instructions.
Note: Ensure the probe machine meets the minimum system requirements and has internet access for successful installation. WinRM must be enabled and properly configured before proceeding.


After downloading the installer, follow these steps:
Locate the Installer: Go to your Downloads folder and double-click the CeburuProbeInstaller.exe file.

Accept the License Agreement: Review the license terms and click I Agree to continue.

Configure Settings: Enter any required configuration details, such as the Portal URL or Authentication Key provided in the portal.

Provide the Probe Listening Port and click Install.
Complete the Installation: Click Install to begin the installation process. Once complete, click Finish to exit the setup.


Verify Installation: After installation, the probe service should start automatically. You can verify this in the Services panel by checking for Ceburu Probe Service status
After installation:
Navigate to Configurations → Network Discovery in the Ceburu Portal.
You will see the registered probes listed under Registered Probes:
Primary Probe – Main discovery node responsible for initiating network scans and device communication.
Secondary Probe – Optional backup or extended discovery node used for redundancy or distributed scanning.
Both probes should display a Connected status once communication is successfully established.
Note: Adding a Secondary Probe is optional. It can be used to improve coverage or provide failover capabilities but is not mandatory for the setup to function.
If the Primary Probe (and optional Secondary Probe, if configured) is connected, the setup is complete.
Configure Network Scan
Go to Configurations → Network Discovery in the Ceburu Portal.
Click Configure Network Scan.
In the popup window, enter the Subnet/IP Address (for example:
192.168.33.0/24).Click Add to include the subnet, then select Create Profile & Start Scan.
The system will start scanning the provided subnet. Once completed, the scan results will display the total number of detected devices along with their IP addresses and hostnames.


Viewing Discovered Devices
After a successful scan, click the eye icon next to the scan profile to view the discovered devices.
To add the devices to your managed inventory, select the desired devices and click Add to Assets.


Once added, devices will appear under Configurations → Assets.

Setting Device Credentials
Before deploying the End Agents, credentials must be set for the target devices:
In the Assets tab, select the devices you want to configure.
Click the Key icon or select Set Credentials from the top-right dropdown.
Enter:
Domain
Username
Password and Confirm Password
Click Set Credentials to apply the credentials to the selected devices.

Installing the End Agent
After setting credentials:
Select the devices where you want to install the Ceburu End Agent.
Click the dropdown menu in the top-right corner and choose Install Agent.
The installation process will automatically begin on the selected systems.
Once installed, the End Agent Status will update to Active.

Go to the Log Management tab. Click on Add Log Source in the Log Sources section.

Enter Log Source Details
- Identifier Tag: Enter a unique identifier for the log source.
- Querying Tags: Add any tags that will help filter or query the logs.

Specify Log File Configuration
- File Path: Provide the absolute path to the log file on the device.
- File Pattern: Define any file matching pattern (e.g., *.log).
- Parser: Choose the appropriate parser to interpret the log format.

Choose the device where the logs are located. Click Create Log Source to complete the setup.

Once added, the new log source will appear in the Log Sources list for monitoring and analysis.

Make sure the file path and permissions are correct on the target device to avoid collection errors.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article