One of the ways we strive to deliver relevant insights is to only create Traces around interesting requests. Some examples of these request types that are interesting would be faster than normal, slower than normal, new web requests, requests introducing new SQL, requests introducing new exceptions, or abnormal Satisfaction scores. Under performing requests will be profiled more often than fast …
Deployment Tracking: API Request Archive
The Deployment API Requests screen (shown below), provides a history of all the deployment requests accepted by our API. The first step when troubleshooting deployment issues should be to go to this page and verify our API actually received a request. Once our API receives a request to complete the deployment and performs initial validation (returning an HTTP 202 response if successful), it …
Prefix Premium: Custom Configuration Editor
By default, Prefix only instruments key, pre-defined events in the IIS pipeline and page lifecycle. One of the key benefits of the profiler, however, is that you may instrument how long any .NET method takes to execute and include that output in the call stack. In deciding what to profile, keep in mind the overhead that could be incurred. For …
Prefix Premium: Advanced Custom Configuration
In Prefix you may notice that some events that do not profile. By default, the Stackify .NET APM+ Profiler only instruments key, pre-defined events in the IIS pipeline and page lifecycle. One of the key benefits of the profiler, however, is that you may instrument how long any .NET method takes to execute and include that output in the call …
Prefix: Configuring Proxies
If you have a network architecture that requires internet traffic to flow through a proxy server, this guide will help you ensure that Prefix can communicate out through your proxy server seamlessly. Configuring the proxy is done by creating a file in the agent’s folder (C:Program Files (x86)Stackify Prefix by default) called CustomAgent.config. Below is an example of how to populate …
Custom Profiling: Configure for Java
The custom configuration file needs to be named ‘stackify-apm.json’ and be located in the classpath. You can configure additional classes and methods that you want to instrument. Example: [{ “Class”: “com.stackify.example.util.ClassToBeInstrumented”, “Method”: “methodToBeInstrumented” }, { “Class”: “com.stackify.example.util.ClassToBeInstrumented”, “Method”: “anotherMethodToBeInstrumented” }] You can also add custom instrumentation to classes by using @Trace Annotation. See more information on our Github page here: …
Performance: Transaction Settings
For each unique web request and database transaction in your app there are some advanced settings you can use to tailor how they are tracked by Retrace APM+. Some points to note about Key Transactions: Unchecking “Track” or “Errors” for a request will not remove historical data, but future data will be ignored. There is no way to apply settings …
Custom Dashboard: Creating Public Dashboards
By using the public dashboard feature, you can easily give read-only access of your custom dashboards to external users. This help doc will outline the process to turn on the sharing feature in the Settings tab, create the dashboard link, and share the dashboard. Note: Anyone who has access to the URL of the public dashboard will be able view the …