> For the complete documentation index, see [llms.txt](https://docs.inrupt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inrupt.com/ess/2.6/installation/customize-configurations/customization-pod-maintenance/modify-storage-metrics.md).

# Modify Storage Metrics Schedule

ESS includes a [Storage Metrics](https://github.com/inrupt/docs-gitbook/blob/main/ess/2.6/installation/services/service-pod-management/service-pod-storage.md#storage-metrics) feature to gather the following metrics:

* The total number of Pods
* The number of Pods that have been “Created” (where the provision has been confirmed)
* The number of Pods that have been “Deleted”(marked for deletion; i.e., soft-deleted).

Specifically, Storage Metrics runs as a [Kubernetes CronJobs](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/).

You can use Kustomize to modify the schedule of when the job runs.

## Example Customizations

{% hint style="warning" %}
**Important**\
Gathering Storage Metrics operations may negatively impact the performance of your system. If possible, schedule the CronJob to run at times when you can minimize its impact.
{% endhint %}

The provided overlays are configured to run every 2 minutes.

If instead you wish to schedule the job to run every day at midnight ( **`0 0 * * *`** ):

1. Go to your ESS installation directory:

   ```sh
   cd ${HOME}/ess
   ```
2. Create a **`kustomize-storage-metrics.yaml`** file with the following content:

   ```javascript
   apiVersion: batch/v1
   kind: CronJob
   metadata:
     name: ess-storage-metrics
   spec:
     schedule: '0 0 * * *'
   ```
3. Modify the **`kustomization.yaml`** (i.e., step 3 of the [Applying Your Customizations](/ess/2.6/installation.md#applying-your-customizations) procedure) to use **`kustomize-storage-metrics.yaml`** .\
   Specifically, add the highlighted content to the **`kustomization.yaml`** file to the `patches` section:

{% hint style="info" %}
**Tip**

If **`patches`** key does not exist in **`kustomization.yaml`** , add the **`patches`** key as well.
{% endhint %}

```yaml
# kustomization.yaml in your ESS installation directory

# ...  Preceding content omitted for brevity 
# ...

patches:
  - path: kustomize-storage-metrics.yaml
```

4\. Continue with the rest of the [Applying Your Customizations](/ess/2.6/installation.md#applying-your-customizations) procedure.

See also [Administration: Storage Metrics](/ess/2.6/administration/storage-metrics.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.inrupt.com/ess/2.6/installation/customize-configurations/customization-pod-maintenance/modify-storage-metrics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.