1# Promscale command line doc
2
3This document gives you information about the configuration flags and arguments supported by Promscale.
4You can also find information on flags with `promscale_<version> -help`.
5
6**Note:** Flags can be set as environment variables by converting `-` to `_` (if any), and prefixing with `PROMSCALE_`. For example, `db-host` can be set as an environment variable as `PROMSCALE_DB_HOST`.
7
8## Arguments
9| Argument | Description |
10|:------:|:-----|
11| version | Prints the version information of Promscale. |
12| help | Prints the information related to flags supported by Promscale.
13
14## General flags
15| Flag | Type | Default | Description |
16|:------:|:-----:|:-------:|:-----------|
17| config | string | config.yml | YAML configuration file path for Promscale. |
18| install-extensions | boolean | true | Install TimescaleDB & Promscale extensions. |
19| upgrade-extensions | boolean | true | Upgrades TimescaleDB & Promscale extensions. |
20| upgrade-prerelease-extensions | boolean | false | Upgrades to pre-release TimescaleDB, Promscale extensions. |
21| leader-election-pg-advisory-lock-id | integer | 0 (disabled) | Leader-election based high-availability. It is based on PostgreSQL advisory lock and requires a unique advisory lock ID per high-availability group. Only a single connector in each high-availability group will write data at one time. A value of 0 disables leader election. |
22| leader-election-pg-advisory-lock-prometheus-timeout | slack/duration | -1 | Prometheus timeout duration for leader-election high-availability. The connector will resign if the associated Prometheus instance does not send any data within the given timeout. This value should be a low multiple of the Prometheus scrape interval, big enough to prevent random flips. |
23| leader-election-scheduled-interval | duration | 5 seconds | Interval at which scheduled election runs. This is used to select a leader and confirm that we still holding the advisory lock. |
24| log-format | string | logfmt | Log format to use from [ "logfmt", "json" ]. |
25| log-level | string | debug | Log level to use from [ "error", "warn", "info", "debug" ]. |
26| migrate | string | true | Update the Prometheus SQL schema to the latest version. Valid options are: [true, false, only]. |
27| read-only | boolean | false | Read-only mode for the connector. Operations related to writing or updating the database are disallowed. It is used when pointing the connector to a TimescaleDB read replica. |
28| use-schema-version-lease | boolean | true | Use schema version lease to prevent race conditions during migration. |
29| async-acks | boolean | false | Acknowledge asynchronous inserts. If this is true, the inserter will not wait after insertion of metric data in the database. This increases throughput at the cost of a small chance of data loss. |
30| tput-report | duration | 1 second | Duration interval at which throughput should be reported. Setting duration to `0` will disable reporting throughput, otherwise, an interval with unit must be provided, e.g. `10s` or `3m`. |
31| tls-cert-file | string | "" (disabled) | TLS certificate file path for web server. To disable TLS, leave this field as blank. |
32| tls-key-file | string | "" (disabled) | TLS key file path for web server. To disable TLS, leave this field as blank. |
33| web-cors-origin | string | `.*` |  Regex for CORS origin. It is fully anchored. Example: 'https?://(domain1|domain2)\.com' |
34| web-enable-admin-api | boolean | false | Allow operations via API that are for advanced users. Currently, these operations are limited to deletion of series. |
35| web-listen-address | string | `:9201` | Address to listen on for web endpoints. |
36| web-telemetry-path | string | `/metrics` | Web endpoint for exposing Promscale's Prometheus metrics. |
37
38## Resource usage flags
39| Flag | Type | Default | Description |
40|------|:-----:|:-------:|:-----------|
41| memory-target | unsigned-integer or percentage | 80% | Target for max amount of memory to use. Specified in bytes or as a percentage of system memory (e.g. 80%). |
42| labels-cache-size P| unsigned-integer | 10000 | Maximum number of labels to cache. |
43| metrics-cache-size | unsigned-integer | 10000 | Maximum number of metric names to cache. |
44| series-cache-initial-size | unsigned-integer| 250000 | Initial number of elements in the series cache. |
45| series-cache-max-bytes | unsigned-integer or percentage | 50% |  Target for amount of memory to use for the series cache. Specified in bytes or as a percentage of the memory-target (e.g. 50%). |
46
47## Auth flags
48
49| Flag | Type | Default | Description |
50|:------:|:-----:|:-------:|:-----------|
51| auth-username | string | "" | Authentication username used for web endpoint authentication. Disabled by default. |
52| auth-password | string | "" | Authentication password used for web endpoint authentication. This flag should be set together with auth-username. It is mutually exclusive with auth-password-file and bearer-token methods. |
53| auth-password-file | string | "" | Path for auth password file containing the actual password used for web endpoint authentication. This flag should be set together with auth-username. It is mutually exclusive with auth-password and bearer-token methods. |
54| bearer-token | string | "" (disabled) | Bearer token (JWT) used for web endpoint authentication. Disabled by default. Mutually exclusive with bearer-token-file and basic auth methods. |
55| bearer-token-file | string | "" (disabled) | Path of the file containing the bearer token (JWT) used for web endpoint authentication. Disabled by default. Mutually exclusive with bearer-token and basic auth methods. |
56
57## Multi-tenancy flags
58
59| Flag | Type | Default | Description |
60|:------:|:-----:|:-------:|:-----------|
61| multi-tenancy | boolean | false | Use multi-tenancy mode in Promscale. |
62| multi-tenancy-allow-non-tenants | boolean | false | Allow Promscale to ingest/query all tenants as well as non-tenants. By setting this to true, Promscale will ingest data from non multi-tenant Prometheus instances as well. If this is false, only multi-tenants (tenants listed in 'multi-tenancy-valid-tenants') are allowed for ingesting and querying data. |
63| multi-tenancy-valid-tenants | string | allow-all |  Sets valid tenants that are allowed to be ingested/queried from Promscale. This can be set as: 'allow-all' (default) or a comma separated tenant names. 'allow-all' makes Promscale ingest or query any tenant from itself. A comma separated list will indicate only those tenants that are authorized for operations from Promscale. |
64
65## Database flags
66
67| Flag | Type | Default | Description |
68|:------:|:-----:|:-------:|:-----------|
69| app | string | promscale@{version} | 'app' sets application_name in database connection string. This is helpful during debugging when looking at pg_stat_activity. |
70| db-host | string | localhost | Host for TimescaleDB/Vanilla Postgres. |
71| db-port | int | 5432 | TimescaleDB/Vanilla Postgres connection password. |
72| db-name | string | timescale | Database name. |
73| db-password | string | | Password for connecting to TimescaleDB/Vanilla Postgres. |
74| db-user | string | postgres | TimescaleDB/Vanilla Postgres user. |
75| db-connect-retries | integer | 0 | Number of retries Promscale should make for establishing connection with the database. |
76| db-connection-timeout | duration | 60 seconds | Timeout for establishing the connection between Promscale and TimescaleDB. |
77| db-connections-max | integer | 80% of possible connections db | Maximum number of connections to the database that should be opened at once. It defaults to 80% of the maximum connections that the database can handle. |
78| db-ssl-mode | string | require | TimescaleDB/Vanilla Postgres connection ssl mode. If you do not want to use ssl, pass `allow` as value. |
79| db-writer-connection-concurrency | integer | 4 | Maximum number of database connections for writing per go process. |
80| db-uri | string | | TimescaleDB/Vanilla PostgresSQL URI. Example:`postgres://postgres:password@localhost:5432/timescale?sslmode=require` |
81| db-statements-cache | boolean | true | Whether database connection pool should use cached prepared statements. Disable if using PgBouncer. |
82| ignore-samples-written-to-compressed-chunks | boolean | false | Ignore/drop samples that are being written to compressed chunks. Setting this to false allows Promscale to ingest older data by decompressing chunks that were earlier compressed. However, setting this to true will save your resources that may be required during decompression. |
83| async-acks | boolean | false | Acknowledge asynchronous inserts. If this is true, the inserter will not wait after insertion of metric data in the database. This increases throughput at the cost of a small chance of data loss. |
84
85## PromQL engine evaluation flags
86
87| Flag | Type | Default | Description |
88|:------:|:-----:|:-------:|:-----------|
89| promql-enable-feature | string | "" | [EXPERIMENTAL] Enable optional PromQL features, separated by commas. These are disabled by default in Promscale's PromQL engine. Currently, this includes 'promql-at-modifier' and 'promql-negative-offset'. For more information, see https://github.com/prometheus/prometheus/blob/master/docs/disabled_features.md |
90| promql-query-timeout | duration | 2 minutes | Maximum time a query may take before being aborted. This option sets both the default and maximum value of the 'timeout' parameter in '/api/v1/query.*' endpoints. |
91| promql-default-subquery-step-interval | duration | 1 minute | Default step interval to be used for PromQL subquery evaluation. This value is used if the subquery does not specify the step value explicitly. Example: <metric_name>[30m:]. Note: in Prometheus this setting is set by the evaluation_interval option. |
92| promql-lookback-delta | duration | 5 minute | The maximum look-back duration for retrieving metrics during expression evaluations and federation. |
93| promql-max-samples | integer64 | 50000000 | Maximum number of samples a single query can load into memory. Note that queries will fail if they try to load more samples than this into memory, so this also limits the number of samples a query can return. |
94| promql-max-points-per-ts  | integer64 | 11000 | Maximum number of points per time-series in a query-range request. This calculation is an estimation, that happens as (start - end)/step where start and end are the 'start' and 'end' timestamps of the query_range. |
95