ci: bump promci to v0.8.2 and push to GHCR (#309)
- Bump promci composite actions to v0.8.2 (pinned by SHA)
- Remove standalone actions/checkout steps before promci build/publish steps (promci v0.8.2 performs the checkout itself)
- Add packages: write permission to publish_main and publish_release jobs
- Add ghcr_io_password: ${{ github.token }} to both publish jobs
Signed-off-by: Julien Pivotto 291750+roidelapluie@users.noreply.github.com
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
Memcached Exporter for Prometheus
A memcached exporter for Prometheus.
Building
The memcached exporter exports metrics from a memcached server for consumption by Prometheus. The server is specified as
--memcached.addressflag to the program (default islocalhost:11211).By default the memcache_exporter serves on port
0.0.0.0:9150at/metrics:Alternatively a Dockerfile is supplied:
Collectors
The exporter collects a number of statistics from the server.
For supported metrics see the metrics documentation.
TLS and basic authentication
The Memcached Exporter supports TLS and basic authentication.
To use TLS and/or basic authentication, you need to pass a configuration file using the
--web.config.fileparameter. The format of the file is described in the exporter-toolkit repository.To use TLS for connections to memcached, use the
--memcached.tls.*flags. Seememcached_exporter --helpfor details.Multi-target
The exporter also supports the multi-target pattern on the
/scrapeendpoint. Example:An example configuration using prometheus-elasticache-sd:
If you are running solely for
multi-targetstart the exporter with--memcached.address=""to avoid attempting to connect to a non existing memcached host, example: