> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/creating-and-running-projects/logging.md).

# Logging

appRules includes several options for logging entries in the project database and for reporting.    Normal Log entries are by default automatically written to the project database by the running process or they can be written to the database by using a logging activity (WriteLogs) at specific points in the running process.  Extended or Debug Logs are automatically written to the file system in the appStrategy/PortalData/\<Company>/DbFiles/\<ProjectDatabase>/Logs folder. (\<Company> default is Default for a single company environment). The file name is prefixed by the project name + a timestamp.

### Project Log Settings

You can set the default logging options for your project by setting the LogOption property in the Execution Options tab of the Project Details window (Workflow button in the Project toolbar):&#x20;

<div data-with-frame="true"><figure><img src="https://1923141441-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFjmFrZ8sef1J7qkr6H%2Fuploads%2FIMBQrytQWuK5D40gUGl3%2Fimage.png?alt=media&amp;token=1f33f482-07f8-4dae-8b10-6eefba85d4d4" alt=""><figcaption></figcaption></figure></div>

#### Viewing Log Entries

The appRules Portal Application application includes tools that you can use to view Logs and Statistics stored in the project database as you run your jobs.  The viewers can be accessed from the “Logs/Statistics” menu or the Logs/Stats button for the current opened project.&#x20;

The Workflow Run Logs shows the run instances and tabs showing the statistics and logs for each run (instance) of the project.

<div data-with-frame="true"><figure><img src="https://1923141441-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFjmFrZ8sef1J7qkr6H%2Fuploads%2Fy7z7IjK3EBJN6Av9RvOq%2Fimage.png?alt=media&amp;token=b8133842-8113-47f5-bae2-8b8712754188" alt=""><figcaption></figcaption></figure></div>

### File Logs

appRules creates log files for certain errors or processes.  For example, if the project database is not available, errors are automatically written to the Logs folder (C:\ProgramData\appStrategy\PortalData\Default\DbFiles\\\<DataBaseName>\Logs).

When tracking down an issue after running your project, you should first check the project logs as shown in the section above.  In addition, you should also check the System Log Files option or Logs folder for any message files that may have been created by the process.  &#x20;

#### Project Run Details

\
You can configure your projects to capture as much information as possible regarding the process.  After running the job or while it is still running, you can use the Project Run Details window to view all details related to the job, including Activity statistics, Source and Target statistics and system logs.   The Project Run Details gives you a centralized report showing all details about instances of the project.

In addition, the Project Run Details also allows you to view details on child jobs launched by each job.

#### Database Log Entries

\
Database Log Entries captured during the course of running your jobs can be viewed using the Database Log Entries of the Logs/Statistics menu.  Log entries can be selected by date range and other criteria.

#### Run Instances

\
Each run instance of a project makes an entry in the Run Instance table.  This selection shows a summary of the run instances for the project selected by date range.

#### Activity Statistics

\
This selection allows you the view the statistics for each activity for each instance of the project.  Entries can be viewed by specifying a date range.

#### Data Source Statistics

\
This selection shows statistics on data sources that have been used by projects in the project database.  Entries can be viewed by specifying a date range.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/creating-and-running-projects/logging.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.