Skip to content

Monitor health and capacity

iVedha continuously monitors the health of the managed platform. Customers remain responsible for monitoring the behavior and outcomes of their own workloads.

A healthy platform does not automatically mean that every application, ingestion source, query, dashboard, or telemetry pipeline is working as expected.

What iVedha monitors

iVedha monitors managed-platform conditions such as:

  • Elasticsearch cluster health;
  • node and service availability;
  • storage and capacity conditions;
  • platform resource utilization;
  • managed Kubernetes and infrastructure health;
  • managed platform component availability.

When a platform condition requires intervention, iVedha can investigate and perform supported remediation.

Customers should not resize Kubernetes nodes, Elasticsearch nodes, disks, or other managed infrastructure directly.

What customers should monitor

Customers should monitor workload outcomes such as:

  • application indexing success;
  • search and query behavior;
  • ingestion completeness;
  • Elastic Agent health;
  • Fleet policy and integration health;
  • OpenTelemetry logs, metrics, and traces arriving as expected;
  • dashboards and alerts showing current data;
  • application availability and service objectives.

For observability workloads, a healthy Elastic Agent or OpenTelemetry Collector does not by itself prove that every expected signal is arriving correctly. Validate the actual logs, metrics, and traces used by the workload.

Review Elasticsearch health

Users with appropriate permissions can review high-level Elasticsearch cluster health.

curl --fail-with-body --user "<user>" \
  "https://<elasticsearch-hostname>/_cluster/health?pretty"

The main cluster states are:

Status Meaning
Green Primary and replica shards are available
Yellow Primary shards are available, but one or more replicas are unavailable
Red One or more primary shards are unavailable

Persistent yellow or any red condition should be investigated.

Do not change shard allocation settings or other managed Elasticsearch infrastructure directly.

Watch workload growth

Capacity requirements can change as workloads grow.

Review trends such as:

  • daily ingestion volume;
  • stored data;
  • retention period;
  • search and query demand;
  • observability signal volume;
  • number of monitored hosts, services, or applications;
  • expected business growth.

Short spikes do not necessarily require a permanent capacity change. Persistent growth or recurring pressure should trigger a capacity review.

When to consider more capacity

Request a capacity review when you observe conditions such as:

  • sustained ingestion growth;
  • stored data approaching the expected profile range;
  • longer retention requirements;
  • sustained indexing or search pressure;
  • recurring capacity-related warnings;
  • significant new applications or telemetry sources;
  • expected business growth that materially changes the workload.

Capacity changes should be based on workload evidence rather than selecting a larger profile without understanding the requirement.

Request a capacity review

Use the supported iVedha workflow:

  • AI chat: https://copilot.opsflw.io
  • Support portal: https://support.ivedha.com/

Provide, when available:

  • deployment reference;
  • current ingestion rate;
  • current stored data;
  • retention requirement;
  • expected growth;
  • workload type;
  • relevant performance or capacity symptoms.

iVedha can review the workload and recommend a supported capacity change.

Do not resize managed Kubernetes, Elasticsearch, storage, or infrastructure resources directly.

For initial planning ranges, see Choose capacity and topology.