1. Log Management & Analysis
  2. Data model
Reference

The tables behind Log Management & Analysis

Log Management & Analysis ships with 12 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
12
Features
6, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Service context

Services, People and Users identify accountable people and operating scope.

Source and signal

Log streams carry endpoint and retention settings; log alerts carry query windows and match counts.

Response work

Incidents and incident updates document response; Problems, Changes and service requests carry follow-up decisions.

Supporting evidence

Assets add affected-item context; integration receipts retain processing outcomes, including stream registration.

Every table, by feature

Services and log streams

4 tablesAbout this feature
  • Services

    Services for log management operations

    Linked to People
  • Log streams

    Log Streams for log management operations

    Linked to Services
  • Log alerts

    Log Alerts for log management operations

    Linked to Log streams
  • Integration receipts

    Integration Receipts for log management operations

Log alerts

4 tablesAbout this feature
  • Log alerts

    Log Alerts for log management operations

    Linked to Log streams
  • Log streams

    Log Streams for log management operations

    Linked to Services
  • Services

    Services for log management operations

    Linked to People
  • Incidents

    Incidents for log management operations

    Linked to Services, Assets, People

Incidents and updates

5 tablesAbout this feature
  • Incidents

    Incidents for log management operations

    Linked to Services, Assets, People
  • Incident updates

    Incident Updates for log management operations

    Linked to Incidents, People
  • Services

    Services for log management operations

    Linked to People
  • Assets

    Assets for log management operations

    Linked to Services
  • People

    People for log management operations

    Linked to Users

Changes

4 tablesAbout this feature
  • Changes

    Changes for log management operations

    Linked to Services
  • Services

    Services for log management operations

    Linked to People
  • Incidents

    Incidents for log management operations

    Linked to Services, Assets, People
  • Problems

    Problems for log management operations

    Linked to Services, People

Problems and assets

5 tablesAbout this feature
  • Problems

    Problems for log management operations

    Linked to Services, People
  • Assets

    Assets for log management operations

    Linked to Services
  • Incidents

    Incidents for log management operations

    Linked to Services, Assets, People
  • Services

    Services for log management operations

    Linked to People
  • People

    People for log management operations

    Linked to Users

Requests and receipts

4 tablesAbout this feature
  • Service requests

    Service Requests for log management operations

    Linked to People, Services
  • Integration receipts

    Integration Receipts for log management operations

  • Services

    Services for log management operations

    Linked to People
  • People

    People for log management operations

    Linked to Users

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

A log alerts record references its log streams source, and a stream references its Services service. Incidents reference Services, Assets and People through their service, affected asset and assignee. Incident updates reference the incident and author. Problems, Changes and service requests each reference a service. A person links to a user account. Integration receipts retain provider and external event identifiers for processing review.

Migration order

  1. Import Users and People, then confirm the intended person-to-user links.
  2. Create Services with their owners and criticality.
  3. Load Assets and log streams against the correct services.
  4. Add open Incidents, Problems, Changes and service requests with the right people and services.
  5. Load log alerts and incident updates after their parent records exist; bring integration receipts with their external event identifiers.
  6. Review status values, dates, query windows and retention settings with each operating owner.

Set up Log Management & Analysis your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started