logscale/operations

VendorCrowdStrike Holdings, Inc.Parsersโœ—
AuthorCrowdStrikeDashboardsโœ“
Version0.1.12Alertsโœ“
Minimum LogScale Version1.207.0Actionsโœ—
ย ย Scheduled Searchesโœ“

The LogScale Operations Monitoring package contains alerts, dashboards, scheduled searches, and saved queries for monitoring the health, performance, and capacity of a self-hosted LogScale cluster. It provides a ready-to-use baseline for cluster health monitoring, alerting, and capacity planning that you can tune for your environment.

What it does

Starter package with alerts, dashboards, scheduled searches, and saved queries for health, performance, and capacity planning.

Who should use it

LogScale administrators and platform or SRE teams who run a LogScale cluster.

What it solves
  • Early warning for dead nodes, ingest lag, retention risks, and storage failures

  • Faster triage with dashboards for each area of the cluster

  • Capacity planning with growth trends for CPU, memory, storage, and ingest, plus daily and weekly reports

  • Safer upgrades with before/after comparison to catch regressions during a LogScale upgrade

  • Alerting baseline with packaged alerts to enable and tune

Post-installation configuration

After installing the package, complete the following configuration steps:

  1. Configure actions: Navigate to Automation, select Actions, and set your endpoints on the action templates. All alerts share these actions, so you only need to configure them once:

    • LogScale Email Alert: Set the recipient list

    • LogScale Slack Webhook: Set the incoming webhook URL

    • LogScale PagerDuty: Set the PagerDuty routing key

    • LogScale Generic Webhook: Set the webhook URL

  2. Configure maintenance windows: Every alert calls the saved query filter_maintenance_schedules() to suppress notifications during planned maintenance. By default, no window is set, so nothing is suppressed. To set a window, edit the saved query and change the day of week and hour values. For details on which alerts should remain active during maintenance, refer to the package documentation.

  3. Enable alerts: All alerts are disabled when installed. Enable only the ones that apply to your environment. For example, Kafka alerts only apply to self-managed Kafka installations, and bucket storage alerts only apply if bucket storage is configured.

The parser normalizes data to a common schema based on CrowdStrike Parsing Standard (CPS) 1.2. This schema allows you to search the data without knowing the data specifically, and just knowing the common schema instead. It also allows you to combine the data more easily with other data sources which conform to the same schema.

Installing the Package in LogScale

Find the repository where you want to send the events, or Create a Repository or View.

  1. Navigate to your repository in the LogScale interface, click Settings and then Packages on the left.

  2. Click Marketplace and install the LogScale package for (i.e. logscale/operations).

Configurations and Sending the Logs to LogScale

Important

This package requires LogScale 1.207.0 or later for full functionality. Most features work with LogScale 1.136.1 or later, but the Query Performance Drilldown and Query Performance Profiler dashboards require version 1.207.0.

This package must be installed on a view, not on a repository. The package queries read LogScale's internal logs, metrics, activity, and usage data, which are stored in four system repositories. Before installing the package, create a view that connects all four repositories.

  1. In the LogScale interface, navigate to your repository or view and select GraphiQL from the main menu.

  2. Run the following GraphQL mutation to create the view:

    graphql
    mutation {
      createView(
        name: "logscale-monitoring-operations"
        connections: [
          { repositoryName: "humio",          filter: "" }
          { repositoryName: "humio-metrics",  filter: "" }
          { repositoryName: "humio-activity", filter: "" }
          { repositoryName: "humio-usage",    filter: "" }
        ]
      ) { id name }
    }
  3. Navigate to the newly created view logscale-monitoring-operations.

Note

If you monitor your production LogScale cluster from a separate LogScale cluster, connect the view to the repositories that receive the shipped internal logs instead.

Verify Data is Arriving in LogScale

Once you have completed the above steps the data should be arriving in your LogScale repository.

After installing the package, verify that data is flowing by running the following query in the view over the last 15 minutes:

logscale
#type=humio
| groupBy([#repo, #kind])

You should see events from the humio, humio-metrics, humio-activity, and humio-usage repositories, including the logs, metrics, and activity kinds. If a repository is missing, check the view's connections. Dashboards and alerts that rely on that data show nothing until the repository is connected.

Package Contents Explained

Before installing this package, you must install the humio/insights package. Some dashboard widgets rely on this package and show no data without it.

This package parses incoming data, and normalizing the data as part of that parsing. The parser normalizes the data to CrowdStrike Parsing Standard (CPS) 1.2 schema based on OpenTelemetry standards, while still preserving the original data.

If you want to search using the original field names and values, you can access those in the fields whose names are prefixed with the word Vendor. Fields which are not prefixed with Vendor are standard fields which are either based on the schema (for example, source.ip) or on LogScale conventions (@rawstring).

The fields which the parser currently maps the data to, are chosen based on what seems the most relevant, and will potentially be expanded in the future. But the parser won't necessarily normalize every field that has potential to be normalized.