Python package version 1.0!

Release AppSignal for Python package version 1.0!

Read our Python package version 1.0 announcement blog post!

This release marks the 1.0 release of our Python integration and contains the following features:

• Track errors in your app.
• Track performance of HTTP endpoints and background jobs.
• Dive into more detail with custom instrumentation.
• View host metrics for Virtual Machines and containers on which the app is running.
• Report custom metrics that are unique to your app, and get alerted when they change.
• Deploy tracking whenever a new version of your application gets deployed.
• Automatic support for the following frameworks and libraries:
  • Celery
  • Django
  • FastAPI
  • Flask
  • Jinja2
  • Psycopg2
  • Redis
  • Requests
  • Starlette
  • WSGI/ASGI

Please see our Python package documentation and guides for more information. Reach out to us on support@appsignal.com if you need any help 👋

Changed

• The diagnose CLI will now print more details about each path in diagnose CLI output, such as if it exists or not, if it's writable and the ownership details. This will help with debugging path related issues without sending the report to the AppSignal servers.
• Rename the example error reported by our installer and demo CLIs from ValueError to DemoError to better communicate this is an example error and should not be treated as a real error from the app.
• Add a message about committing the Push API key in the client file upon generation. We recommend storing this key in environment variables instead or in some kind of separate credentials system instead.

Fixed

• Fix an issue where the installer would always find the push API key to be invalid, halting the installation process.
• Fix the diagnose report CLI exiting with an error when a path was not found. When a file, like the appsignal.log file, was not found, the diagnose CLI would exit with an error when trying to read from the file. It will now no longer try to read a non-existing file and no longer error.
• Fix the demo error and performance incidents that are reported by our install and demo CLI tools to recognize them by our front-end as examples. It will now show the intended box with some additional explanation that you don't have to worry about these example errors and performance measurements. They're there to test if our integration works in your app and report the first bits of data.

See the Python package 1.0.0 changelog for more information.