Installation guide



  • logBee.Backend-{version}

  • logBee.Frontend-{version}

Artifacts can be downloaded from




For instructions installing MongoDB server, please check the official tutorial.

IIS web applications

  1. On the machine hosting the IIS server, install ASP.NET Core Runtime 8.

  2. Create two IIS applications:

    • logBee.Backend

    • logBee.Frontend

  3. Update the Application Pool settings for both of the applications to the following:

logBee.Frontend Application Pool logBee.Backend Application Pool
  1. Copy into each IIS application folder the corresponding deploy package

logBee.Frontend folder
logBee.Backend folder


Hotizontal scaling is not currently supported by logBee app.

Both logBee.Backend and logBee.Frontend applications must each be deployed to a single instace.


On the first deployment you need to update the required configuration options, such as:

  • database connection

  • application endpoints

  • authorization tokens

The configuration file for each application (logBee.Frontend and logBee.Backend) is located under Configuration\logBee.json.

Initial startup

After the configuration files have been updated, you can run the applications.

The initial startup will bootstrap all the necessary components including the MongoDB database.

Startup logs (including errors) will be generated under the \logs folder:

  • C:\inetpub\wwwroot\logBee.Backend\logs

  • C:\inetpub\wwwroot\logBee.Frontend\logs

Startup steps

  1. Make a single request to logBee.Backend root URL (

    If everything went successful, you will see the logBee.Backend home page.

    logBee.Backend home page
  2. Make a single request to the logBee.Frontend root URL (

    If the startup process went successful, you will see the home page.

    logBee.Frontend home page

Post deployment

Your logBee app is running and ready to process the logs. You can update your .NET applications to start sending the logs to the newly created logBee.Backend application.

Make sure you update the configuration values, respectively the “OrganizationId”, “ApplicationId” and “ApiUrl”.

    .Add(new RequestLogsApiListener(new Application(Configuration["LogBee.OrganizationId"], Configuration["LogBee.ApplicationId"]))
        ApiUrl = ""
logBee.Frontend request


Startup logs (including errors) will be available under \logs folder. Here should be the first place to check.

  • C:\inetpub\wwwroot\logBee.Backend\logs

  • C:\inetpub\wwwroot\logBee.Frontend\logs

Quick checklist

  1. If there are any confiuguration errors, you should see them under the \logs folder.

  2. If using a relational database provider (MySql/SqlServer), logBee.Frontend will try to create the database (if it doesn’t exist).

    Additionally, the database script will be saved under the “\logs\{Provider}-database.sql.txt” file.

  3. If the application fails to start and there are no log messages, enable IIS logs:
    Update web.config, set <aspNetCore stdoutLogEnabled="true" />, then restart the application.
    <?xml version="1.0" encoding="utf-8"?>
        <location path="." inheritInChildApplications="false">
                    <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
                <aspNetCore processPath="dotnet" arguments=".\logBee.Backend.AspNetCore.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />
    <!--ProjectGuid: 4EC40754-6618-4D7D-B45E-C7FE1D6B8EF6-->
    Create an empty logs folder if one does not already exist.
  4. If no logs are generated (including no IIS logs), double check that you have ASP.NET Core Runtime 8 installed.

Need help?

Open a GitHub issue or send an email to

For technical support, questions or any feedback, please feel free to send us a message and we will get back to you.