Cribl Activation Advanced

A Cribl deployment that is designed well from the start is cheap to run and easy to extend. One that grew out of a proof of concept costs more every month in licence, compute and engineer time.

Cribl Activation puts a VisiCore certified engineer beside your team for the first 90 days, so the architecture, naming, routing and pipeline conventions are right before the data volume arrives.

• Kickoff to production deployment in 90 days or less
• Best practices applied to your goals, not a generic install
• Your team runs it on day 91: knowledge transfer is built into every session
• Three use cases live, plus a Resident Engineer for three months after activation

Service

Cribl Activation – Advanced

Part number

VC-PS-ACT-ADV

Family

Cribl Activation

Platforms

Cribl

Engagement

Fixed-scope project, 90 days service period

Pricing

Stated on the Order Form. Request a quote.

Cribl Activation is a fixed-scope consulting engagement that takes a new Cribl Stream or Cribl Edge purchase from kickoff to a documented production deployment. It teaches your team the fundamentals of deploying and operating Cribl while delivering the first use cases on live data.

A dedicated VisiCore engineer, certified by Cribl, guides the work. By day 90 your team should be able to onboard new sources, build pipelines and operate the platform against your own data goals.

VisiCore delivers this service remotely through scheduled working sessions led by a named VisiCore engineer who holds current Cribl and/or Splunk certifications. On-site days can be added under a separate order.

Unless agreed otherwise in writing, the engagement starts within one week of VisiCore accepting the signed order. The working schedule is set at the kickoff meeting.

VisiCore provides an agenda before each session, including which of your team members should attend. Sessions run one to four hours.

Every task, decision and deliverable is tracked as a ticket in the X10 client portal, so your team always has a current record of what was done and why.

Scope summary. The base scope below plus 3 customer-chosen use cases, delivered in approximately 20 working sessions.

• Architecture: deployment architecture, sizing and dependency planning for the environment in scope
• Use-case workshop: requirements, success criteria and priority for each use case
• Deployment: Cribl Stream and/or Edge installed on customer infrastructure, or worker groups configured in Cribl.Cloud
• Source and destination configuration for the use cases in scope, including routes and pipelines
• Production-readiness health check before cutover
• As-built documentation of the deployed architecture and configuration
• Knowledge transfer in every working session, with recordings where permitted
• A data source is a unique system or platform type (for example Palo Alto firewalls, Windows Event Logs or Linux syslog), not an individual device or protocol.
• Resident Engineer after activation: two working sessions per month for three months covering performance tuning, upgrade planning, onboarding guidance for new sources, pipeline optimization and FinOps review

Quantities

Deliverables

• Architecture document and dependency plan
• Use-case definitions with acceptance criteria
• Working Cribl deployment with the in-scope use cases live in production
• As-built configuration documentation
• Production-readiness health check report
• Session recordings and knowledge-transfer notes in the X10 portal

VisiCore Technology Group provides the services described in this brief under the applicable Order Form and the VisiCore Master Services Agreement, or another written agreement in place between VisiCore and the customer.

Session and hour counts in this brief are planning estimates for the work described, not a guarantee of a fixed number of service hours.

Pricing is stated on the Order Form. Contact VisiCore for a quote.

The following are not included unless added to the Order Form:

• Installation, modification or maintenance of customer hardware, operating systems, containers, firewalls or load balancers
• Changes to the configuration of source or destination systems outside the platform in scope
• Backup and recovery, or day-to-day maintenance, of the customer's environment
• Performance testing and benchmarking
• Formal product training beyond the guidance given in working sessions
• Any service or activity not explicitly listed in the Scope section of this brief
• Custom scripting to pull or push data from systems that have no native Cribl integration (see Content Factory: Custom Pack)
• CI/CD or infrastructure-as-code automation of the Cribl deployment (available as a custom SOW)
• Migration of existing content from another platform (see SIEM Migration and Cribl Search Activation)

90 days.

• The customer has 90 days from the start date (the "Service Period") to schedule and use the services in this brief.
• The service ends automatically at the close of the Service Period unless VisiCore agrees in writing to extend it.
• Unused portions of the service are non-refundable and non-creditable.
• VisiCore may deliver services after the Service Period if the customer gives written notice at least 30 days before it ends and VisiCore agrees.
• The Resident Engineer sessions included in this tier are not subject to the Service Period expiry and forfeiture rules above, which apply to the Activation work only. The sessions start within one week of the Activation ending, unless agreed otherwise in writing, and run for the stated number of months.

To deliver this service on schedule, the customer agrees to:

• Name an engagement lead with the authority to make decisions and accept deliverables
• Provide the accounts, access and network connectivity VisiCore engineers need before the first working session
• Attend scheduled sessions (one to four hours each) and complete prerequisite work before them
• Bring the subject-matter experts who own the systems being integrated
• Review each deliverable within five business days of hand-off. Without written feedback in that window the deliverable is accepted; non-blocking issues are handled after acceptance
• Have the target infrastructure or Cribl.Cloud organization provisioned and reachable before the first working session
• Provide representative sample data, with no personal data, so engineers can build pipelines offline between sessions
• Use cases are defined in the workshop. A use case can be swapped only before work on it has started
• Schedule the Resident Engineer sessions at the start of the post-activation period and provide remote access so the engineer can work independently between sessions

Meetings are scheduled at mutually agreed times during VisiCore business hours.

The customer must give at least 48 hours' written notice to cancel, reschedule or shorten a scheduled meeting. Without that notice, VisiCore may count the meeting as delivered.