Observability Review

Overview

A fixed-price, advisory-only assessment engagement delivering a comprehensive health check of the Customer's existing Elastic observability implementation. Elastic consultants assess the current-state implementation across five structured review domains — using stakeholder interviews, read-only access, configuration review, and representative sampling — and deliver a risk-rated findings report with a prioritised 30/90/180-day remediation roadmap.

This engagement is advisory only. Elastic consultants analyze, audit, and advise. No configuration changes, agent deployments, dashboard modifications, alert rule changes, or any other implementation activities are performed during this engagement. All implementation and remediation work is out of scope and requires a separate follow-on engagement.

Scope

• Phase 1: Project kickoff; read-only access verification; scope statement confirmed; success criteria agreed; interview schedule established
• Phase 2: Assessment approach finalized; sampling plan documented; interview guides prepared per review domain; initial environment inventory captured
• Phase 3: Assessment of five review domains:
  • Infrastructure Monitoring: Agent deployment coverage, metric quality, baselines, capacity trends
  • APM: Instrumentation coverage, distributed tracing, golden signals, SLOs
  • Log Management: Log source coverage, ECS alignment, ILM and retention configuration
  • Dashboards & Visualization: Coverage, quality, usability, RBAC alignment
  • Alerting: Rule coverage, noise and false-positive assessment, escalation paths, SLO alerting
• Phase 4: Cross-domain theme analysis; maturity scores assigned; 30/90/180-day remediation roadmap produced; Observability Health Check Report completed
• Phase 5: Findings presentation to all stakeholders; remediation roadmap walkthrough; follow-on engagement recommendations discussed

The review is conducted using stakeholder interviews, read-only access to relevant Elastic components, configuration and content review, and representative sampling where full inventory review is not practical within standard scope. Where representative sampling is used, this is documented in the final report.

Out of scope

This engagement does not include:

• Implementation of any recommendations from the findings report
• Agent deployment, reconfiguration, or uninstallation
• APM instrumentation changes
• Dashboard creation, editing, migration, or deletion
• Alert rule creation, tuning, connector changes, or deletion
• Log pipeline redesign or parsing changes
• Data migration or reindexing
• Future-state architecture design beyond roadmap-level recommendations
• Forensic audit of every dashboard, alert rule, service, index, or data source
• Greenfield observability deployments or customers without an existing Elastic deployment
• Multi-environment or multi-deployment reviews beyond the single production environment in scope
• Review domains beyond the five standard areas; additional domains require a change order

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 observability deployment in scope — at least one production Elastic cluster in active use for observability
• Consultant is granted read-only access sufficient to assess all five review domains (Kibana read-only, Elasticsearch read-only, cloud console read-only where applicable) before Day 1
• Scope is limited to one production environment and one primary Elastic deployment
• Customer domain owners (Infrastructure Lead, APM/Dev Lead, Log/Platform Lead, Dashboard Owners, On-Call/Monitoring Lead) are available for interviews and walkthroughs at approximately 2–3 hours per day throughout the engagement
• Where customer scale is large, representative sampling is used and documented; the engagement does not guarantee a forensic review of every observability asset
• No implementation activities are performed during this engagement — this is an advisory assessment only

If any of the above assumptions are not met, Elastic may adjust the schedule, limit the assessment to domains where sufficient access and participation is available, or require a change order.

Deliverables

• One (1) Observability Health Check Report, comprising:
  • Executive summary and overall observability maturity rating
  • Maturity assessment by review domain (Infrastructure Monitoring, APM, Log Management, Dashboards, Alerting)
  • Risk-rated findings (Critical/High/Medium/Low) with evidence references per review domain
  • 30/90/180-day prioritized remediation roadmap
  • Follow-on Elastic Professional Services engagement recommendations
  • Scope, assumptions, and limitations documentation
• One (1) Findings register (finding ID, domain, description, severity, recommended action, recommended horizon)

Completion

The engagement will be considered complete upon: all five review domains assessed; findings documented with supporting evidence; maturity scores assigned; Observability Health Check Report delivered; 30/90/180-day remediation roadmap delivered. The engagement may also be deemed complete if Customer delays, is unavailable, fails to provide required access, or is otherwise unable to participate after Elastic has made commercially reasonable efforts to deliver within the agreed engagement window. Where access or participation limitations restrict the assessment, findings confidence levels and limitations will be documented in the report.

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.