What’s New in Chronicle

2024.11.0

Improvements

Posit Usage Report

This version of Chronicle updates the Posit Usage Report functionality to populate additional information, including:

Posit Connect

  • R and Python versions installed and configured
  • Content visits
  • Version information
  • User seats

Posit Workbench

  • Additional session launch metrics

Additionally, the report now explicitly notes elements that are not yet implemented, instead of leaving them with missing values.

See the Reports section for how to generate the report.

Diagnostics and logging

To help validate the successful installation of Chronicle and diagnose issues, the Agent and Server now include additional logging details.

Breaking

The following changes have been made since the previous release (2024.09.0):

  • The Chronicle documentation is now permanently available at docs.posit.co/chronicle. Please update any outdated bookmarks, as previous locations will no longer be updated.
  • Chronicle Agent:
    • The agent no longer collects or stores system-level host metrics and now focuses only on application metrics. These host metrics were not being used and contributed to higher data volume. We may reintroduce them in the future if they are needed.
    • Support for Posit Package Manager in Chronicle Agent is temporarily disabled. The related metrics are currently unused and will be added back with additional reporting in a future release. Do not install Chronicle Agent with Posit Package Manager at this time.

Known issues

Upgrades

For those upgrading from a previous release, please review the following upgrade notes based on your currently installed Chronicle version:

  • After upgrading Chronicle on RedHat-based systems, manually start the service with sudo systemctl start chronicle (and/or sudo systemctl start chronicle-agent).
  • When you set an Agent Environment Variable to override metric endpoint auto-detection, the agent will no longer fall back to auto-detection if the variable is invalid. If you encounter failures after the upgrade, verify and remove any outdated environment variables.
  • After upgrading Chronicle on RedHat-based systems, manually start the service with sudo systemctl start chronicle (and/or sudo systemctl start chronicle-agent).
  • If you installed Chronicle Server or Agent using yum or apt, you may encounter errors due to a URL path change from rstudio to posit. Follow the Cloudsmith configuration instructions to update the repository path, or contact us for help.
  • If you override the Chronicle Agent’s autodetection of metrics endpoints by setting the CHRONICLE_CONNECT_METRICS_URL or CHRONICLE_WORKBENCH_METRICS_URL environment variables, you must now append /metrics to the end of the URL. Previously, /metrics was added automatically, but this change allows access through a reverse proxy or other URL rewriting.
  • Chronicle Server now stores temporary, internal data prior to compaction in a /private directory, instead of as temporary files in the primary /v1/metrics directory. After upgrading, any uncompacted data from the previous hour may be lost, causing a small gap in hourly data right before the upgrade. However, this should have minimal impact on overall metrics quality.

Documentation

The Chronicle documentation is now permanently available at docs.posit.co/chronicle.

Installation and upgrade procedures:

Back to top