Skip to content
Bijstaan
PluginsThe suiteDocumentation

GLPI Service

glpi-service

The services people actually depend on, mapped over your CMDB — and a record of where everything in it came from.

Full documentationRepository
version
0.1.0
requires
GLPI 11.0
plugin key
glpiservice
licence
GPL-3.0-or-later
Service page: health and why, subscribed entities, member CIs, and open tickets with the route each tookService page: health and why, subscribed entities, member CIs, and open tickets with the route each tookView full size
Service page: health and why, subscribed entities, member CIs, and open tickets with the route each took

What it does

  • A BusinessService itemtype with owners, criticality and subscriptions
  • Members stored in GLPI’s own impact graph, not a copy of it
  • Health derived and cached, with the reasoning shown beside it
  • Which collector last spoke about an asset — core cannot say

Business services over the CMDB, and the hygiene work that keeps the CMDB worth building them on. Answers what is broken for a given entity, and where the contents of the CMDB came from.

7 more screens

Members tab: core's item picker, the member list, and the plugin's log of what it changed in the graphMembers tab: core's item picker, the member list, and the plugin's log of what it changed in the graphView full size
Members tab: core's item picker, the member list, and the plugin's log of what it changed in the graph
The affected-service strip offering one suggested service with accept and dismissThe affected-service strip offering one suggested service with accept and dismissView full size
The affected-service strip offering one suggested service with accept and dismiss
Census: counts per source across the estate, the caveats printed on the page, per-entity breakdownCensus: counts per source across the estate, the caveats printed on the page, per-entity breakdownView full size
Census: counts per source across the estate, the caveats printed on the page, per-entity breakdown
Two records of one machine side by side, with the identity fields and a decision to recordTwo records of one machine side by side, with the identity fields and a decision to recordView full size
Two records of one machine side by side, with the identity fields and a decision to record
One machine's drift after a patch window: two upgrades as single changed rows, one package added, one removedOne machine's drift after a patch window: two upgrades as single changed rows, one package added, one removedView full size
One machine's drift after a patch window: two upgrades as single changed rows, one package added, one removed
Settings page: status card, then one card and one Save per concernSettings page: status card, then one card and one Save per concernView full size
Settings page: status card, then one card and one Save per concern
The services people actually depend on, mapped over your CMDB — and a record of where everything in it came from.View full size
The services people actually depend on, mapped over your CMDB — and a record of where everything in it came from.

More in service management

Change

0.1.0

Change enablement built on GLPI’s own changes: a risk score, a shared calendar, freeze windows, collision warnings and a recorded outcome.

KEDB

0.1.0

A known-error database that surfaces the workaround mid-ticket, and turns recurring incidents into problem candidates a human decides on.

SOP

0.2.0

Interactive procedures that find the ticket, ask only the questions that apply, and record the answers as data.