[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-480":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":9,"pushedAt":9,"updatedAt":32,"readmeContent":33,"aiSummary":34,"trendingCount":15,"starSnapshotCount":15,"syncStatus":35,"lastSyncTime":36,"discoverSource":37},480,"prometheus","prometheus\u002Fprometheus","The Prometheus monitoring system and time series database.","https:\u002F\u002Fprometheus.io\u002F",null,"Go",64436,10494,1127,518,0,14,164,479,74,45,"Apache License 2.0",false,"main",true,[26,27,28,29,30,5,31],"alerting","graphing","hacktoberfest","metrics","monitoring","time-series","2026-06-12 02:00:14","\u003Ch1 align=\"center\" style=\"border-bottom: none\">\n    \u003Ca href=\"https:\u002F\u002Fprometheus.io\" target=\"_blank\">\u003Cimg alt=\"Prometheus\" src=\"\u002Fdocumentation\u002Fimages\u002Fprometheus-logo.svg\">\u003C\u002Fa>\u003Cbr>Prometheus\n\u003C\u002Fh1>\n\n\u003Cp align=\"center\">Visit \u003Ca href=\"https:\u002F\u002Fprometheus.io\" target=\"_blank\">prometheus.io\u003C\u002Fa> for the full documentation,\nexamples and guides.\u003C\u002Fp>\n\n\u003Cdiv align=\"center\">\n\n[![CI](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fprometheus\u002Factions\u002Fworkflows\u002Fci.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fprometheus\u002Factions\u002Fworkflows\u002Fci.yml)\n[![Docker Repository on Quay](https:\u002F\u002Fquay.io\u002Frepository\u002Fprometheus\u002Fprometheus\u002Fstatus)][quay]\n[![Docker Pulls](https:\u002F\u002Fimg.shields.io\u002Fdocker\u002Fpulls\u002Fprom\u002Fprometheus.svg?maxAge=604800)][hub]\n[![Go Report Card](https:\u002F\u002Fgoreportcard.com\u002Fbadge\u002Fgithub.com\u002Fprometheus\u002Fprometheus)](https:\u002F\u002Fgoreportcard.com\u002Freport\u002Fgithub.com\u002Fprometheus\u002Fprometheus)\n[![CII Best Practices](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F486\u002Fbadge)](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F486)\n[![govulncheck](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fprometheus\u002Factions\u002Fworkflows\u002Fgovulncheck.yml\u002Fbadge.svg?event=schedule)](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fprometheus\u002Factions\u002Fworkflows\u002Fgovulncheck.yml)\n[![OpenSSF Scorecard](https:\u002F\u002Fapi.securityscorecards.dev\u002Fprojects\u002Fgithub.com\u002Fprometheus\u002Fprometheus\u002Fbadge)](https:\u002F\u002Fsecurityscorecards.dev\u002Fviewer\u002F?uri=github.com\u002Fprometheus\u002Fprometheus)\n[![CLOMonitor](https:\u002F\u002Fimg.shields.io\u002Fendpoint?url=https:\u002F\u002Fclomonitor.io\u002Fapi\u002Fprojects\u002Fcncf\u002Fprometheus\u002Fbadge)](https:\u002F\u002Fclomonitor.io\u002Fprojects\u002Fcncf\u002Fprometheus)\n[![Fuzzing Status](https:\u002F\u002Foss-fuzz-build-logs.storage.googleapis.com\u002Fbadges\u002Fprometheus.svg)](https:\u002F\u002Fbugs.chromium.org\u002Fp\u002Foss-fuzz\u002Fissues\u002Flist?sort=-opened&can=1&q=proj:prometheus)\n\n\u003C\u002Fdiv>\n\nPrometheus, a [Cloud Native Computing Foundation](https:\u002F\u002Fcncf.io\u002F) project, is a systems and service monitoring system. It collects metrics\nfrom configured targets at given intervals, evaluates rule expressions,\ndisplays the results, and can trigger alerts when specified conditions are observed.\n\nThe features that distinguish Prometheus from other metrics and monitoring systems are:\n\n* A **multi-dimensional** data model (time series defined by metric name and set of key\u002Fvalue dimensions)\n* PromQL, a **powerful and flexible query language** to leverage this dimensionality\n* No dependency on distributed storage; **single server nodes are autonomous**\n* An HTTP **pull model** for time series collection\n* **Pushing time series** is supported via an intermediary gateway for batch jobs\n* Targets are discovered via **service discovery** or **static configuration**\n* Multiple modes of **graphing and dashboarding support**\n* Support for hierarchical and horizontal **federation**\n\n## Architecture overview\n\n![Architecture overview](documentation\u002Fimages\u002Farchitecture.svg)\n\n## Install\n\nThere are various ways to install Prometheus.\n\n### Precompiled binaries\n\nPrecompiled binaries for released versions are available in the\n[*download* section](https:\u002F\u002Fprometheus.io\u002Fdownload\u002F)\non [prometheus.io](https:\u002F\u002Fprometheus.io). Using the latest production release binary\nis the recommended way to install Prometheus.\nSee the [Installing](https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fintroduction\u002Finstall\u002F)\nchapter in the documentation for all the details.\n\n### Docker images\n\nDocker images are available on [Quay.io](https:\u002F\u002Fquay.io\u002Frepository\u002Fprometheus\u002Fprometheus) or [Docker Hub](https:\u002F\u002Fhub.docker.com\u002Fr\u002Fprom\u002Fprometheus\u002F).\n\nYou can launch a Prometheus container for trying it out with\n\n```bash\ndocker run --name prometheus -d -p 127.0.0.1:9090:9090 prom\u002Fprometheus\n```\n\nPrometheus will now be reachable at \u003Chttp:\u002F\u002Flocalhost:9090\u002F>.\n\n### Building from source\n\nTo build Prometheus from source code, you need:\n\n* Go: Version specified in [go.mod](.\u002Fgo.mod) or greater.\n* NodeJS: Version specified in [.nvmrc](.\u002Fweb\u002Fui\u002F.nvmrc) or greater.\n* npm: Version 10 or greater (check with `npm --version` and [here](https:\u002F\u002Fwww.npmjs.com\u002F)).\n\nStart by cloning the repository:\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fprometheus.git\ncd prometheus\n```\n\nYou can use the `go` tool to build and install the `prometheus`\nand `promtool` binaries into your `GOPATH`:\n\n```bash\ngo install github.com\u002Fprometheus\u002Fprometheus\u002Fcmd\u002F...\nprometheus --config.file=your_config.yml\n```\n\n*However*, when using `go install` to build Prometheus, Prometheus will expect to be able to\nread its web assets from local filesystem directories under `web\u002Fui\u002Fstatic`. In order for\nthese assets to be found, you will have to run Prometheus from the root of the cloned\nrepository. Note also that this directory does not include the React UI unless it has been\nbuilt explicitly using `make assets` or `make build`.\n\nAn example of the above configuration file can be found [here.](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fprometheus\u002Fblob\u002Fmain\u002Fdocumentation\u002Fexamples\u002Fprometheus.yml)\n\nYou can also build using `make build`, which will compile in the web assets so that\nPrometheus can be run from anywhere:\n\n```bash\nmake build\n.\u002Fprometheus --config.file=your_config.yml\n```\n\nThe Makefile provides several targets:\n\n* *build*: build the `prometheus` and `promtool` binaries (includes building and compiling in web assets)\n* *test*: run the tests\n* *test-short*: run the short tests\n* *format*: format the source code\n* *vet*: check the source code for common errors\n* *assets*: build the React UI\n\n### Service discovery plugins\n\nPrometheus is bundled with many service discovery plugins. You can customize\nwhich service discoveries are included in your build using Go build tags.\n\nTo exclude service discoveries when building with `make build`, add the desired\ntags to the `.promu.yml` file under `build.tags.all`:\n\n```yaml\nbuild:\n    tags:\n        all:\n            - netgo\n            - builtinassets\n            - remove_all_sd           # Exclude all optional SDs\n            - enable_kubernetes_sd    # Re-enable only kubernetes\n```\n\nThen run `make build` as usual. Alternatively, when using `go build` directly:\n\n```bash\ngo build -tags \"remove_all_sd,enable_kubernetes_sd\" .\u002Fcmd\u002Fprometheus\n```\n\nAvailable build tags:\n* `remove_all_sd` - Exclude all optional service discoveries (keeps file_sd, static_sd, and http_sd)\n* `enable_\u003Cname>_sd` - Re-enable a specific SD when using `remove_all_sd`\n\nIf you add out-of-tree plugins, which we do not endorse at the moment,\nadditional steps might be needed to adjust the `go.mod` and `go.sum` files. As\nalways, be extra careful when loading third party code.\n\n### Building the Docker image\n\nYou can build a docker image locally with the following commands:\n\n```bash\nmake promu\npromu crossbuild -p linux\u002Famd64\nmake npm_licenses\nmake common-docker-amd64\n```\n\nThe `make docker` target is intended only for use in our CI system and will not\nproduce a fully working image when run locally.\n\n## Using Prometheus as a Go Library\n\nWithin the Prometheus project, repositories such as [prometheus\u002Fcommon](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fcommon) and\n[prometheus\u002Fclient-golang](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fclient-golang) are designed as re-usable libraries.\n\nThe [prometheus\u002Fprometheus](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fprometheus) repository builds a stand-alone program and is not\ndesigned for use as a library. We are aware that people do use parts as such,\nand we do not put any deliberate inconvenience in the way, but we want you to be\naware that no care has been taken to make it work well as a library. For instance,\nyou may encounter errors that only surface when used as a library.\n\n### Remote Write\n\nWe are publishing our Remote Write protobuf independently at\n[buf.build](https:\u002F\u002Fbuf.build\u002Fprometheus\u002Fprometheus\u002Fassets).\n\nYou can use that as a library:\n\n```shell\ngo get buf.build\u002Fgen\u002Fgo\u002Fprometheus\u002Fprometheus\u002Fprotocolbuffers\u002Fgo@latest\n```\n\nThis is experimental.\n\n### Prometheus code base\n\nIn order to comply with [go mod](https:\u002F\u002Fgo.dev\u002Fref\u002Fmod#versions) rules,\nPrometheus release number do not exactly match Go module releases.\n\nFor the\nPrometheus v3.y.z releases, we are publishing equivalent v0.3y.z tags. The y in v0.3y.z is always padded to two digits, with a leading zero if needed.\n\nTherefore, a user that would want to use Prometheus v3.0.0 as a library could do:\n\n```shell\ngo get github.com\u002Fprometheus\u002Fprometheus@v0.300.0\n```\n\nFor the\nPrometheus v2.y.z releases, we published the equivalent v0.y.z tags.\n\nTherefore, a user that would want to use Prometheus v2.35.0 as a library could do:\n\n```shell\ngo get github.com\u002Fprometheus\u002Fprometheus@v0.35.0\n```\n\nThis solution makes it clear that we might break our internal Go APIs between\nminor user-facing releases, as [breaking changes are allowed in major version\nzero](https:\u002F\u002Fsemver.org\u002F#spec-item-4).\n\n## React UI Development\n\nFor more information on building, running, and developing on the React-based UI, see the React app's [README.md](web\u002Fui\u002FREADME.md).\n\n## More information\n\n* Godoc documentation is available via [pkg.go.dev](https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fprometheus\u002Fprometheus). Due to peculiarities of Go Modules, v3.y.z will be displayed as v0.3y.z (the y in v0.3y.z is always padded to two digits, with a leading zero if needed), while v2.y.z will be displayed as v0.y.z.\n* See the [Community page](https:\u002F\u002Fprometheus.io\u002Fcommunity) for how to reach the Prometheus developers and users on various communication channels.\n\n## Contributing\n\nRefer to [CONTRIBUTING.md](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fprometheus\u002Fblob\u002Fmain\u002FCONTRIBUTING.md)\n\n## License\n\nApache License 2.0, see [LICENSE](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fprometheus\u002Fblob\u002Fmain\u002FLICENSE).\n\n[hub]: https:\u002F\u002Fhub.docker.com\u002Fr\u002Fprom\u002Fprometheus\u002F\n[quay]: https:\u002F\u002Fquay.io\u002Frepository\u002Fprometheus\u002Fprometheus\n","Prometheus 是一个系统和服务监控工具及时间序列数据库。它能够从配置的目标中以设定的时间间隔收集指标，评估规则表达式，并展示结果，同时在检测到特定条件时触发警报。其核心功能包括一个多维度的数据模型，支持通过PromQL进行灵活查询；采用HTTP拉取模式来收集时间序列数据，同时也支持通过中间网关推送时间序列数据给批量作业；具备服务发现或静态配置目标的能力；提供多种图形化和仪表盘支持方式；以及支持水平和垂直联邦。Prometheus适用于需要对分布式系统的性能、健康状况进行持续监控的场景，如云原生环境下的微服务架构等。",2,"2026-06-11 02:36:20","top_all"]