Insights
Practical guides from the inside.
How to run GLPI, Zabbix and Metabase well: upgrades, alerting, reporting and the details that decide whether a platform is trusted. Written for the people who run them.
Articles
Guides for the people who run the platforms.
One GLPI, many SLA policies
GLPI SLA study: four service level policies and 1,701 tickets in one GLPI. Where results match the contract, where they differ, and how to configure it.
29 Oct 2026 · 12 min readWhere GLPI reaches its limits
We loaded one GLPI server with up to 500,000 tickets and more technicians than it could serve: where the limits arrive, what fails quietly, and how to size ahead.
26 Oct 2026 · 20 min readWho tells the service desk first?
How fast does an outage reach GLPI? The same ERP failure timed with no monitoring (22:37), Zabbix (1:02) and Google Cloud (3:38), and the tickets each path left.
17 Oct 2026 · 9 min readOne outage, forty tickets, one response
A core switch fails and 40 tickets arrive in 14 minutes. How we run it as one major incident in GLPI, solve once for every user and fix the cause.
13 Oct 2026 · 8 min readCutting alert noise in Zabbix: six settings that matter
When people stop reading alerts, monitoring has stopped working. Six Zabbix features that turn a flood of notifications into a short list of real problems.
6 Oct 2026 · 6 min readPlanning a GLPI upgrade without surprises
Most GLPI upgrades that go wrong were in trouble before the first command ran. A checklist for planning and rehearsing a GLPI upgrade, even on customised code.
6 Oct 2026 · 6 min readReporting on GLPI with Metabase: getting the numbers right
GLPI's database is built to run a service desk, not to report on one. Five things to get right before a Metabase dashboard on GLPI data can be trusted.
6 Oct 2026 · 6 min read
Upstream work
We don't just deploy and run GLPI. We help make it better.
Most active community contributor to GLPI
What we find in the field isn't patched quietly for one installation and forgotten. It goes back to the community, so every organisation that runs GLPI benefits.
Security findings are handled with particular care. We report them privately to the GLPI maintainers and work with them on a fix, following the project's disclosure guidelines, before anything is made public.
Every bug closed and every vulnerability fixed makes GLPI safer for everyone who depends on it. A rising tide lifts all boats.
- Shared, not kept
- Disclosed responsibly
- Safer for everyone
October 2026
- Apply form conditions on actor questions filled with a default value#25695
- Do not give the same index to concurrent answers of a form#26029
- Protect the login and the directory link of users against unallowed updates#25775
- Fix dropdown condition of ITIL objects massive update#26042
- Link the items selected in Item questions to the created ticket#25919
- Only copy ticket document links to merged tickets#25920
- Only show the permissions of a knowledge base article to the users who can edit it#25787
- Do not reopen a solved ticket when editing one of its tasks#25691
- Do not load items of another definition in custom assets and dropdowns#25818
- Fix dashboard init error when the dashboard select has no option#25984
- Do not poll browser notifications for anonymous users#25928
- Do not update the TCO of items without a ticket_tco field#25994
- Use the same opening date for all tickets of a recurrent ticket per item#25989
- Fix undefined is_request warning when the ticket has no category#25983
- Check the rights before removing an item link from an ITIL object#25967
- Check the read right on the item before creating a planning recall#25968
- Show cable rights in the assets tab of profiles#25985
- Fix the session list with client credentials tokens#25921
- Do not notify a removed actor when assigning a replacement#25694
- Do not propagate follow-ups through the ticket merge graph for non-tickets#25510
- Resolve the webhook parent item of fixed-parent children#25690
- Show licenses without a linked software in the financial report#25696
- Use root_doc in the Reports dropdown empty option#25692
- Check item rights in reservation massive actions#25710
- Remove TinyMCE blocker div when it contains a non-breaking space#25703
- Check that the ticket is accessible before updating it from the ticket form#25765
- Check rights before linking a knowledge base article to a category#25761
- Apply visibility criteria in the connect dropdown#25740
- Check that a rule is of the current type before updating or purging it#25767
- Check rights in dropdown and reminder translation forms#25759
- Only reorder the helpdesk tiles of the given entity or profile#25719
- Check the update right on reminders and RSS feeds for all visibility targets#25698
- Hide deleted child licenses from the parent license tab#25704
- Check system logs right in the log viewer ajax endpoint#25748
- Check the re-authentication when updating an LDAP directory#25769
- Check parent read right when rendering a validation template#25700
- Ignore unexpected group conditions in the actors dropdown#25697
September 2026
- Do not use a refused solution in ITIL resolution notifications#25508
- Match addresses against the network address when linking them to a network#25566
- Use reminder translations in the planning#25463
- Enforce HL API sub-resource scope independently of the user filter#25552
- Do not treat a form answer of 0 as empty#25553
- Encode itemtype in generated action links for custom assets#25548
- Import LDAP user location in the assigned entity#25485
- Round the top-left corner of right-aligned timeline bubbles#25529
- Create saved search notification in the saved search entity#25498
- Encode itemtype in templatable item menu and redirect URLs#25512
- Form fields answered with 0 are wrongly treated as empty#25520
- Add entity id to entity map points#25501
- Avoid a warning when listing linked items without a name field#25518
- High-level API is-empty filter wrongly matches a numeric 0#25521
- Fix TTR OLA type migrated with the wrong value#25484
- Skip inline image parsing when the mail body has no document link#25502
- Send queued notifications in a stable order#25505
- Do not start overlapping ajax notification polls#25499
- Fix API search warning on additional fields with TABLE prefix#25462
Have a question about your GLPI?
Something not behaving as you expect, or a feature you are not sure how to use? Tell us what you are seeing and our engineers will help you make sense of it.