This article is intended to give you an in depth look at all the features of the Log Dashboard. If you have not already downloaded and added a Stackify Log appender or the Stackify API to your app, see the article on Errors and Logs Overview . Logs Dashboard After installing the logging appender, you will be able to configure your App to integrate logging data into the Log Dashboard. This dat
https://docs.stackify.com/logs-dashboard
You can log messages directly via the Stackify API without the use of a logging framework. You can get more information at the Stackify Github page . Use a Logging Framework! Please note that we recommend using NLog, Serilog, or log4net. Those frameworks allow you to send your logs to multiple different outputs. If you decide to not use Stackify products in the future, your code also isn'
https://docs.stackify.com/logs-using-stackify-api-for-net
Step 1: Add StackifyLib nuget package and basic configuration No matter which logging framework you are using, you need to add StackifyLib and add the Stackify.ApiKey to your config file. Set Stackify Configuration settings Because .NET core allows a wide variety of configuration options, how you configure the key could vary wildly. This is just one example of how to do it with the standa
https://docs.stackify.com/errors-and-logs-configure-net-core
To configure your Python application, an Application Programming Interface (API) can be used to send Errors and Logs to Retrace. The step-by-step process is presented below and for more information, visit this Stackify API for Python Github page: https://github.com/stackify/stackify-api-python. Installation and Configuration Python Logging Integration Python logging can be setup to extend
https://docs.stackify.com/configure-python-logging
Stackify uploads IIS logs to capture the usage, response codes, and load times of your web applications. Logs are upload by the Stackify agent continuously. Configuring IIS Logging Settings In IIS, check to ensure that your Logging: is configured for one log file per Site is using the W3C format Provided you have these settings configured as described, you should see IIS log data app
https://docs.stackify.com/advanced-iis-logging
To configure your Ruby application, an Application Programming Interface (API) can also be used to send Errors and Logs to Retrace. The step-by-step process is presented below and for more information, visit this Stackify API for Ruby Github page: https://github.com/stackify/stackify-api-ruby. Installation and Configuration Requirements: Ruby 1.9/2.0/2.1 Rails 3.x/4.x (optional)
https://docs.stackify.com/errors-and-logs-configure-ruby-applications
This guide is intended to help users who are experiencing problems trying to configure their errors and logs to be sent to Stackify. If you haven’t already, check out our documentation on installing Stackify for your appropriate logging framework. This guide will provide you with a checklist of items that will help troubleshoot what is going on. If you are still not successful in sending logs
https://docs.stackify.com/troubleshoot-errors-and-logs-net-configurations
Start logging errors using Error Logging Modules and Handlers (ELMAH) appender with minimal changes to your project. Add a few Dynamic-link libraries (DLLs) and add configuration details to the .config file specifying an additional (or replacement) appender. Getting Started Using NuGet For NuGet from Visual Studio, integrate the Stackify ELMAH libraries and configurations. Search Stacki
https://docs.stackify.com/error-logging-elmah
The following section will cover how to enable sending your Linux syslogs to Retrace to be viewed in the Logs Dashboard with an agent running on your server. Enabling Syslog with Retrace Go to Servers > Locate your Linux server > Click the 3 dots on the right > Click on 'Server Settings' To enable syslog on your server, go to the server settings of the server and check the Syslog che
https://docs.stackify.com/errors-and-logs-configure-syslog-with-the-stackify-agent
By default, Production servers get throttled at 1000 messages per minute whereas Non-Production servers get throttled at 100 messages per minute. Any log messages that exceed the threshold will get a message noted by a #hostthrottled tag. If you have questions about how to avoid throttling, or wish to discuss an increased volume of logging for your account, please contact Stackify Sales at sale
https://docs.stackify.com/faq-log-throttling
Get Started with Retrace Today.
