The Compose platform logs activity that takes place within the platform; for example, deployments of databases, addons being added, scaling actions and similar. These can be viewed from the user interface under Accounts Activity. On this page we list the codes that can, potentially, be found in an account's activity log.
These codes reflect the overall lifecycle of a database deployment:
The deployment has been provisioned.
A deployment has been provisioned and loaded with data from a backup of this deployment.
Redis only: Changes have been made in the Settings page of the UI to this deployment.
Changes have been made in the Settings page of the UI to this deployment.
The database version of the deployment has been changed. This may have involved a rolling-restart.
The deployment's database was backed up.
A request was made by the user or API to make a backup of the database.
A capsule has been removed from this deployment, either by direct operations control or as a result of a removal action by the user.
The deployment was updated to use Let's Encrypt certificates instead of self-signed certificates.
The deployment was de-provisioned.
These codes reflect the addition and removal of addons and other components during a deployment's active life.
A haproxy portal capsule has been added.
Elasticsearch only: A Kibana addon has been added or removed.
The deployment has been horizontally scaled up by adding one (or more) nodes.
The deployment has been horizontally scaled down by removing one (and only one) node.
MongoDB only: An "oplog portal" addon has been added or removed.
RabbitMQ only: An MQTT addon has been added or removed.
RabbitMQ only: A STOMP addon has been added or removed.
Redis only: A readonly slave was added.
MongoDB only: A shard has been added or removed.
A syslog addon has been added or removed.
A telegraf addon has been added or removed.
These codes reflect changes in resource allocations to various components of database deployments:
The database has been scaled by adding or removing RAM and storage from its available resources.
JanusGraph only: The backing database has been scaled by adding or removing RAM and storage from its available resources.
Elasticsearch only: The allocation of memory to the Kibana addon has been changed.
The allocation of memory to the SSH portal in a deployment has been changed.
The allocation of memory to all the HAproxy portals in a deployment has been changed.
These codes are concerned with access to the database, either adjusting internal roles or switching SSL security verifications:
Access roles were added to the deployment.
Access roles were removed from the deployment.
Access roles were added to the account.
Access roles were removed from the account.
Access roles were added to a private/enterprise cluster.
Access roles were removed from a private/enterprise cluster.
A Compose account can support many users and teams. Changes to these are logged in the activity log.
A user has been created under this account.
A user's details have been updated.
A user's password has been changed
A team has been created. Teams are groups of users.
A team has been deleted.
The accounts billing details (CC and address) have been updated.
When an accounts users log in to the Compose console, their login success or failure is recorded.
A user logged in with 2FA enabled and was verified.
A user attempted to log in with 2FA enabled and was rejected.
A user logged in using thier 2FA recovery codes and was verified.
A user attempted to login using their 2FA recovery code. It was found to be invalid and the login attempt rejected.
A user logged in using a U2F token and was verified.
A user logged in using just username and password.
If this article didn't solve things, summon a human and get some help!
Updated almost 3 years ago