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

[Template contribution]: prometheus-security-check

未关闭
  • 哪里不对？
#109 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 6 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
56/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
github, javascript
领域
devops, observability

调研方向

Read CONTRIBUTING.md § Authoring a template and inspect the demo YAML at next-gen-o11y/workflows/prometheus-security-check.kibana.yaml. Create the Serverless-safe library template at library/workflows/<slug>/<slug>.yaml, following the listed install-form bindings and metadata. Run npm run build:catalog, then install and run it on Serverless Observability with Prometheus or OTLP metrics; done means the dashboard upserts, the agent returns OPEN_CASE or NO_CASE, and validation reports no errors.

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

描述

What does your template do?

Security-aware SRE scan on Prometheus / OTLP metrics: ES|QL for auth failures (401/403), login-failure deltas, and 5xx hotspots → upsert Auto: Prometheus security signals dashboard → Agent Builder assesses risk and opens an Observability Case only when warranted. Optional Security MCP enrichment when configured on the agent.

Demo workflow name: prometheus-security-check
Proposed library slug: prometheus-security-check (or prometheus-auto-security-check)

Install form variables (must be present)
Field inputType required default Used as
agent-id text yes elastic-ai-agent ai.agent agent-id
metrics-index esIndex yes metrics-generic.prometheus-* consts.metrics_index for all ES|QL
security-mcp-hint text no `` (empty) consts.security_mcp_hint — optional URL/hint for Security Agent Builder MCP; omit from agent prompt when empty

Not in PR https://github.com/elastic/workflows/pull/94 yet — this issue requests a new library template.

Template YAML or pull request

Source: https://github.com/elastic/next-gen-o11y/blob/main/workflows/prometheus-security-check.kibana.yaml

Acceptance: install on Serverless Observability with only the form fields → dashboard upserts → agent step completes with OPEN_CASE / NO_CASE verdict; no unknownVariableType / validation errors (single agent step; no chained conversation_id).

Library format (required — Serverless-safe)

Follow CONTRIBUTING.md § Authoring a template:

  • Path: library/workflows/<slug>/<slug>.yaml
  • template-metadata with slug, version, availability: ">=9.5.0", name, description, solutions: [observability], categories
  • No hardcoded project URLs / space IDs / API keys
  • Promote environment-specific values to install.form and bind via bare __install__.<field> → consts: (never wrap __install__ in {{ }})
  • ai.agent steps: agent-id: __install__.agent-id (default elastic-ai-agent)
  • ES|QL / Streams: FROM {{ consts.metrics_index }} / stream name from consts
  • Validate: npm run build:catalog must pass
  • Install + run once on an Elastic Cloud Serverless Observability project with Prom/OTLP metrics — zero editor validation errors
Related
主要语言
JavaScript
星标
59
派生
38
平均合并
5 天 16 小时
30 天内合并 PR
14

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

elastic/workflows 的其他 Issue

查看 elastic/workflows 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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