Q&A

If you can’t find an answer to your question below,
please contact Ozcode support.

Knowledge Base

Pricing & Payments

No. You can start on our Starter Kit plan which is free forever without entering payment details. You will only need to provide a credit card when you upgrade to a paid plan.

You can only pay with a Purchase Order on the Enterprise Package. If you would like to do so, please get in touch through our contact form or send an email to sales@oz-code.com. 

Yes, we’re happy to support our community with free subscriptions to user groups and other programs. To get in touch with a user group or meetup in your area, please contact us at community@oz-code.com 

It takes less than 5 minutes to change the payment method in your Ozcode account. Just follow these 2 steps:

  1. Login to the Ozcode portal and click on the button with your name on it in the top right corner of the screen.
  2. Click on the Change Payment Method link to change the credit card you have on file with us.

KB Assign Seats - Ozcode  Change Credit Card - Ozcode

If you continue to have trouble making payment, contact us at support@oz-code.com.

Let your boss know how much time you save by using Ozcode Production Debugger. Update our team at sales@oz-code.com and we’ll reach out to your boss, tell him how effective you have been, and show him how Ozcode can improve your team’s productivity (i.e., save him money).

Once you install more than 5 Ozcode agents, you will automatically be upgraded to the enterprise plan and get all the perks. If you want to upgrade but aren’t ready to install more than 5 agents yet, just contact us at sales@oz-code.com and we’ll be happy to help. 

There’s no need for a discount. You can use Ozcode Production Debugger on the Starter Kit plan which is free forever. Register here to START FOR FREE 

In most cases, when a credit card is declined, it is because the card has been blocked by the credit card processor. You may call the number on the back of your card and ask the processor to unblock the card for the Ozcode purchase (an online/international transaction by BlueSnap). 

 

You can also try changing the card you have provided as the payment method in your Ozcode account. To change your payment method, follow the instructions below: 

  1. Login to the Ozcode portal and click on the button with your name on it in the top right corner of the screen. 
  1. Click on the Change Payment Method link to change the credit card you have on file with us. 

If you continue to have trouble making payment, contact us at support@oz-code.com. 

Sure. You can purchase an Enterprise subscription with as many agents as you like. Visit our Pricing page or contact sales@oz-code.com 

We accept the following credit and debit cards: 

  • MasterCard 
  • Visa 
  • American Express 
  • Discover 
  • Diners Club 
  • JCB 

Card payments are processed by our third-party gateway. Please note that if your card does not contain an expiration date and security code, it may not be used on our online store. 

For an Enterprise plan, you may also pay through a Purchase Order by contacting sales@oz-code.com 

All your invoices are available through the Ozcode Customer Portal.

We use your address to confirm payment and billing and to determine VAT obligations. We also require your address in order to charge your credit card and to issue you an invoice.  

Depending on which plan you choose, our paid plans offer a variety of benefits including premium support with issues (bugs or performance), a dedicated success manager to promote feature requests, training sessions and more. In addition, you will get access to an Admin portal where you can manage the users in your organization. To upgrade your plan, visit our Pricing page or contact sales@oz-code.com. 

Subscription Management

Yes. The Ozcode subscription is based on the number of agents you install. The Production Debugger is a web service that can be hosted both in the cloud and on-premises, and you can use it for debugging from any browser that has access to the web service. 

Yes. If the features available in the Starter Kit are sufficient for your commercial needs, we’re fine with that. We’re confident you’ll succeed and eventually scale up to the SMB or Enterprise plan which provides more support and services for your commercial endeavors. 

Yes. The Ozcode subscription is based on the number of agents you install. The Production Debugger is a web service that can be hosted both in the cloud and on-premises, and you can use it for debugging from any browser that has access to the web service. 

Yes. The Ozcode subscription is based on the number of agents you install. The Production Debugger is a web service that can be hosted both in the cloud and on-premises, and you can use it for debugging from any browser that has access to the web service. 

You can assign other users with administrator privileges if you are an administrator yourself. To do soTBD 

Yes. To learn which plan best meets your needs, please reach out to us at sales@oz-code.com 

You can also just get started on our Starter Kit which is FREE forever. Sign up here. You can upgrade later at any time .

Let them know how productive you have been using Ozcode Production Debugger, and how much debugging time you saved by using it. We’ve heard that statements like,” It led me right to the problem,” and “I fixed that issue in half the time it would have taken me without Ozcode,” to be effective in getting team members to give Ozcode a try. If any team member shows an interest, let us know. We’ll reach out, put in a good word for you, and set up a demo. You’ll be a hero once they see how great it is to debug with Ozcode. 

o invite a developer to use Ozcode Production Debugger, select the Invite a teammate icon in the top right corner of the Production Debugger screen. 

 

Provide their email address and click Send Invitation. Your teammate will receive an email with instructions on how to setup their account and get started. 

 

Oh, you’ll have to work hard for that 😉. Here are some things you can do to get some of our awesome swag: 
  • Tweet about Ozcode at least once a week for 3 months straight. 
  • Reference Ozcode in 2 of your blog posts during a 3-month period. 
  • Set up a demo/training session for your organization or for a friend in another organization. 

To add users from your organization to use Ozcode Production Debugger, select the Invite a teammate icon in the top right corner of the Production Debugger screen.  

 

Provide their email address and click Send Invitation. Your users will receive an email with instructions on how to setup their account and get started. 

Your username is your email address. Usually this will be your corporate email.   Go to the Ozcode Production Debugger Sign in screen at: https://app.oz-code.com/sign-in.  Click the Forgot Password? link at the bottom. In the following screen, submit your email to receive instructions on how to reset your password.  If you run into any issues or need help with anything, feel free to reach out to us at support@oz-code.com 

Of course. We welcome anyone tolog get started using Ozcode Production Debugger using the Starter Kit plan which is FREE for ever. It’s a great way to evaluate the product with zero commitment, and we’re confident that once you see the value Ozcode can bring to your company, you’ll upgrade to one of our paid plans. 

Yes. Just let us know and we’ll work with you to make the transfer. Contact us sales@oz-code.com 

Of course. We welcome anyone to get started using Ozcode Production Debugger using the Starter Kit plan which is FREE for ever. It’s a great way to evaluate the product with zero commitment, and we’re confident that once you see the value Ozcode can bring to your company, you’ll upgrade to one of our paid plans.

 

Usage & Features

Yes. Ozcode Production Debugger works in parallel with a variety of popular APMs including New Relic, Application Insights, Dynatrace and more. Ozcode’s lightweight instrumentation uses a multiplexing technique to ensure it doesn’t interfere with your APM’s instrumentation ensuring the two can work together on the same application. Your APM will provide the high-level performance monitoring, and perhaps, point you in the direction of an error. Ozcode provides the code-level visibility that lets you determine the root cause of the error.

For more information on how Ozcode works with your APM here are a few resources:

Yes, you’ll need to install a lightweight agent on the production machines that should work with Ozcode. The agent will attach to the process and report exceptions as they occur.

Yes, here’s how it works.

The first time an exception is thrown, the Ozcode Production Debugger agent turns on its code instrumentation. At this point, Ozcode will only provide you with the call stack. The second time the exception is thrown, the agent captures the full-fidelity time-travel recording, and then removes the instrumentation, so from then on, Ozcode will only count subsequent occurrences of the same error and the number of unique users affected to help you prioritize the bug for fixing.

Yes, in fact, this demo that we used in one of our webinars was written with .NET Core.

Our support for .NET Core means that the Ozcode agent can run in containers so you can debug your code whether it’s running on Windows or Linux.

Yes. To enable compliance with different privacy regulations, Ozcode Production Debugger provides a flexible mechanism to redact PII before it reaches the developer. In the Debugging screen, redacted data is masked and accompanied by a lock icon to indicate redaction.

Masking redacted PII data

PII redaction is configured by your organization’s Ozcode administrator and is applied at two levels. First, the Ozcode agent redacts PII before it leaves your client application. Then, Ozcode also redacts PII before displaying debug information. This ensures that if the PII redaction configuration has changed since the Ozcode agent sent telemetry data to the server, data is redacted according to the latest configuration.

To learn more, please refer to Configuring PII redaction in the Ozcode Production Debugger documentation.

Yes, Ozcode supports .NET Core installations on Linux, including a .NET Core process running within a Docker container.

A performance profiling session can help us at Ozcode identify and remediate performance issues you may have when running Ozcode Production Debugger on your systems.

How you record your performance profiling session depends on how your system is deployed. The sections below describe how to record a performance profiling session for a deployment on:

  • a VM on IIS
  • an Azure App Service

Recording a performance profiling session in a VM on IIS

You can record a performance profiling session in a VM on IIS with PerfView as follows:

  1. Download PerfView to your virtual machine
  2. Run Perfview as Admin
  3. In the Collect menu, choose Collect
    PerfView Collect - Ozcode
    Make sure Merge, Zip, and Thread Time options are checked.
    PerfView Options - Ozcode

  4. Run the scenario with the performance problem, or still just let it run for a minute if it’s already in progress.
  5. Stop collecting and wait several minutes for the snapshot to merge and zip.
    PerfView Stop Collect - Ozcode
  6. An etl.zip fil will be created. Please send us this file.

Creating a performance snapshot in an Azure App Service

There are two ways to create a performance snapshot in an Azure App Service:

  • Using Kudu services
  • Using Application Insights

Both of these methods create a .diagsession file which can be analyzed by PerfView.

Using Kudu services

  1. Enter Kudu services for your App Service. The simplest method is to enter the link, .scm.azurewebsites.net for your site. It’s also accessible from Azure Portal under [Your App Service] in Advanced Tools | Go.
  2. Go to the Process Explorer and choose Start Profiling near the process of your application. Make sure to choose the correct process—it will be under w3wp, but without an scm tag.
    Start Profiling
    Click on Stop profiling when done
    Stop Profiling
    This will automatically download a .diagsession file which contains the snapshot.

Using Application Insights

  1. Go to the Application Insights resource in your Azure Portal
  2. Go to Performance and click on the Configure Profiler button
    Configure Profiler - Ozcode
  3. Click on Profile Now. This will create a performance snapshot file, but it but it takes about 20 minutes for the file to be fully populated and ready
  4. The performance snapshot file is eventually accessible in the same Performance page. This is the file you should send us.

Ozcode Production Debugger is a separate product, although it does reuse quite a bit of code from Ozcode Visual Studio extension, so users familiar with our Visual Studio extension will feel right a home using the Production Debugger. Ozcode Visual Studio extension focuses on developers debugging code locally, and the Production Debugger aims to provide a similar experience for remote debugging, whether on a QA machine, on Staging, and, of course, in Production.

It’s also important to emphasize that Ozcode Production Debugger also works in on-premises deployments.

For more information on deployment options, please refer to Supported Platforms in the Ozcode Production Debugger documentation.

Ozcode supports all popular deployment targets in the cloud and on a desktop machine as follows:

  • Microsoft Azure – Windows
    • Azure App Service
    • Service Fabric
    • Azure Functions
    • Virtual Machine (IIS & Windows Services)
  • AWS – Windows
    • Virtual Machine (IIS & Windows Services)
  • Other cloud providers – Windows
    • Virtual Machine (IIS & Windows Services)
    • Desktop (WPF and WinForms)
  • Enterprise data center – Windows
    • Virtual Machine (IIS & Windows Services)
    • Desktop (WPF and WinForms)
  • All platforms – Linux
    • Docker

To get started with any of the supported deployment options, please refer to Getting Started in the Ozcode Production Debugger documentation.

For detailed instructions on how to install the Ozcode agent for your deployment, please refer to Installation Table in the Ozcode Production Debugger documentation.

Ozcode Production Debugger requires .NET 4.6.1 or higher to run, but it will also debug applications written on .NET 4.5 and above.

The Ozcode Production Debugger agent was designed to provide full-fidelity time-travel debugging without hampering performance. It uses a self-throttling mechanism that monitors CPU, network and memory usage:

  • CPU will never exceed 3%, otherwise the code instrumentation is temporarily switched off
  • Network usage is capped at a maximum of 10MB per hour
  • Memory usage is negligible since the agent only uses lightweight instrumentation to record the code execution flow of an error.

Ozcode shows all exceptions in the applications that contain user code. This includes failed HTTP requests, application crashes, failed tasks, and caught exceptions. Exceptions occurring and swallowed in ASP.NET Framework (or a different framework) will not be reported.

In addition, Ozcode shows all logged errors. Anything logged with log.Error or log.Fatal will report an error. Most major C# logging frameworks are supported out of the box. The Ozcode agent will detect the platform you are using and integrate with it automatically.

Please refer to Troubleshooting in the Ozcode Production Debugger documentation.

Ozcode supports any application type running on top of the .NET Framework or .NET Core. This includes web applications, web API, desktop applications, and Windows services. Ozcode supports all versions of ASP.NET, ASP.NET Core, ASP.NET WebAPI, ASP.NET MVC, WCF, WPF and WinForms. Content

Can’t find what you're looking for?

Ozcode Logo

This website uses cookies to ensure you get the best experience on our website.