Resident Engineer Essentials

Most Splunk and Cribl problems are not projects. They are a source that needs onboarding this week, a pipeline that started dropping fields after a vendor update, a dashboard a director asked for, an upgrade that needs a plan. Hiring for that is slow and expensive; opening a SOW for each one is slower.

Resident Engineer gives you a named VisiCore engineer on a predictable monthly allotment under the X10 engagement model. Every task is a ticket in the client portal, so you can see where the hours went, and unused time carries over instead of vanishing.

• A named engineer who knows your environment, not a rotating bench
• Predictable monthly capacity with one month of carryover
• Every request is a ticket in the X10 portal with its hours and resolution
• Twenty hours a month for the questions that are not projects

Service

Resident Engineer – Essentials

Part number

VC-SS-RE-ESS

Family

Resident Engineer

Platforms

Cribl, Splunk

Engagement

Ongoing subscription, 12-month term

Pricing

Stated on the Order Form. Request a quote.

Resident Engineer is a 12-month subscription that embeds a named VisiCore engineer with your team. Work is delivered through recurring scheduled sessions and through tickets you open in the X10 client portal, each drawing from a monthly allotment of hours.

The engineer handles ad-hoc Splunk and Cribl work, gives proactive guidance on upgrades, releases and performance, and reports monthly on usage and platform health. Hours can be used across Cribl Stream, Edge, Search and Lake and across Splunk Cloud and Enterprise.

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.

• A named VisiCore engineer assigned for the term who learns your environment, conventions and priorities
• Recurring scheduled working sessions for planned work, set at kickoff
• X10 portal tickets for ad-hoc work: onboarding new sources, pipeline and route fixes, search and dashboard help, FinOps and license questions, configuration reviews
• Proactive guidance on upgrades, release notes, performance and best practices across Cribl and Splunk
• Monthly usage and health summary: hours used and carried over, tickets closed, open risks and recommendations
• Access to VisiCore's open-source apps and packs with installation support
• Hours are usable across Cribl Stream, Edge, Search and Lake, and Splunk Cloud and Enterprise, as your tickets require

Quantities

Deliverables

• Kickoff notes: environment inventory, access confirmed, session cadence agreed
• Completed tickets in the X10 portal, each with its resolution and the hours drawn
• Session notes and recordings where permitted
• Monthly usage and health summary
• Upgrade and release recommendations as they arise

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.

The monthly allotment stated on the Order Form is the committed amount of VisiCore engineer time for each month of the term. Time is drawn against tickets and scheduled sessions and tracked in the X10 client portal.

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
• Performance testing and benchmarking
• Formal product training courses beyond the guidance given in sessions and tickets
• After-hours or on-call coverage. A 24×7 coverage add-on is available separately
• Work beyond the monthly allotment, which is billed as additional credits or scoped as a custom SOW
• Full project delivery that belongs in an Activation, Migration or Content Factory engagement
• Any service or activity not described in the Scope section of this brief

12 months.

• The term is 12 months from the start date, renewable by mutual agreement.
• Monthly allotments reset on the first of each month. Unused time carries over for one month and is otherwise forfeited; carried-over time is used before the current month's allotment.
• Either party may end the term for convenience with 60 days' written notice. Pre-paid, unused months are refunded; the current month is not.

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
• Name a counterpart on your side who prioritizes tickets and attends the scheduled sessions
• Open requests as tickets in the X10 client portal so the hours and history are tracked
• Remote access so the engineer can work independently between sessions is strongly recommended; without it, work is limited to the scheduled 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.