Cluster Management
A LogScale cluster has some additional requirements for configuring, monitoring, and managing. This section explains how to handle common tasks when running a cluster.
Monitoring
Once a cluster is runnning, you can't forget about it. You'll need to monitor it to ensure high availability. For this administrative duty, LogScale provides some good monitoring tools.
The Query Monitor allows you to view queries in LogScale as they're executed, running queries. It provides information on resource usage and processes.
LogScale provides a host of metrics for more detailed monitoring and the operating of LogScale.
Preventing and Resolving Problems
Problems with any system are inevitable. In a cluster, they can be more likely and more complex. However, there are some precautions you can take to prevent them, and steps to reduce stress as you're resolving them.
LogScale can be configured to prevent the execution of queries that may cause problems (e.g., sensitive data, hacker attemps).
When you discover some corrupted data, or perhaps while you're performing an update to the software, you may want to disable ingesting of data until you're ready to continue.
Repository Management
The core of LogScale is the repository. For clusters, there are some administrative tasks to consider: how to ingest data into a repository; and how much data to keep after a certain amount of time.
Ingest Listeners utilize raw TCP/UDP sockets with various formats (e.g., rsyslog, StatsD). Related to this, you can configure them for specific parsing, security, and to reduce packet losses.
LogScale can accumulate a tremendous amount of data in time. When the data becomes too old to be meaningful for your needs, you probably should delete it to improve performance, to minimize security vulnerabilities, and for compliance with related regulations.
Backup and Archiving
One of the most basic administrative tasks is making back-ups and archiving data. LogScale allows for storing such data in external locations.
LogScale supports archiving ingested logs to Amazon S3. If this is something your organization wants to use, you'll need to review the documentation pages on this.
Google Cloud Storage Archiving
Another external storage method is to use Google Cloud Storage. Read the documentation in this section to learn how to configure and monitor it.
Licensing
The use of LogScale software requires a license. For cloud accounts, this is handled for you. For self-hosting, you'll have to ensure they're installed properly.
To use LogScale in a self-hosted environment, you'll need to install your license key on your servers in your cluster. This section of the documentation explains what you'll need to do.
To use the GraphQL API for retrieving information on a cluster, see the documentation pages on the cluster() and clusterManagementSettings() query fields. For checking connections, consider using the checkLocalClusterConnection() and checkRemoteClusterConnection() query fields. Related to that, look at the pages on the createRemoteClusterConnection(), deleteClusterConnection(), and similar mutation fields.