Datasources Overview
A Datasource contains the location, filename, and settings of log files to be processed.
NOTES
- Datasources can be linked to Profiles
- A single Datasource can be linked to many Profiles
- A Datasource and Profile can only be linked if they're in the same Collection
- To process data, a Profile needs at least one Datasource
Datasources can be configured to point at logs stored locally on the server, at logs on a remote server, or at a SharePoint Online instance. This is configured in the "Datasource Type" field.
Options are:
- Local Filesystem
- FTP
- SFTP
- UNC
- SharePoint Online
On Windows, Angelfish runs under the Local System account. Datasources aren't able to access a mapped drive unless the mapping is owned by the Local System account.
We recommend using Service Accounts when accessing logs on remote servers.
Help Article: Service Accounts
LOCATION FIELD
The Location field in each Datasource stores the path & filename of the logs. You can ese RegEx, Date Substitution Statements, & Wildcards in the Location field to match multiple logs and new logs as they're created in the future.
Help Article: RegEx
Before saving a Datasource, use the Browse button to the right of the Location field to verify your settings are correct.
For all Datasources, specify the full path to the logs in the Location field. For example:
Local Filesystem
- Windows: C:\inetpub\logs\LogFiles\W3SVC3512\u_exYYMM.*
- Linux: /usr/local/logs/website-name/access.YYYYMM.*
FTP
The entered username must be able to access the path & files on the remote server
- /usr/local/logs/website-name/access.YYYYMM.*
SFTP
The entered username must be able to access the path & files on the remote server
- /usr/local/logs/website-name/access.YYYYMM.*
UNC
Enter the full path to the logs, including server name (or IP address) and share name
The entered username must be able to access the path & files on the remote server
- \\server-name\LogFiles\W3SVC3512\u_exYYMM.*
- \\10.1.1.55\LogFiles\W3SVC3512\u_exYYMM.*