IT diagnostics via logs

How can AI help you analyse logs and prepare an IT diagnosis?

1250 € per session, excl. VAT

In short

IT support, operations and development teams learn to work with logs using the chosen AI assistant: remove secrets and identifiers, align timestamps, build a timeline, separate observations from hypotheses and propose non-destructive tests. Deliverables: a sourced timeline, a hypothesis tree and a diagnostic ticket that is ready for escalation to the next team.

Why this training?

The problem
Teams are overwhelmed by the volume of logs during an incident, making diagnosis difficult and slow.
What it costs today
Repeated messages and different time zones obscure the answer, leading to incomplete or delayed diagnoses.
Why this skill
This skill is necessary to prepare a documented and actionable IT diagnosis from cleaned and structured logs using an AI assistant capable of log analysis.
What you gain
The participant and the company gain in diagnosis reliability and autonomy in preparing incident escalation.

Objectives of this training

  • Remove secrets and identifiers from logs before analysis
  • Harmonize timestamps from different sources into a timeline
  • Construct a sourced timeline of the incident with the chosen AI assistant
  • Separate factual observations from diagnostic hypotheses
  • Propose non-destructive tests to validate hypotheses
  • Draft a complete diagnostic ticket ready for immediate escalation

Who is it for and what are the prerequisites?

Roles and tasks concerned

  • IT Support Teams Level 1
  • IT Support Teams Level 2
  • Operations Teams
  • Developers in charge of incidents

Prior skills

  • AI Fundamentals and AI Prompting completed, or equivalent experience (a learning prerequisite, not a registration condition).
  • Regular reading of application or system logs
  • Basic practice of an AI assistant capable of log analysis
  • A paid subscription to an AI solution offering the features used, the organisation’s authorisation for third-party tools, and the actual accounts and access rights.

To prepare before the session

  • Activated account for the chosen AI assistant
  • Authorized fictional log documents or data
  • Current reading of application or system logs

What you will work on

  1. Cleanse before analysis

    The participant is able to identify and mask sensitive data in logs.

  2. Harmonize and order

    The participant can build a unique and coherent timeline from multiple log sources.

  3. Observations and hypotheses

    The participant knows how to distinguish observed facts in logs from interpretations or diagnostic hypotheses.

  4. Test and hand over

    The participant can propose non-destructive tests and write a complete diagnostic ticket.

What you take away

  • Sourced incident timeline
  • Hypothesis tree
  • Diagnostic ticket

Method and assessment

  • Fictional logs from several sources
  • Log line cited for every observation
  • Ticket reviewed by the colleague taking over

The diagnosis is assessed on the absence of residual secrets or identifiers, timeline accuracy, separation of observations and hypotheses, the non-destructive nature of proposed tests and whether a colleague can take over the ticket.

Frequently asked questions

What concrete result does this course deliver?

The team has a method for turning traces into a clear, safe diagnostic ticket ready for escalation. Deliverables: sourced incident timeline, hypothesis tree, diagnostic ticket.

Who is this course for and what are the prerequisites?

It is designed for: first and second line it support teams, operations teams, developers handling incidents. Comfortable reading application or system logs and basic experience with the chosen AI assistant. Exercise logs are fictional; no access to a real system is used.

What data and access need to be arranged?

Exercise logs are fictional. No real logs are shared with the chosen AI assistant without prior masking and the organisation's authorisation. Required tools and licences are checked before the session; no subscription is included in the price.

What practical exercise is completed?

On fictional logs, participants remove secrets and identifiers, align timestamps, build a timeline, group symptoms, separate observations from hypotheses, then propose non-destructive tests and a documented escalation.

What are the limits and who validates the results?

The chosen AI assistant runs no commands and fixes nothing automatically. The workshop does not claim to find every vulnerability; actions on systems are decided and carried out by authorised people.

Can the course be adapted to our line of work?

During scoping, the fictional logs are chosen to resemble the team's environment: web application, workstation, network, database or cloud service.

How is the session organised and what does it cost?

Half-day, private in-person session for up to 12 participants. The fee is €1,250 excluding VAT per session. Date and location are agreed during scoping; each session runs in a single language: French, Dutch or English.

Related courses

Last updated: