The key terms and concepts defined on this page are the fundamentals of Attlaz. While we define new terms as you come across them throughout our documentation, having an understanding of the key concepts and features here will make it easier to learn more complex ideas about the product.

This list is ordered so that each definition builds on the previous ones.

Key Concepts

Some of the following key concepts have corresponding features with the same name listed (in upper case) in the Key Features section.

  • Attlaz SDKs - Attlaz's programming language/framework-specific libraries for running flows, integrating platforms, application monitoring.

  • - Attlaz's web interface, where you can build and manage your flows, configure your connections and event and log data is visualized.

  • project - A project represents your service or application in Attlaz. You can create a project for a particular language or framework used in your application. For example, you might have separate projects for your API server and frontend client. For more information, check out our best practices for creating projects. Projects allow you to associate events with a distinct application in your organization and assign responsibility and ownership to specific users and teams within your organization.

  • team - Teams are associated with your Attlaz projects, and their members receive issue notifications, in addition to becoming issue owners. Learn more about setting up teams.

  • environment - environment allows you to separate a project in [stages] such as development, testing, staging, or production. A project has one or more environments. A local environment is an environment where you run the code on your local machine while other environments are run on the Attlaz platform.

Key Features

Each of these key features in is represented by a page (or set of pages) in the application.

  • Flows - Lists the projects of which you're a member, by team, and provides you with a high-level overview of your projects. From here, you can go to the Project Details page of each project for a more granular view. Learn more in the full Projects documentation.

  • Connections - Displays information about grouped problems in your application. From here, you can go to the Issue Details page for a more granular view of any issue. Learn more in the full Issues documentation.

  • Storage - The main view in where you can search or browse for transaction data. The page displays graphs that visualize transactions or trends, as well as a table where you can view relevant transactions and drill down to more information about them. Learn more in the full Performance documentation.

  • Log - Provides a high-level view of each release version, the associated project, the adoption stage of each release, the authors of each commit, as well as release health data including the percentage of crash-free users, and the percentage of crash-free sessions. You can navigate directly to the Releases page or from the Issue Details page, by selecting release ID listed under "Last Seen". Learn more in the full Releases documentation.

  • Insights - Where you can create new alert rules and manage existing ones. Learn more in the full Alerts documentation.

  • Dashboards - Provide you with a broad overview of your application’s health by allowing you to navigate through error and performance data across multiple projects. Dashboards are made up of one or more widgets, and each widget visualizes one or more Discover or Issues queries. Learn more in the full Dashboards documentation.

This content does not seem to be complete

Our documentation is currently getting migrated and being re-written. In the meantime don't hesitate to reach out if you have any questions or want more information about certain topics.