Managing Your Deployment
You can use the Admin Console to perform many of the deployment monitoring and management functions available in Buckit, such as:
Monitor the deployment activity and health by viewing a dashboard of metrics, server or audit logs, trace history, S3 events, or drive health.
Configure alerts by adding or managing a notification target.
Configure deployment settings.
Monitoring
The Monitoring section provides an interface for monitoring the Buckit deployment.
The section contains the following subsections: Some subsections may not be visible if the authenticated user does not have the required administrative permissions.
Metrics
The Console Dashboard section displays metrics for the Buckit deployment. The default view provides a high-level overview of the deployment status, including the uptime and availability of individual servers and drives.
The Console also supports displaying time-series and historical data by querying a Prometheus service configured to scrape data from the Buckit deployment. Specifically, the Admin Console uses the Prometheus query API to retrieve stored metrics data and display historical metrics See Monitoring and Alerting using Prometheus for more information on scraping Buckit metrics into Prometheus.
Logs
The Console Logs section displays server logs generated by the Buckit Deployment.
Use the Nodes dropdown to filter logs to a subset of server nodes in the Buckit deployment.
Use the Log Types dropdown to filter logs to a subset of log types.
Use the Filter to apply text filters to the log results
Select the Start Logs button to begin collecting logs using the selected filters and settings.
Audit
Important
Buckit plans to deprecate the Tenant Console Audit Log feature and remove it in an upcoming release. As an alternative, use any webhook-capable database or logging service to capture audit logs from the Tenant.
The Audit Log section provides an interface for viewing audit logs collected by a configured PostgreSQL service.
Trace
The Trace section provides HTTP trace functionality for a bucket or buckets on the deployment.
This section provides similar functionality to bm admin trace.
You can modify the trace to show only specific trace calls. The default is to show only S3 related HTTP traces.
Select Filters to open additional filters to apply to trace output, such as restricting the Path on which the trace applies to a specific bucket or bucket prefix.
Watch
The Watch section displays S3 events as they occur on the selected bucket.
This section provides similar functionality to bm watch.
Encryption
The Encryption section allows you to view the status and metrics for configured Key Encryption Service providers.
Events
The Events section provides an interface to view, add, or remove Event Notification targets.
You can use this screen configure Buckit to push notification events to the one or more target destinations, including Redis, MySQL, Kafka, PostgreSQL, AMQP, MQTT, Elastic Search, NATS, NSQ, or a Webhook.
Select the Add Event Destination + button to add a new event target to the deployment.
You can select an existing notification target from the list to view its details or delete the target.
Encryption
The Encryption setting provides an interface for listing, creating, and deleting keys for use with Buckit Server-Side Encryption.
You can use keys created or listed in this view for object encryption operations, including setting a bucket-level default key.
Important
Deleting a key prevents Buckit from decrypting any objects protected with that key. If no backups of that key exist, deleting a key renders objects permanently unreadable. See Secure Erasure and Locking for more information.
Configuration
The Settings section provides an interface for viewing and retrieving configuration settings for all Buckit Servers in the deployment. Use the buttons to Export and Import the settings between deployments.
This section contains the following subsections.
Some subsections may not be visible if the authenticated user does not have the required administrative permissions.
The interface functionality mimics that of using bm admin config get or bm admin config set.
Refer to those commands for details on how to define the many options.
Some configuration settings may require restarting the Buckit deployment to apply changes.
