- Welcome to Retrace
- Installing Retrace
- Account Setup
- Application Performance
- Centralized Logging
- Error Monitoring
- Monitoring Configuration
- Overview
- Application Monitoring Overview
- Application Monitoring Configuration
- Windows Performance Counters
- How to Monitor Key Transactions
- How to Monitor Your Logs
- How to Monitor Azure Service Bus
- Server Monitoring Templates
- How to Monitor SQL Queries
- How to Monitor Websites
- How to Monitor Files
- Log Query Monitor Best Practices
- Alerts and Notifications
- FAQs
- Deployment Tracking
- RUM Setup Guide
- OTel Support
- .NET Setup Guide
- Getting Started
- APM Setup Guides
- New vs Legacy Profiler
- Legacy .NET Profiler Guide
- Supported Technologies
- .NET APM on Windows
- .NET APM on Linux
- .NET APM with Docker (Linux)
- .NET APM with Kubernetes
- Custom Instrumentation
- APM Troubleshooting Guide
- Agent Installation Options
- How to Profile Windows Services
- Azure Deployments
- AWS Deployments
- Advanced APM Topics
- .NET Logging Guide
- .NET API Library
- Examples
- Java Setup Guide
- APM Setup Guides
- Java APM on Linux
- Java APM on Windows
- Java APM with Docker
- Java APM with Kubernetes
- Java APM with AWS ECS
- Java APM with AWS Fargate
- Java APM with AWS Lambda
- Java APM with Heroku
- Java APM Troubleshooting Guide
- Support for Java Background Services
- How to Collect Servlet Web Request Details
- Custom Instrumentation
- Supported Java Technologies
- Getting Started
- Logging Setup Guides
- Java API Library
- Examples
- APM Setup Guides
- PHP Setup Guide
- Getting Started with PHP
- APM Setup Guides
- PHP APM with Linux
- PHP APM with Docker
- PHP APM with Kubernetes
- PHP APM with AWS ECS
- PHP APM with AWS Fargate
- PHP APM with AWS Elastic Beanstalk
- PHP APM with AWS Lambda
- PHP APM with Plesk
- PHP APM with Heroku
- PHP APM Troubleshooting Guide
- Custom Instrumentation
- Advanced Configuration
- Supported PHP Technologies
- Logging Setup Guides
- Node.js Setup Guide
- Getting Started
- APM Setup Guides
- Node.js APM with Linux / Windows
- Node.js APM with Docker
- Node.js APM with Kubernetes
- Node.js APM with AWS ECS
- Node.js APM with AWS Fargate
- Node.js APM with AWS Lambda
- Node.js APM with AWS Elastic Beanstalk
- Node.js APM with Heroku
- Node.js APM Troubleshooting Guide
- Custom Instrumentation
- Supported Node.js Technologies
- Logging Setup Guides
- Ruby Setup Guide
- Getting Started
- APM Setup Guides
- Ruby APM with Linux / Windows
- Ruby APM with Docker
- Ruby APM with Kubernetes
- Ruby APM with Heroku
- Ruby APM with Scalingo
- Ruby APM with AWS ECS
- Ruby APM with AWS Fargate
- Ruby APM with AWS Lambda
- Ruby APM with AWS Elastic Beanstalk
- Ruby APM Troubleshooting
- Custom Instrumentation
- Advanced Configuration
- Supported Ruby Technologies
- Logging Setup Guides
- Python Setup Guide
- Integrations
- Prefix
- What is Prefix?
- Getting Started
- Updates In Prefix
- Distributed Tracing
- Missing Spans
- Search Syntax
- Open Telemetry Support
- Using Prefix with .NET
- Using Prefix with Java
- Using Prefix with PHP
- Using Prefix with Node.js
- Using Prefix with Ruby
- Using Prefix with Python
- Prefix Premium
- Troubleshooting
- Data Collection Policy
- Release Notes
- Windows Agent Release Notes 2024
- Linux Agent Release Notes 2024
- Profiler Updates 2024
- 2023
- 2022
- 2021
- 2020
- 2019
- December Platform Release
- Windows Agent 4.24
- November 19, 2019 - Platform
- October 15, 2019 - Platform
- Windows Agent 4.23
- September 19, 2019 - Platform
- Windows Agent 4.22
- August 27, 2019 - Platform
- August 1, 2019 - Platform
- Windows Agent 4.21
- July 11, 2019 - Platform
- July 1, 2019 - Platform
- Windows Agent 4.20
- June 4, 2019 - Platform
- Linux Agent 2.20
- May 15, 2019 - Platform
- April 16, 2019 - Platform
- April 2, 2019 - Platform
- March 19, 2019 - Platform
- Windows Agent 4.19
- March 11, 2019 - Platform
- Linux Agent 2.17
- February 6, 2019 - Platform
- January 17, 2019 - Platform
- January 8, 2019 - Platform
- Linux Agent 2.16
- 2018
- December 19, 2018 - Platform
- December 2018 - Platform
- November 2018 - Platform
- Linux Agent 2.15.5
- Windows Agent 4.18.8
- October 2018 - Platform
- Windows Agent 4.17.20
- Windows Agent 4.17.19
- Linux Agent 2.14.3
- September 2018 - Platform
- Windows Agent 4.17.14
- Windows Agent 4.17.11
- August 2018 - Platform
- July 2018 - Windows Agent 4.16
- July 2018 - Platform
- June 2018 - Platform
- April 2018 - Platform
- March 2018 - Platform
- March 2018 - Windows Agent 4.14
- March 2018 - Linux Agent 2.9
- February 2018 - Platform
- February 2018 - Windows Agent 4.13
- January 2018 - Windows Agent 4.12
- January 2018 - Windows Agent 4.11
- January 2018 - Linux Agent 2.8
- January 2018 - Linux Agent 2.6
- January 2018 - StackifyLib 2.1
- Other Announcements
- Insights
- Website Monitoring and Alerting
- Alert Notification and Escalation
- Leveraging Retrace for the Different Application Support Levels
- Application Cloud Migration and Re-architecture Journey
- Using Retrace as a key DevOps CI/CD automation tool
- ITIL v4 Service Management – Service Operations Processes
- Problem Management – Key to Achieving Operational Excellence
- OTel Appliance - Put your serverless and containerized apps on Retrace
- Open Telemetry: Under The Hood
Common Azure App Service Issues
Below are common Azure App Service issues.
'StackifyHttpTracer' Not Found
If you encounter the error "Could not load file or assembly 'StackifyHttpTracer' or one of its dependencies. The system cannot find the file specified.", download and install our NuGet package that will install the module into your project and redeploy it: Nuget: Stackify Http Module
Using the "WEBSITE_LOCAL_CACHE_OPTION" Azure Setting
We can't support APM with this setting enabled. With this setting enabled, you are likely to get a couple minutes of data and then APM will abruptly stop. A little back-story: because we collect the data out-of-process via the web job, we have to output to D:\Home as D:\local is per process so D:\local for w3wp.exe can't be accessed by any other running process. Microsoft docs state that "D:\Home will point to the local cache." Unfortunately, we cannot, via Kudu, access the local cache drive which is on C:. The advice is to not use this setting.
Agent Goes Down After Deployment/Web Deployment Task Failed Error
If you are using multiple deployment slots, you will want to install the site extension for each deployment slot. This is required so when you are swapping slots everything works correctly, as site extensions are part of what is swapped. Setting Stackify.Environment is also important so we can identify which slot is which. If you are trying to deploy your application and getting an error about StackifyWebJob files being locked, you may need modify your deployment settings. Stackify runs as a WebJob that is installed via the Azure Site Extension in to your App_Data folder. If you are trying to use the optional deployment setting of "Remove additional files at destination" this would try to remove our WebJob. Error: Web deployment task failed. (Web Deploy cannot modify the file 'StackifyWebJob' on the destination because it is locked by an external process. To fix this, also select "Exclude files from the App_Data folder" so the Stackify WebJob is not affected by the deployment. This setting is shown below in the Visual Studio UI as part of the publish options.
No APM data for .Net Core Applications
In Azure, the platform architecture option can be configured as 32 or 64 bit. The application service 'bitness' needs to match the publish/compile bitness set here. If this doesn't align, Stackify may have issues profiling the application. Following changes to your app, sometimes it is necessary to remove the site extension and reinstall as such:
- Delete site extension and related folders
- Reinstall site extension
- Restart site
Restart is Different than Stop and Start
It is important to note that fully stopping and then subsequently starting an Web App, Webjob, or Web Service inside of Azure can function differently then a normal 'Restart.' All these actions are in the control panel of the Azure Portal.
If APM data doesn't show following a restart, a full stop/start has shown to work in some instances.