Observability and logs
Package logs
Package logs show 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.
How it works
To view package logs, go to the Logs tab of the Cloudsmith web app and click Package logs:
Each log entry diplays a timestamp, an action, the actor who performed it, and the affected package and version. Click an entry to expand and view detailed metadata such as package size and actor IP address.
Cloudsmith creates package logs for the following actions:
| Action | Description |
|---|---|
COPY | A package was copied from one repository to another. |
DELETE | A package was deleted. |
HARD DELETE | A package was hard deleted from Recently deleted packages. |
MOVE | A package was moved from one repository to another. |
POLICY VIOLATION | A package has violated an active policy. |
QUARANTINE | A package was quarantined. |
RESTORE | A previously-deleted package was restored from Recently deleted packages. |
RESYNC | A package was resynchronized. |
SYNC | A package was synchronized for the first time. |
TAGS CHANGED | Tags were added, removed, or updated for a package. |
COPY and MOVE package logs
When you copy or move a package from one repository to another, a package log is created for the destination repository only.
HARD DELETE package logs
A
HARD DELETElog is only generated when you explicitly hard delete a package from the recycle bin via the Cloudsmith API or web app (https://app.cloudsmith.com).There are other scenarios in which Cloudsmith hard deletes a package that either generate a
DELETElog, or no log at all. For example, when packages are automatically deleted from Recently deleted packages after 1 week, no log is generated.
For more information about package actions, see Package actions.
Filters
You can filter package logs by action, target, and actor.
- Action: Filter by action, for example,
DELETEorQUARANTINE. - Target: Filter by package name, format, and repository.
- Actor: Filter by actor and actor kind.
- Actor: The name of the user or service that performed the action.
- Actor kind: The kind of actor that performed the action - either User or Service.
Known limitations
- Deleting a user: Deleting a user removes their info from package logs, including any identifying log information for actions they performed.
- Deleting a repository: Deleting a repository also deletes all associated package logs for that repository.
