Infrastructure Monitoring Accelerator

Overview

A fixed-price, time-boxed professional services engagement delivering unified infrastructure monitoring visibility across agreed in-scope layers — hosts/VMs, Kubernetes, and cloud resources — on an existing Elastic deployment. Elastic consultants design the monitoring architecture, deploy agents, validate telemetry, configure dashboards and alerting, and train the customer team within a structured customer-facing engagement window of 11 consecutive working days.

Scope

• Phase 0 (Day 0 — Elastic internal): Pre-engagement preparation; draft architecture and delivery approach; internal alignment
• Phase 1 (Day 1): Project kickoff; infrastructure discovery and scope confirmation; architecture review; success criteria agreed; deployment plan documented
• Phase 2 (Day 2): Implementation plan finalized; integration assumptions documented; delivery timeline confirmed
• Phase 3 (Days 3–4): Elastic Agent deployed to agreed hosts/VMs; Kubernetes monitoring (cluster, node, pod, container metrics); cloud resource integration (agreed single provider); telemetry validated; baseline metrics recorded; infrastructure relationships documented
• Phase 4 (Days 5–7): Operational priorities documented; dashboards built (Infrastructure Health, K8s, Cloud, Capacity, operational); up to 5 custom alerting rules configured; OOTB alerting reviewed; RBAC and access model reviewed
• Phase 5 (Days 8–9): Production telemetry validated; dashboards refined; alerting tuned; troubleshooting runbooks drafted
• Phase 6 (Days 10–11): Team enablement session; 2–3 runbooks finalized; documentation handover; and success criteria verification; post-delivery support plan; 30-day check-in scheduled

Out of scope

This engagement does not include:

• Infrastructure rearchitecture or Elastic platform deployment from scratch
• Large-scale or multi-region infrastructure onboarding beyond the agreed bounded scope
• More than one cloud provider (additional providers require a change order)
• More than 5 custom alerting rules (additional rules require a change order)
• Advanced dashboard customization beyond agreed operational priorities
• Multi-environment deployments — single production scope only; additional environments require a change order
• Kubernetes monitoring beyond the agreed cluster count (additional clusters require a change order)
• Log ingestion or management — this engagement covers infrastructure metrics only
• Full SIEM or security monitoring integration
• Post-engagement managed services, ongoing support, or further infrastructure expansion beyond the 30-day check-in call

Any work outside the scope above requires a mutually executed change order and may result in additional fees, revised assumptions, and schedule changes.

Engagement timeline

• Scheduled to commence approximately 6–8 weeks after purchase, subject to resource availability and Customer readiness
• Delivered by an Elastic Consultant or a certified partner resource under Elastic oversight
• Unless otherwise agreed in writing, the services will be delivered remotely
• Delivery is expected to occur over contiguous business days or contiguous calendar weeks, as scheduled by Elastic
• If delivery is delayed, interrupted, or rescheduled due to Customer availability, access issues, environment readiness, or other Customer dependencies, Elastic may reassign resources, adjust the schedule, or require an Order Form (change order)
• Time scheduled for the engagement that cannot be used due to Customer delay, unavailability, failure to meet dependencies, or inability to provide required access will count against the total consulting days

Fixed-price conditions and assumptions

• Customer has an existing Elastic deployment available for infrastructure monitoring onboarding before Day 1
• Infrastructure scope is bounded and agreed before kickoff — approximate host/VM count, Kubernetes cluster count, and cloud provider confirmed
• One production scope is in focus; lower-environment validation is available where possible
• Required customer access, credentials, and deployment permissions are confirmed before Day 1
• Customer technical resources (infrastructure engineers, DevOps/SRE, platform administrators) are available throughout the engagement
• Production change approvals and notification channels are prearranged before engagement commencement
• Cloud monitoring scope is limited to a single provider unless otherwise agreed
• Dashboard outputs depend on available telemetry and agreed operational priorities
• Initial alerting is limited to agreed operational priorities — up to 5 custom alert rules within the package scope
• Access model implementation depends on customer permissions and governance
• Advanced dashboard customisation is not included in the standard package
• If any of the above assumptions are not met, Elastic may adjust the schedule, limit the services performed to fit the fixed-price scope, count impacted time against the allocated consulting days, or require a change order.

Deliverables

Discovery & Planning

• One (1) monitoring architecture design document, finalized following infrastructure discovery and scope confirmation
• One (1) success criteria and deployment plan document, capturing the success criteria and deployment approach agreed at kickoff
• One (1) implementation plan document, documenting integration assumptions and the confirmed delivery timeline

Deployment & Telemetry (bounded to the hosts/VMs, clusters, and cloud provider confirmed during scope confirmation; anything beyond that baseline requires a change order)

• Elastic Agent deployed and validated across the hosts/VMs confirmed in scope
• Kubernetes monitoring operational for the clusters confirmed in scope, covering cluster, node, pod, and container-level metrics
• Cloud resource monitoring operational for the one (1) single cloud provider confirmed in scope
• One (1) baseline metrics report, documenting baseline telemetry for all in-scope hosts/VMs, clusters, and cloud resources
• One (1) infrastructure relationship map, depicting dependencies between in-scope infrastructure components

Dashboards & Alerting

• Five (5) operational dashboards: Infrastructure Health, Kubernetes, Cloud, Capacity, and one dashboard of choice
• Up to five (5) custom alerting rules, configured and tested against operational priorities agreed in Phase 4
• Out-of-the-box Elastic alerting reviewed, with recommendations provided (configuration changes beyond the five (5) custom rules are out of scope unless agreed via change order)
• RBAC and access model reviewed against the customer's existing role structure, with configuration applied for up to three (3) role profiles using Elastic's built-in role definitions

Validation & Enablement

• Production telemetry validated for all in-scope hosts/VMs, clusters, and cloud resources
• Two (2) infrastructure troubleshooting runbooks, covering [host/VM resource exhaustion] and [Kubernetes pod/container failure investigation] 
• One (1) team enablement session (hands-on training; format and duration to be confirmed) with documentation handover of all deliverables produced during the engagement

Closeout

• One (1) success criteria verification summary, confirming delivery against the criteria agreed at kickoff
• One (1) post-delivery support plan and escalation guide, defining the post-go-live support window, escalation path, and contacts
• 30-day check-in call, scheduled with a defined agenda (success criteria review)

Completion

The engagement will be considered complete upon delivery of the working AI assistant prototype, the Results Review Workshop, and project documentation. The engagement may also be deemed complete if Customer delays, is unavailable, fails to meet required prerequisites, or is otherwise unable to participate after Elastic has made commercially reasonable efforts to deliver within the agreed engagement window.

General terms

Capitalized terms used but not defined in this package description have the meanings given to them in the Order Form, the applicable Service Description, or the Elastic Services Agreement.

No formal Customer signoff and no milestone or deliverable acceptance process applies to this fixed-price Services Package. Each Service is deemed accepted upon Completion.

"Completion" means, with respect to a Service, the point at which Elastic has performed the activities within the scope of this Services Package, including (where applicable) delivery of any written report, materials, or knowledge transfer session described in this package's scope, or the expiry of the time-boxed engagement period for this package, whichever occurs first. Completion does not require Customer signoff or acceptance of any deliverable.

Customer is solely responsible for the backup, maintenance, and security of its environment, systems, and data. Elastic is not responsible for any configuration changes, data loss, downtime, or other impact to Customer's environment arising from or in connection with the Service.

This engagement delivers a configured net-new, self-managed Elastic document search solution, including search use case analysis, data modeling and ingestion, advanced example query implementation, advanced RBAC configuration, infrastructure provisioning, and a final report, within the defined fixed-price scope. Elastic does not guarantee any specific performance, cost, operational, or business outcome beyond the deliverables defined above. Customer remains solely responsible for ongoing operations, configuration changes made outside the engagement scope, and all post-engagement activities related to its environment.

References in this package to validation, testing, acceptance tests or acceptance test harnesses, golden queries, launch readiness, or go-live describe activities performed, demonstrated, or delivered by Elastic and do not create any Customer acceptance, signoff, testing, or payment condition. Completion occurs as defined in this package regardless of any such activity, and no portion of the fees is withheld or deferred pending any test result, validation, or go-live event.