> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/manage/monitor-and-automate-silk/monitor-your-silk-environment.md).

# Monitor Your Silk Environment

Track system health, investigate performance changes, and monitor capacity and replication using Silk's monitoring tools.

Monitoring helps you understand how your Silk environment is operating, recognize changes in the workload behavior, and address emerging issues before they affect applications.

Use Silk Flex for an overview of your DataPods, the SDP Management Console for detailed operational monitoring, and Silk Clarity for longer-term analysis. Together, these tools provide visibility into system health, performance, capacity consumption, and replication activity.

## Choose the right monitoring tool

<table><thead><tr><th width="231.1112060546875">Tool</th><th>Use it to</th></tr></thead><tbody><tr><td><strong>Silk Flex</strong></td><td>Review DataPod status and key metrics across the DataPods managed by your Flex instance. Check deployment and scaling tasks and access their logs.</td></tr><tr><td><strong>SDP Management Console</strong></td><td>Investigate a specific DataPod's components, performance, capacity, replication sessions, and events.</td></tr><tr><td><strong>Silk Clarity</strong></td><td>Review historical performance, capacity, and system information over longer periods to identify trends and support planning.</td></tr><tr><td><strong>External syslog destination</strong></td><td>Collect DataPod logs centrally alongside logs from other systems in your environment.</td></tr></tbody></table>

Flex displays key information like DataPod state, physical capacity usage, bandwidth, IOPS, and latency. Open a DataPod's SDP Management Console when you need to investigate its activity in more detail.

## Check DataPod health and recent events

Start with the SDP Management Console dashboard. It brings together the DataPod's current state, component counts, capacity usage, performance metrics, and event notifications.

<figure><img src="https://3917177233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7UwK9S9vo5qr2qGPjCUv%2Fuploads%2FQCqxxdvmZvZw29aq2Lnu%2Fimage.png?alt=media&amp;token=93f658a9-f0db-4625-9202-9ba39b781910" alt=""><figcaption></figcaption></figure>

<details>

<summary><strong>DataPod state</strong></summary>

Check whether the system reports a healthy state or a condition requiring attention.

</details>

<details>

<summary><strong>Component health</strong></summary>

Open **System > Components** to inspect c.nodes, m.nodes, and d.nodes.

</details>

<details>

<summary><strong>Event notifications</strong></summary>

Review the **Info**, **Warning**, **Error**, and **Critical** categories. Select a category to open the associated event log.

</details>

{% hint style="info" %}
**Recent changes?**

Consider whether a performance or health change coincides with a configuration update, scaling operation, or host connectivity change.
{% endhint %}

Use **Events > Log** to investigate individual events. Each entry includes the DataPod time, severity level, message, and labels. Filter by severity or by labels like `HOST`, `SYSTEM`, `REPLICATION`, `VOLUME`, OR `IO_CONNECTIVITY` to narrow your investigation.

Prioritize critical events and errors, then review related warnings and informational messages for context.

## Monitor performance and workload behavior

The SDP Management Console provides two complementary performance views:

{% columns %}
{% column %}
**Performance > Monitor**

Review current activity and recent trends.
{% endcolumn %}

{% column %}
**Performance > Analysis**

Investigate a selected time range and isolate activity by volume, volume group, read/write operation, or block size.
{% endcolumn %}
{% endcolumns %}

### Understand the core performance metrics

<table><thead><tr><th width="111.85174560546875">Metric</th><th>What it shows</th><th>What to examine</th></tr></thead><tbody><tr><td><strong>Bandwidth</strong></td><td>The amount of data read or written per second, displayed in MB/s.</td><td>Changes in throughput, sustained demand, and the balance between reads and writes.</td></tr><tr><td><strong>IOPS</strong></td><td>The number of input/output operations completed per second.</td><td>Workload intensity, bursts of activity, and changes in the read/write mix.</td></tr><tr><td><strong>Latency</strong></td><td>The time taken to respond to an IO request, displayed in milliseconds.</td><td>Increases in response time and whether they coincide with changes in workload activity.</td></tr><tr><td><strong>Replication bandwidth</strong></td><td>Inbound and outbound replication traffic, displayed in Mbps.</td><td>Changes in replication traffic and their relationship to session status and RPO compliance.</td></tr></tbody></table>

Read these metrics together. A rise in IOPS or bandwidth may reflect expected application activity. A simultaneous increase in latency may warrant closer investigation.

Block size and the proportion of reads and writes also help explain workload behavior. Compare changes against a normal operating period for the same application rather than relying on a single metric.

### Investigate a performance change

Follow this sequence to narrow your investigation:

{% stepper %}
{% step %}

#### Identify the time window

Note when the application slowdown or unexpected activity began.
{% endstep %}

{% step %}

#### Review the Monitor view

Check bandwidth, IOPS, latency, and replication traffic around that time.
{% endstep %}

{% step %}

#### Open Analysis

Select a point on a Monitor graph or navigate directly to **Performance > Analysis**.
{% endstep %}

{% step %}

#### Filter the workload

Select the relevant volumes or volume groups, then refine the view by read/write activity or block size.
{% endstep %}

{% step %}

#### Compare events and changes

Review the event log and any relevant Flex tasks for activity during the same period.
{% endstep %}
{% endstepper %}

The **Analysis** page also supports **Export to Excel**, allowing you to share the selected performance data or examine it outside the console.

{% hint style="info" %}
**Monitoring guidance**

DataPod metrics describe activity at the Silk layer. When investigating application response times, compare them with application, database, host, and cloud-network observations from the same period.
{% endhint %}

## Track capacity usage and growth

Monitor both allocated and physical capacity. They measure different aspects of consumption:

* **Allocated capacity:** The amount of storage consumed before data reduction.
* **Physical capacity:** The amount of storage consume after data reduction (including compression and deduplication).

The SDP Management Console dashboard shows both capacity indicators and a capacity trend graph. Use them together to understand current usage and how quickly consumption is changing.

For a more detailed breakdown, open **System > General** to review capacity information for volumes, snapshots, and views. Review individual volume groups when you need to understand which applications or data copies are contributing to growth.

As part of a routine capacity review:

* [ ] Check remaining capacity and recent growth
* [ ] Review both allocated and physical usage
* [ ] Investigate unexpected increases
* [ ] Review volume group quotas and capacity policies where applicable
* [ ] Allow time for capacity changes before usage becomes critical

Capacity policies can trigger notifications and automated actions as thresholds are reached, including deletion of eligible snapshots or views. Review the applicable policy so that you understand the consequences of continued growth.

For capacity definitions and planning guidance, see [Plan DataPod Capacity](/deploy/plan-your-deployment/plan-datapod-capacity.md).

## Verify replication status and RPO compliance

If your environment uses replication, monitor the sessions as well as the traffic they generate.

In **Snapshots & Replication > Replication**, review session status and **RPO History**. RPO, or recovery point objective, represents the acceptable data-loss window for recovery.

**RPO History** shows how consistently a session is meeting its configured objective over time. Use it to distinguish a session that is transferring data from one that is keeping pace with its recovery requirements.

When investigating replication behavior:

* Check whether the session is active, synchronized, suspended, or reporting an issue.
* Review **RPO History** for missed objectives.
* Compare the affected periods with replication bandwidth and source workload activity.
* Review replication-related events for additional context.

{% hint style="info" %}
Setting an RPO defines the objective. Monitor session status and RPO History to confirm whether replication is meeting your RPO.
{% endhint %}

For replication concepts and recovery options, see [Replication and Recovery](/manage/protect-your-environment/replication-and-recovery.md).

## Review longer-term trends in Clarity

Silk Clarity provides historical analysis using operational information collected through the call home mechanism. This information includes capacity statistics, performance statistics, and system events.

Each DataPod sends operational information to Clarity once per hour through the call home mechanism. Clarity retains this information for up to two years.

Use Clarity to examine longer-term patterns, including:

* Capacity growth over successive weeks or months
* Recurring workload peaks
* Changes in performance following workload or configuration changes
* Historical context for resource planning

Since Clarity receives information through call home, use the SDP Management Console when you need to inspect current DataPod activity.

## Centralize logs with syslog

You can forward DataPod logs to an external syslog destination through **System > External Configuration** in the SDP Management Console.

Centralized logging helps your operations team review Silk events alongside activity from applications, hosts, and other infrastructure. Syslog configuration supports a destination hostname or IP address, a port, TCP or UDP transport, and an option to include audit entries.

The DataPod forwards logs to the destination, and your organization manages the external syslog service.

After configuration, verify that the destination receives DataPod messages. When using UDP, confirm delivery at the receiving server because the DataPod cannot actively monitor the connection.

For setup instructions, see the **Create a Syslog Server** section of the [SDP Management Console User Guide](https://support.silk.us/sys/document/preview/Silk-Cloud-Platform-User-Guide-240223011600..pdf).

## Collect context for troubleshooting

When an issue requires further investigation, capture enough information to connect the symptoms with the relevant system activity:

* Affected DataPod, volumes, and applications
* Start time, duration, and time zone
* Observed application impact
* Relevant performance graphs or exported data
* Related event messages
* Recent configuration, scaling, or workload changes

For deployment or orchestration issues, review the relevant task logs in Flex. You can also download a full Flex log bundle to provide to Silk Support.

## Related resources

{% content-ref url="/spaces/jI1rjszhUJU6LG8J53d0/pages/zcHZBR1wDVYG5AtIoJrE" %}
[Silk Clarity Overview](/learn/products-and-core-concepts/silk-product-fundamentals/silk-clarity-overview.md)
{% endcontent-ref %}

{% content-ref url="/spaces/zRoeFiUtkaS7g8f3vjz5/pages/FXudgU7rJdcdoOSoDNH5" %}
[Plan DataPod Capacity](/deploy/plan-your-deployment/plan-datapod-capacity.md)
{% endcontent-ref %}

{% content-ref url="/pages/ZUkR7xovQDMAbI7eiZ8b" %}
[Replication and Recovery](/manage/protect-your-environment/replication-and-recovery.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.silk.us/manage/monitor-and-automate-silk/monitor-your-silk-environment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
