Catalog
Last updated
Was this helpful?
Last updated
Was this helpful?
The Catalog provides a dynamic view of your environment, enabling exploration from you application, infrastructure, code, or contributors. It serves as the gateway to Heeler’s patent-pending ProductDNA, which automates deployment tracking, application lineage, and lifecycle management.
Within Heeler, applications connect the services that work together to deliver business outcomes. Heeler will automatically map the communication paths between the services. Context such as Tier and Security Lead, when set at the application are propagated to all services which of the application.
When viewing an application in Heeler, the platform models the connections between services by analyzing both the code and the underlying running infrastructure. This provides a holistic view of the application’s architecture. From the application view, you can seamlessly explore individual services or dive into the cloud infrastructure that supports the application.
Services are automated constructs that map source code to its running deployments, bridging the gap between development and runtime. Once connected to your SCMs and CSPs, Heeler automatically identifies and creates services in your environment, mapping source code repositories to the running compute in the your environment. It analyzes your cloud environment along with the source code to identify related resources such as databases, load balancers, and additional services.
For monorepos, Heeler goes a step further by automatically mapping individual projects to their respective running deployments, enabling segmentation of findings for each project in the monorepo.
With each service deployment, Heeler pinpoints the exact changeset of the repository in use, enabling precise tracking of individual deployments. This capability allows you to identify and compare material changes between deployments, ensuring greater visibility and control over your application lifecycle.
Application findings (e.g., API endpoints) and security findings (e.g., OSS vulnerabilities) are linked directly to service deployments, enabling precise tracking of changes within each application. Tracking findings at both the deployment and changeset levels allows for accurate identification of where security issues are detected or need remediation. For instance, Heeler can track if a new API is created in a development deployment or if an urgent vulnerability is discovered within a production service.
Deployments are an instance of a service running on cloud infrastructure, either past or present. For example if a service is deployed to a development account, staging account, and production account, Heeler would define 3 deployments for this service. Heeler enables you to inspect each deployment in isolation - identifying dependencies, APIs, and findings specific to that deployment.
The Infrastructure section provides essential context by linking your cloud infrastructure to the services and applications it supports. This connection enables you to quickly inspect infrastructure components and understand their relationships with the broader application ecosystem. With Heeler, you can easily determine which service or application is tied to a specific piece of infrastructure, offering deep visibility into your environment.
Once event collection is configured for your CSP, Heeler detects infrastructure changes within 60 seconds, delivering a near real-time view of your cloud environment. This capability ensures that you stay informed about updates and modifications as they happen, empowering you to maintain control and respond quickly to any changes that impact your applications.
