[Feature][Plugin] Add a GLPI data source plugin
维护者通常 2 天内回复
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 38/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go
调研方向
The issue specifies a GLPI REST API plugin, entity scopes, ticket collection, optional ticket data, and MySQL and PostgreSQL dashboards, but names no source files or tests. Start by reading the repository’s existing data source plugin implementations and their tests to find the plugin entry points and conventions. Done means collecting tickets for a GLPI entity with the described mappings and options, plus the config UI and dashboards.
由索引模型根据 Issue 内容生成。
描述
Search before asking
- I had searched in the issues and found no similar feature requirement.
Use case
As an IT or engineering lead using GLPI, I want DevLake to collect tickets so I can see throughput and lead time alongside the rest of our delivery data. DevLake has no GLPI data source.
Description
Add a GLPI plugin for the GLPI REST API (apirest.php). A scope is one GLPI entity. Child entities are separate scopes.
Connection:
- Endpoint: the GLPI base URL, for example https://glpi.example.com
- Application token, from Setup → General → API
- User token, from My settings → Remote access keys
- Timezone, required, matching the GLPI server timezone. GLPI stores local times, and the plugin converts them to UTC
The plugin opens a session with App-Token and Authorization: user_token, then sends App-Token and Session-Token on later calls.
Domain mapping uses the ticket domain. Each entity becomes a board of type ITSM.
Tickets are always collected:
- Incident → INCIDENT, Request → TASK, any other type → TASK
- New → TODO
- Processing (assigned), Processing (planned), and Pending → IN_PROGRESS
- Solved and Closed → DONE
- Any other status → OTHER
- Priority, urgency, and impact use GLPI’s scale: Very Low, Low, Medium, High, Very High, Major
- The ITIL category is the issue component and an issue label
- The requester is the issue creator
- Due date is GLPI’s time to resolve
- Lead time comes from GLPI’s solve delay
- The issue URL points at front/ticket.form.php
Time range:
- A full sync lists tickets by opening date, newest first, and stops at the project time
- An incremental sync lists tickets by last modification, newest first, and stops at the previous watermark
Optional ticket data, chosen per scope. Assignees are on by default. The others are off:
- Assignees: assigned users and groups on the issue, and as issue assignees
- Follow-ups: public ITIL follow-ups as issue comments. Private follow-ups are skipped
- Tasks: ticket tasks with a recorded duration as issue worklogs
- Change logs: ticket history as issue changelogs
- Solutions: the latest solution text is appended to the issue description
- Ticket links: linked, duplicate, parent, and child links as issue relationships. A parent link also sets the parent issue
Referenced users and groups are stored as accounts. This is not a full user or group directory sync.
Plugin fields stay on the tool ticket as JSON. They are not written to the domain custom-field tables.
Config UI: beta plugin, connection form, entity scope picker, and the optional-collection checkboxes. Collected entity: TICKET.
Dashboards: MySQL (glpi-dashboard) and PostgreSQL (glpi-dashboard-pg). They show issue throughput, delivery rate, status distribution, and lead time.
This version collects tickets for a GLPI entity. It does not collect assets, computers, changes, problems, projects, or the knowledge base.
Related issues
No response
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
- 主要语言
- Go
- 星标
- 3.2k
- 派生
- 832
- 平均合并
- 2 天 6 小时
- 30 天内合并 PR
- 62
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apache/devlake 的其他 Issue
-
type/bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 60/100
维护者通常 2 天内回复
-
[Bug][claude_code] Incremental collection stops after the first run可能已有人在做 @clementsen 于 1 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 32/100
维护者通常 2 天内回复
-
type/bug
难度 3/5 半天 新手友好度 73/100
维护者通常 2 天内回复
-
[Refactor][Build] Build the core and all plugins into a single binary by default可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭component/plugins type/refactor
难度 5/5 一周以上 新手友好度 25/100
维护者通常 2 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
caddyserver/caddy#8314 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 72/100
hashicorp/golang-lru#245 ·
-
graphite: empty metric registry logs nil as an error and still dials可能已有人在做 @helmipradita 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
prometheus/client_golang#2203 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
spotify/flink-on-k8s-operator#1075 ·