Prerequisites

In order to use Chronicle in your organization, there are a few things you will need in advance:

• Privileges to install the agent alongside supported professional products. For VM-based installations, this usually means sudo access to those machines, and for Kubernetes-based installations this usually means permission to modify the Helm deployments for that cluster.

• The agents need to be able to make HTTP(S) connections to the server, so it must be visible to them on the network.

• To collect metrics from Posit Connect, you need to enable Prometheus metrics in Connect.

• To collect metrics from Posit Connect, you will need a Connect administrator to provision a Connect API key for the agent.

• To collect metrics from Posit Workbench, you need to enable Prometheus metrics in Workbench.

• If you intend to persist data to AWS S3, you need AWS credentials to do so. When the server is deployed on an EC2 instance, the usual choice is an instance profile. When the server is running on Kubernetes, the usual choice is to use IAM roles for service accounts.

Important

When using S3 to store files created by Posit Chronicle, you should use the built-in AWS S3 lifecycle rules to manage how long files are kept in the S3 bucket. See the Setting a lifecycle configuration on a bucket for details.

You will also need to decide on one of two installation paths: virtual machines (VMs) or Kubernetes. This will depend on how you have configured the supported professional products:

• If you are running supported professional products on dedicated Linux servers or VMs, you should run Chronicle on them as well.

• If you are running these applications on Kubernetes, you should run Chronicle in the same cluster.