日志类:

-log.level 可选值 [debug, info, warn, error, fatal]  例:-log.level "info"

-log.format  可选输出到syslog或者控制台  例:-log.format "logger:syslog?appname=prom&local=7"

查询类:

-query.max-concurrency 20  最大支持的并发查询量

   -query.staleness-delta 5m0s    Staleness delta allowance during expression evaluations.

-query.timeout 2m0s   查询超时时间,2分钟。超过自动被kill掉。

存储类:

  -storage.local.checkpoint-dirty-series-limit 5000   崩溃恢复时候,只恢复5000个时序数据,这样减少了prometheus的恢复时间。如果是SSD盘,可以适当增大这个值。

  -storage.local.checkpoint-interval 5m0s   5分钟执行一次落盘,将in-memory metrics and chunks持久化到磁盘。

  -storage.local.chunk-encoding-version 1     chunks的编码格式 ,默认是1

  -storage.local.engine "persisted"    开启持久化

  -storage.local.index-cache-size.label-name-to-label-values 10485760     存放prometheus里面定义的 label名称的 index cache大小,默认10MB

  -storage.local.path "/bdata/data/nowdb2"

  -storage.local.retention 8760h0m0s    保存1年的数据

  -storage.local.series-file-shrink-ratio 0.3    表示 30%的chunks被移除的时候才触发rewrite

  -storage.local.num-fingerprint-mutexes 4096 当prometheus server端在进行checkpoint操作或者处理开销较大的查询的时候,采集指标的操作会有短暂的停顿,这是因为prometheus给时间序列分配的mutexes可能不够用,可以通过这个指标来增大预分配的mutexes,有时候可以设置到上万个。

  -storage.local.series-sync-strategy "adaptive"

  -storage.local.target-heap-size 2147483648     # prometheus独占的内存空间,默认2GB的内存空间,建议不要超过3GB

Web配置:

  -web.listen-address ":9090"

  -web.max-connections 512

  -web.read-timeout 30s

目前在用的启动参数:

nohup ./prometheus 
-log.level "info"
-log.format "logger:syslog?appname=prom&local=7" info
-storage.local.checkpoint-dirty-series-limit 5000
-storage.local.checkpoint-interval 5m0s
-storage.local.chunk-encoding-version 1
-storage.local.engine "persisted"
-storage.local.index-cache-size.label-name-to-label-values 10485760
-storage.local.path "/bdata/data/nowdb2" -storage.local.retention 8760h0m0s
-storage.local.series-file-shrink-ratio 0.3
-storage.local.series-sync-strategy "adaptive"
-storage.local.target-heap-size 2147483648 &

关闭进程:

kill -SIGTERM $(pid of prometheus)

补充: ./prometheus -h的结果:

usage: prometheus [<args>]

-version false

Print version information.

-config.file "prometheus.yml"

Prometheus configuration file name.

ALERTMANAGER

-alertmanager.notification-queue-capacity 10000

The capacity of the queue for pending alert manager notifications.

-alertmanager.timeout 10s

Alert manager HTTP API timeout.

-alertmanager.url

Comma-separated list of Alertmanager URLs to send notifications to.

LOG

-log.format "\"logger:stderr\""

Set the log target and format. Example:

"logger:syslog?appname=bob&local=7" or "logger:stdout?json=true"

-log.level "\"info\""

Only log messages with the given severity or above. Valid levels:

[debug, info, warn, error, fatal]

 QUERY

-query.max-concurrency 20    最大支持的并发查询量

Maximum number of queries executed concurrently.

-query.staleness-delta 5m0s

Staleness delta allowance during expression evaluations.

-query.timeout 2m0s   查询超时时间,2分钟。超过自动被kill掉。

Maximum time a query may take before being aborted.

STORAGE 

-storage.local.checkpoint-dirty-series-limit 5000   崩溃恢复时候,只恢复5000个时序数据,这样减少了prometheus的恢复时间。如果是SSD盘,可以适当增大这个值。

If approx. that many time series are in a state that would require

a recovery operation after a crash, a checkpoint is triggered, even if

the checkpoint interval hasn't passed yet. A recovery operation requires

a disk seek. The default limit intends to keep the recovery time below

1min even on spinning disks. With SSD, recovery is much faster, so you

might want to increase this value in that case to avoid overly frequent

checkpoints. Also note that a checkpoint is never triggered before at

least as much time has passed as the last checkpoint took.

-storage.local.checkpoint-interval 5m0s   5分钟执行一次落盘,将in-memory metrics and chunks持久化到磁盘。

The time to wait between checkpoints of in-memory metrics and

chunks not yet persisted to series files. Note that a checkpoint is never

triggered before at least as much time has passed as the last checkpoint

took.

-storage.local.chunk-encoding-version 1  chunks的编码格式 ,默认是1

Which chunk encoding version to use for newly created chunks.

Currently supported is 0 (delta encoding), 1 (double-delta encoding), and

2 (double-delta encoding with variable bit-width).

-storage.local.dirty=false   是否强制开启crash recovery功能。默认 -storage.local.dirty=false的。

如果您怀疑数据库中的损坏引起的问题,可设置启动的时候 -storage.local.dirty=true强制执行crash recovery

If set, the local storage layer will perform crash recovery even if

the last shutdown appears to be clean.

-storage.local.engine "persisted"

Local storage engine. Supported values are: 'persisted' (full local

storage with on-disk persistence) and 'none' (no local storage).

-storage.local.index-cache-size.fingerprint-to-metric 10485760

The size in bytes for the fingerprint to metric index cache.

-storage.local.index-cache-size.fingerprint-to-timerange 5242880

The size in bytes for the metric time range index cache.

上面2个参数的作用: Increase the size if you have a large number of archived time series, i.e. series that have not received samples in a while but are still not old enough to be purged completely.

-storage.local.index-cache-size.label-name-to-label-values 10485760     存放prometheus里面定义的 label名称的 index cache大小,默认10MB

The size in bytes for the label name to label values index cache.

-storage.local.index-cache-size.label-pair-to-fingerprints 20971520  #

The size in bytes for the label pair to fingerprints index cache. Increase the size if a large number of time series share the same label pair or name.

-storage.local.max-chunks-to-persist 0   废弃的参数

Deprecated. This flag has no effect anymore.

-storage.local.memory-chunks 0  废弃的参数 设定prometheus内存中保留的chunks的最大个数

Deprecated. If set, -storage.local.target-heap-size will be set to

this value times 3072.

-storage.local.num-fingerprint-mutexes 4096

The number of mutexes used for fingerprint locking.

当prometheus server端在进行checkpoint操作或者处理开销较大的查询的时候,采集指标的操作会有短暂的停顿,这是因为prometheus给时间序列分配的mutexes可能不够用,可以通过这个指标来增大预分配的mutexes,有时候可以设置到上万个。

-storage.local.path "data"

Base path for metrics storage.

-storage.local.pedantic-checks false   默认false 如果设置true,崩溃恢复时候会检查每一个序列文件

If set, a crash recovery will perform checks on each series file.

This might take a very long time.

-storage.local.retention 360h0m0s   历史数据存储多久,默认15天。

How long to retain samples in the local storage.

-storage.local.series-file-shrink-ratio 0.1

A series file is only truncated (to delete samples that have

exceeded the retention period) if it shrinks by at least the provided

ratio. This saves I/O operations while causing only a limited storage

space overhead. If 0 or smaller, truncation will be performed even for a

single dropped chunk, while 1 or larger will effectively prevent any

truncation.

用来控制序列文件rewrite的时机,默认是在10%的chunks被移除的时候进行rewrite,如果磁盘空间够大,不想频繁rewrite,可以提升该值,比如0.3,即30%的chunks被移除的时候才触发rewrite。

-storage.local.series-sync-strategy "adaptive"

When to sync series files after modification. Possible values:

'never', 'always', 'adaptive'. Sync'ing slows down storage performance

but reduces the risk of data loss in case of an OS crash. With the

'adaptive' strategy, series files are sync'd for as long as the storage

is not too much behind on chunk persistence.

控制写入数据之后,何时同步到磁盘,有'never', 'always', 'adaptive'. 同步操作可以降低因为操作系统崩溃带来数据丢失,但是会降低写入数据的性能。

默认为adaptive的策略,即不会写完数据就立刻同步磁盘,会利用操作系统的page cache来批量同步。

-storage.local.target-heap-size 2147483648     # prometheus独占的内存空间,默认2GB的内存空间,建议不要超过3GB

The metrics storage attempts to limit its own memory usage such

that the total heap size approaches this value. Note that this is not a

hard limit. Actual heap size might be temporarily or permanently higher

for a variety of reasons. The default value is a relatively safe setting

to not use more than 3 GiB physical memory.

-storage.remote.graphite-address

WARNING: THIS FLAG IS UNUSED! Built-in support for InfluxDB,

Graphite, and OpenTSDB has been removed. Use Prometheus's generic remote

write feature for building remote storage integrations. See

https://prometheus.io/docs/operating/configuration/#<remote_write>

-storage.remote.graphite-prefix

WARNING: THIS FLAG IS UNUSED! Built-in support for InfluxDB,

Graphite, and OpenTSDB has been removed. Use Prometheus's generic remote

write feature for building remote storage integrations. See

https://prometheus.io/docs/operating/configuration/#<remote_write>

-storage.remote.graphite-transport

WARNING: THIS FLAG IS UNUSED! Built-in support for InfluxDB,

Graphite, and OpenTSDB has been removed. Use Prometheus's generic remote

write feature for building remote storage integrations. See

https://prometheus.io/docs/operating/configuration/#<remote_write>

-storage.remote.influxdb-url

WARNING: THIS FLAG IS UNUSED! Built-in support for InfluxDB,

Graphite, and OpenTSDB has been removed. Use Prometheus's generic remote

write feature for building remote storage integrations. See

https://prometheus.io/docs/operating/configuration/#<remote_write>

-storage.remote.influxdb.database

WARNING: THIS FLAG IS UNUSED! Built-in support for InfluxDB,

Graphite, and OpenTSDB has been removed. Use Prometheus's generic remote

write feature for building remote storage integrations. See

https://prometheus.io/docs/operating/configuration/#<remote_write>

-storage.remote.influxdb.retention-policy

WARNING: THIS FLAG IS UNUSED! Built-in support for InfluxDB,

Graphite, and OpenTSDB has been removed. Use Prometheus's generic remote

write feature for building remote storage integrations. See

https://prometheus.io/docs/operating/configuration/#<remote_write>

-storage.remote.influxdb.username

WARNING: THIS FLAG IS UNUSED! Built-in support for InfluxDB,

Graphite, and OpenTSDB has been removed. Use Prometheus's generic remote

write feature for building remote storage integrations. See

https://prometheus.io/docs/operating/configuration/#<remote_write>

-storage.remote.opentsdb-url

WARNING: THIS FLAG IS UNUSED! Built-in support for InfluxDB,

Graphite, and OpenTSDB has been removed. Use Prometheus's generic remote

write feature for building remote storage integrations. See

https://prometheus.io/docs/operating/configuration/#<remote_write>

-storage.remote.timeout

WARNING: THIS FLAG IS UNUSED! Built-in support for InfluxDB,

Graphite, and OpenTSDB has been removed. Use Prometheus's generic remote

write feature for building remote storage integrations. See

https://prometheus.io/docs/operating/configuration/#<remote_write>

== WEB ==

-web.console.libraries "console_libraries"

Path to the console library directory.

-web.console.templates "consoles"

Path to the console template directory, available at /consoles.

-web.enable-remote-shutdown false

Enable remote service shutdown.

-web.external-url

The URL under which Prometheus is externally reachable (for

example, if Prometheus is served via a reverse proxy). Used for

generating relative and absolute links back to Prometheus itself. If the

URL has a path portion, it will be used to prefix all HTTP endpoints

served by Prometheus. If omitted, relevant URL components will be derived

automatically.

-web.listen-address ":9090"

Address to listen on for the web interface, API, and telemetry.

-web.max-connections 512

Maximum number of simultaneous connections.

-web.read-timeout 30s

Maximum duration before timing out read of the request, and closing

idle connections.

-web.route-prefix

Prefix for the internal routes of web endpoints. Defaults to path

of -web.external-url.

-web.telemetry-path "/metrics"

Path under which to expose metrics.

-web.user-assets

Path to static asset directory, available at /user.

Prometheus监控学习笔记之prometheus 版本1.7 常用启动参数的更多相关文章

  1. Prometheus监控学习笔记之Prometheus 2.x版本的常用变化

    最近用了prometheus 2.0 版本,感觉改变还是有点大,现将改变相关记录如下: 1.prometheus.yml文件配置修改后,要想重新加载,必须在启动的时候添加参数: --web.enabl ...

  2. Prometheus监控学习笔记之Prometheus存储

    0x00 概述 Prometheus之于kubernetes(监控领域),如kubernetes之于容器编排.随着heapster不再开发和维护以及influxdb 集群方案不再开源,heapster ...

  3. Prometheus监控学习笔记之Prometheus普罗米修斯监控入门

    0x00 概述 视频讲解通过链接网易云课堂·IT技术快速入门学院进入,更多关于Prometheus的文章. Prometheus是最近几年开始流行的一个新兴监控告警工具,特别是kubernetes的流 ...

  4. Prometheus监控学习笔记之Prometheus从1.x升级到2.x

    详细参考这篇文章 https://cloud.tencent.com/developer/article/1171434 prometheus 2.0于2017-11-08发布,主要是存储引擎进行了优 ...

  5. Prometheus监控学习笔记之Prometheus的Relabel,SD以及Federation功能

    0x00 k8s 的监控设计 k8s 默认以及推荐的监控体系是它自己的一套东西:Heapster + cAdvisor + Influxdb + Grafana,具体可以看 这里 . 包括 k8s 自 ...

  6. Prometheus监控学习笔记之prometheus的federation机制

    0x00 概述 有时候对于一个公司,k8s集群或是所谓的caas只是整个技术体系的一部分,往往这个时候监控系统不仅仅要k8s集群以及k8s中部署的应用,而且要监控传统部署的项目.也就是说整个监控系统不 ...

  7. Prometheus监控学习笔记之prometheus的远端存储

    0x00 概述 prometheus在容器云的领域实力毋庸置疑,越来越多的云原生组件直接提供prometheus的metrics接口,无需额外的exporter.所以采用prometheus作为整个集 ...

  8. Prometheus监控学习笔记之Prometheus不完全避坑指南

    0x00 概述 Prometheus 是一个开源监控系统,它本身已经成为了云原生中指标监控的事实标准,几乎所有 k8s 的核心组件以及其它云原生系统都以 Prometheus 的指标格式输出自己的运行 ...

  9. Prometheus监控学习笔记之Prometheus监控简介

    0x00 Prometheus容器监控解决方案 Prometheus(普罗米修斯)是一个开源系统监控和警报工具,最初是在SoundCloud建立的.它是一个独立的开放源码项目,并且独立于任何公司.不同 ...

随机推荐

  1. 个人项目wc(Java)

                                                      个人项目(Java) 一丶Github地址:https://github.com/SAH2019/S ...

  2. bat脚本弹出消息示例(msg命令详细解释)

    弹出消息的bat,其实就是通过批处理调用msg命令,msg是系统自在的一个可以发送信息的命令. 示例: @echo off rem 测试MSG msg * "ok" rem 测试M ...

  3. Asp.Net六大内置对象

    前面学习mvc管道处理模型的时候,我们晓的HttpContext是贯穿全文的一个对象,在HttpRuntime产生,现在我们所谓的Asp.Net六大内置对象,其实就是HttpContext的属性.具体 ...

  4. Ubuntu 18.04上安装 phpMyAdmin

    我们将安装 phpMyAdmin 在 Ubuntu18.04 上配合 Apache 一起工作. 在安装 phpMyAdmin 之前需要已经安装了LAMP栈并提供了web页面. 如果没有安装可以参照 U ...

  5. 数据库-mysql01 简单介绍以及安装部署

    本次mysql数据库安装采用二进制安装(免安装即绿色版),数据库版本是mysql5.7.26 首先下载mysql安装包,然后上传服务器里,最后解压. 卸载centos7自带的数据库软件包: [root ...

  6. 流程及迭代驱动测试管理软件, itest 发布到开源中国

    itest 源码已发布到码云 ,项目已被开源中国收录!详见  https://www.oschina.net/p/itest-cn 测试人自己开发,汇聚10年沉淀,独创流程驱动测试.度量展现测试人价值 ...

  7. 使用类似GeoJson的数据生成物体(建筑等)的功能逻辑

    GeoJson作为一种模型传输格式, 用的最多的就是地图里面的各种简单模型了, 比如下图中很贴切的俄罗斯方块楼: 它的格式大概就是下面这样: { "type": "Fea ...

  8. LOJ 3184: 「CEOI2018」斐波那契表示法

    题目传送门:LOJ #3184. 题意简述: 题目说得很清楚了. 题解: 首先需要了解「斐波那契数系」为何物. 按照题目中定义的斐波那契数列 \(F_n\),可以证明,每个非负整数 \(n\) 都能够 ...

  9. VC 静态库与动态库(二)静态库创建与使用

    1.新建项目,创建项目和解决方案 StaticLibrary  这是静态库项目 G:\C++Learn\Library  Library文件夹用于存放库相关文件,包含静态库与后面的动态库工程和解决方案 ...

  10. Mrmr:

    Feature selection: minimum redundancy and maximum relevance feature selection for high-dimensional d ...