Skip to content

Manage maintenance

The maintenance window defines the preferred time for planned platform changes that can affect service availability or performance.

The initial maintenance schedule is selected during Marketplace deployment.

Platform maintenance configuration is managed through the iVedha AI chat:

https://copilot.opsflw.io

Understand the maintenance window

The maintenance schedule includes:

  • day or recurrence;
  • start time;
  • time zone;
  • maintenance duration.

Always confirm the configured time zone when reviewing or changing the schedule.

Do not assume that the displayed time is UTC or your local workstation time.

Before planned maintenance

Before a maintenance event that can affect service availability:

  • notify affected users and application owners;
  • confirm important applications can retry temporary connection failures;
  • review active incidents or business-critical processing;
  • avoid scheduling major customer-side changes during the same window when possible.

For observability workloads, temporary interruptions can cause agents or applications to buffer and retry telemetry.

For search workloads, applications should handle temporary Elasticsearch connection failures using appropriate retry behavior.

Change the maintenance window

To request a maintenance-window change:

  1. Sign in to the iVedha AI chat application.
  2. Select or identify the deployment.
  3. Ask the assistant to change the maintenance window.
  4. Provide the requested day, start time, time zone, and other schedule information.
  5. Review the requested change.
  6. Confirm the change when prompted.
  7. Wait for confirmation that the new configuration has been applied.

Allow a few minutes for the updated configuration to synchronize.

Verify the schedule

After the change completes, confirm the maintenance schedule through the supported iVedha workflow.

Make sure the configured:

  • day;
  • start time;
  • time zone;
  • recurrence

match the intended maintenance window.

After maintenance

After a maintenance event, confirm that normal workload behavior has resumed.

Check:

  • Elasticsearch is available;
  • Kibana loads normally;
  • users can authenticate;
  • Elastic Agents return to Healthy in Fleet;
  • OpenTelemetry logs, metrics, and traces continue to arrive;
  • application indexing and searches are working.

iVedha monitors managed-platform health during and after supported maintenance operations.

Emergency maintenance

Some urgent platform changes may need to occur outside the preferred maintenance window to protect availability, security, or data integrity.

When possible, iVedha will communicate the expected impact and status through the configured support contacts.

Need help

If the maintenance schedule cannot be changed or service does not recover as expected:

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

Provide the deployment reference from your deployment notification.

Do not include passwords, API keys, private keys, or other secrets.

Choose what to do next