Documentation

Logs and observability

Cloudsmith's observability features provide the tools to understand how your artifacts are being accessed, used, and managed. This section covers the key data sources that enable deep visibility into your artifact management lifecycle.

• Client logs are the foundational data layer, capturing the granular, real-time interactions with your repository. They record every request, download, and deployment, providing a detailed view from the perspective of the developer machines and CI/CD pipelines that consume your artifacts. They are invaluable for understanding package consumption patterns.

• Audit logs provide a critical security and compliance perspective of your workspace. This feature tracks significant events related to governance of your workspaces and repositories, such as user authentications, permission changes, or modifications to repository settings. This creates an immutable record of "who did what, and when" which is fundamental for security forensics and meeting regulatory requirements.

• Package logs provide a record of package-based events in the Cloudsmith web app. You can see when packages are deleted, updated, or modified, providing a clear audit trail of what happened and when.

• Policy decision logs provide a record of policy decisions - when a package is evaluated against a policy, the policy engine creates a decision log entry.

  Note

  Policy decision logs are generated only for policies created using Policy as code.

• Usage analyzes and aggregates client logs information to provide insights and a general overview of your usage data.

Together, these logging mechanisms offer a comprehensive view of your artifact ecosystem. While this section also touches on advanced capabilities like exporting this data for long-term retention or specialized analysis, the core principle is to provide you with the foundational visibility needed to secure and manage your software supply chain effectively.

Log access

Different levels of workspace and repository access determine which logs you can access:

Updated 3 minutes ago