- Getting Started
- Managing Stacks
- Manual Stacking
- Filtering & Searching
- Bulk Actions
- Project Settings
- Reference Ids
- User Sessions
- Log Levels
- API Usage
- .NET Client
- Self Hosting
Please follow this section to set up Exceptionless in a Kubernetes environment. Please note this section is a work in progress, any contributions is greatly appreciated.
Please note that we recommend you use Kubernetes for running in production.
- Follow the steps here for how to create it in AKS
- View the configuration settings below for more information on configuring Exceptionless.
- Configure your clients to send errors to your website.
Now, you can create a local account, organization, and project and send events to it.
The following section will cover how to configure exceptionless inside of a Kubernetes instance using the
exceptionless-config config map. All exceptionless configuration keys are prefixed with
EX_. Please note that these instructions also apply to docker using environment variables.
All configuration options and settings can be found in the various option classes located here.
Please note that if you are specifying configuration via
docker-compose, then you will need to drop the
# connection string used for any provider specifying Redis.
You can append values to any connection string using a
;. For example, you can control many shards and replicas each Elasticsearch index should be created with by appending to the
EX_ConnectionStrings__Elasticsearch connection string. For a Elasticsearch cluster (3 nodes, two masters), you would append
provider value determines what implementations to use for the various abstractions. We've made it easier to reuse a single connection string by automatically looking up a connection string by the provider name and adding any key value pairs to the current connection string (as shown above with redis).
General Configuration #
- You'll want to set the
EX_ApiUrlkey to your external url of the api.
- You'll want to set the
EX_BaseUrlkey to your external url of the website. If you are not following the clean urls optional section below, please make sure you also add the hashbang (
/#!) to the base url.
EX_AppModeshould be set to
Productionif you want to send unrestricted emails.
- Please take a quick look at all the configuration options and settings that can be found in the various option classes located here.
Active Directory Authentication #
To enable Active Directory authentication, update the Update the
exceptionless-config config map to include the
EX_ConnectionStrings__LDAP connection string. The value should be your domain's LDAP URI (e.g.
Please note the following:
- Users must still go through the registration process using their AD credentials. This allows account setup to proceed as normal. AD credentials are not stored.
- Exceptionless relies on the following properties being available in AD:
givenName: user's first name
sn: user's last name
sAMAccountName: user's username
- To ensure the correct account information is retrieved for a user, consider using a more specific connection string to narrow down the LDAP account type. For example:
LDAP://ad.domain.com/OU=Standard Users,OU=User Accounts,DC=domain,DC=com
Enabling Slack Integrations #
- Create a Slack app for your workspace
- Please do not distribute your app outside of your organization.
- Go to the
OAuth & Permissionsfeature. Add a new redirect URL. The redirect URL should be your Exceptionless base URL.
- On the basic info page of your Slack App, you will need to find the Client ID and Client Secret
- Update the
ConnectionStrings__OAuthvalue to include
SlackId=YOUR_ID;SlackSecret=YOUR_SECRET;and restart the associated pods.
- If you've already loaded a page in Exceptionless, you will need to do a hard refresh for the config changes to apply.
Please see the Upgrading for details on how to upgrade to the current version.
If you are having issues please try the following to resolve the issues. If this doesn't work please open an issue or contact us on Discord.
- Make sure you are running the latest release by visiting our releases page. You can verify the version you are currently running by accessing the status page
- You can also enable detailed logging by updating the
Serilog__MinimumLevel__Defaultconfig map value to