Review Security Data Lake Usage

Updated on 12 Nov 2024
1 Minute to read

Article summary

Did you find this summary helpful?

Thank you for your feedback

The Security Data Lake Usage page provides an overview and breakdown of the data currently stored in your Security Data Lake. If you’re a security administrator responsible for managing your organization’s data, this page helps you to answer questions like:

How much space do I have left?
Will I run out of space?
To avoid running out of space, what configuration changes should I make?

Navigate to the Usage page

From the navigation menu, under Your Environment, expand Security Data Lake and click Usage.

Overview of the Usage page

There are four main sections of the Usage page:

1: “Available storage” progress bar

Shows how much data is currently stored in the Security Data Lake, and how much space is available.

2: “By the numbers” KPIs

Lists key performance indicators related to Security Data Lake usage.

KPI	Description	Purpose
Licensed data lake size	The total storage capacity available.	Understand how much space is available.
Integrations in data lake	The number of integrations with data currently stored in the data lake. This can include inactive integrations with old data that hasn’t “aged out”. This can exclude active integrations that haven’t sent any new data recently.	Understand how many integrations are actually impacting available storage, regardless of status.
Net lake usage last 7 days	The overall change in the amount of data stored in the last 7 days.	Understand if space will run out (assuming recent trends continue unchanged). If the number is positive, the available space is shrinking. If the number is negative, the available space is increasing.
Largest integration	The integration with the largest amount of data currently stored in the data lake.	Understand which integration impacts available storage the most. If available space is limited, reducing the data stored for this integration will have the greatest effect.

3: “Usage by integration” table

Breaks down data currently stored in the Security Data Lake per integration. Use this to understand which integrations impact available storage the most. If available space is limited, reducing the data stored for your largest integrations will have the greatest effect.

4: “Usage by month” chart

Breaks down data currently stored in the Security Data Lake by when it was originally ingested. Use this to understand if there are any spikes in data ingest that could affect your projected available space. If available space is limited, this can help you to estimate the impact of reducing your data retention period for relevant integrations.

Was this article helpful?

What's Next

Search and Export Data from the Security Data Lake

Table of contents

Navigate to the Usage page
Overview of the Usage page