Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Feature][Plugin] Add Grafana IRM Integration

未关闭
#9,065 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
go, grafana

调研方向

先查看链接的 Grafana IRM Incident API 和 OnCall API 文档,然后将其中可用的实体与 DevLake 现有的数据源插件模式进行比较。当维护者就支持的 API 和实体、收集范围以及同步策略达成一致后,该 issue 就可以继续推进。

由索引模型根据 Issue 内容生成。

描述

type/feature-request
Search before asking
  • I had searched in the issues and found no similar feature requirement.
Use case

Teams using Grafana Cloud IRM should be able to ingest its data into Apache DevLake and analyze it alongside data from other DevOps tools.

For example, incidents managed in Grafana IRM could be correlated with deployment data and used to calculate DORA metrics such as:

  • Change Failure Rate
  • Failed Deployment Recovery Time / MTTR
Description

I propose adding a grafana_irm data source plugin to support Grafana Cloud IRM.

Grafana IRM provides multiple capabilities, including Incident and OnCall, with APIs for programmatic access:

For example, Grafana IRM Incident data could be mapped to DevLake's domain models as follows:

  • Grafana IRM Incident → DevLake Issue (type = INCIDENT)
  • Incident status → Issue status / original status
  • Incident severity → Issue severity / priority
  • Incident declared time → Issue created date
  • Incident resolved time → Issue resolution date
  • Incident roles/members → Issue assignees, where applicable

This could allow Grafana IRM incidents to be correlated with deployment data through DevLake's existing DORA incident-to-deployment correlation.

Before proceeding with the implementation, I would like to confirm whether this overall direction is appropriate, particularly regarding:

  • which Grafana IRM APIs and entities should be supported
  • the scope of data to be collected
  • the synchronization strategy
Related issues

No related issue found.

Are you willing to submit a PR?
  • Yes I am willing to submit a PR!
Code of Conduct
主要语言
Go
星标
3.1k
派生
812
平均合并
1 天 23 小时
30 天内合并 PR
51

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/devlake 的其他 Issue

查看 apache/devlake 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。