This page lists and explains the available Posit Package Manager metrics.
Chronicle collects Package Manager data from Package Manager’s OpenTelemetry logs, not from its API. To collect it, set LogOTLPEndpoint in the PackageManager section of the Chronicle configuration. Chronicle does not currently produce curated datasets for Package Manager, so this data is available in the daily directory only.
Each metric is listed with its description, schema, why it matters, and recommended actions. It also includes technical details, including metric type and aggregation strategy.
These metrics are stored in separate folders based on the name of the metric. These folders are located within the configured storage location (/var/lib/posit-chronicle/data by default).
Packages
ppm_package_download
This metric records each package download from a Package Manager repository. Every row represents a single download request, with the timestamp column recording when it occurred.
Schema
package_name |
string |
The name of the package that was downloaded. |
package_version |
string |
The version of the package that was downloaded. |
package_language |
string |
The language of the package, such as r or python. |
package_type |
string |
The type of package that was downloaded. |
binary_distribution |
string |
The operating system distribution of the binary package. Empty for source packages. |
repository_name |
string |
The name of the repository the package was downloaded from. |
repository_type |
string |
The type of repository the package was downloaded from. |
user_guid |
string |
The GUID, in RFC4122 format, of the user who downloaded the package. |
client_ip |
string |
The IP address of the client that made the request. |
client_user_agent |
string |
The user agent of the client that made the request. |
client_os |
string |
The operating system of the client that made the request. |
client_language_version |
string |
The version of R or Python used by the client. |
http_status_code |
int |
The HTTP status code of the response. |
response_bytes |
int |
The size of the response in bytes. |
Why this metric matters
- Package usage: Shows which packages and versions your organization depends on
- Repository activity: Reveals which repositories are used most heavily
- Client environments: Shows which operating systems and language versions are in use
Recommended actions
- Review the most-downloaded packages to prioritize validation and support
- Look for older language and package versions that are still in heavy use
- Join
ppm_package_download.user_guid to ppm_user_logins.user_guid to relate downloads to user activity
Technical details
| Metric Type |
non-numeric |
| Aggregation Strategy |
Full retention |
ppm_package_publish
This metric records each time a package is published to a Package Manager source.
Schema
package_name |
string |
The name of the package that was published. |
package_version |
string |
The version of the package that was published. |
package_language |
string |
The language of the package, such as r or python. |
source_name |
string |
The name of the source the package was published to. |
publisher_user_id |
string |
The ID of the user who published the package. |
is_update |
boolean |
Whether this publish updated a package that already existed in the source. |
Why this metric matters
- Internal package development: Shows how actively your organization publishes packages
- Accountability: Identifies who is publishing to each source
Recommended actions
- Review publishing trends over time to understand adoption of internal packages
- Use
is_update to distinguish new packages from new versions of existing packages
Technical details
| Metric Type |
non-numeric |
| Aggregation Strategy |
Full retention |
ppm_package_delete
This metric records each time a package is deleted from a Package Manager source.
Schema
package_name |
string |
The name of the package that was deleted. |
package_version |
string |
The version of the package that was deleted. |
source_name |
string |
The name of the source the package was deleted from. |
user_id |
string |
The ID of the user who deleted the package. |
reason |
string |
The reason given for the deletion. |
Why this metric matters
- Auditing: Provides a record of who removed which packages, and why
- Change tracking: Helps explain why a package that was previously available no longer is
Recommended actions
- Review deletions regularly as part of your package governance process
Technical details
| Metric Type |
non-numeric |
| Aggregation Strategy |
Full retention |
Security
ppm_vulnerability_blocked
This metric records each time Package Manager acts on a package because of a known vulnerability.
Schema
package_name |
string |
The name of the affected package. |
package_version |
string |
The version of the affected package. |
package_language |
string |
The language of the affected package, such as r or python. |
vulnerability_id |
string |
The identifier of the vulnerability. |
vulnerability_severity |
string |
The severity of the vulnerability. |
vulnerability_cvss_score |
float |
The CVSS score of the vulnerability. |
vulnerability_title |
string |
The title of the vulnerability. |
repository_name |
string |
The name of the repository the request was made to. |
action |
string |
The action Package Manager took in response to the vulnerability. |
policy_name |
string |
The name of the policy that triggered the action. |
client_ip |
string |
The IP address of the client that made the request. |
user_id |
string |
The GUID of the user who made the request. |
Why this metric matters
- Risk visibility: Shows how often users attempt to install packages with known vulnerabilities
- Policy effectiveness: Shows whether your vulnerability policies are being applied
Recommended actions
- Identify frequently blocked packages and work with users on supported alternatives
- Review high-severity vulnerabilities first
Technical details
| Metric Type |
non-numeric |
| Aggregation Strategy |
Full retention |
Users
ppm_user_logins
This metric records each user login to Package Manager. Every row represents a single login, with the timestamp column recording when it occurred.
Schema
user_guid |
string |
The GUID, in RFC4122 format, of the user who logged in. |
Why this metric matters
- User activity: Shows how often and when users sign in to Package Manager
- Adoption: Reveals trends in how many distinct users use the server
Recommended actions
- Review login trends over time to understand adoption
Technical details
| Metric Type |
non-numeric |
| Aggregation Strategy |
Full retention |
Back to top