30098ac8bd
- Parse protobuf if Content-Type isn't set to `application/json` - this behavior is documented at https://grafana.com/docs/loki/latest/api/#push-log-entries-to-loki - Properly handle gzip'ped JSON requests. The `gzip` header must be read from `Content-Encoding` instead of `Content-Type` header - Properly flush all the parsed logs with the explicit call to vlstorage.MustAddRows() at the end of query handler - Check JSON field types more strictly. - Allow parsing Loki timestamp as floating-point number. Such a timestamp can be generated by some clients, which store timestamps in float64 instead of int64. - Optimize parsing of Loki labels in Prometheus text exposition format. - Simplify tests. - Remove lib/slicesutil, since there are no more users for it. - Update docs with missing info and fix various typos. For example, it should be enough to have `instance` and `job` labels as stream fields in most Loki setups. - Allow empty of missing timestamps in the ingested logs. The current timestamp at VictoriaLogs side is then used for the ingested logs. This simplifies debugging and testing of the provided HTTP-based data ingestion APIs. The remaining MAJOR issue, which needs to be addressed: victoria-logs binary size increased from 13MB to 22MB after adding support for Loki data ingestion protocol at https://github.com/VictoriaMetrics/VictoriaMetrics/pull/4482 . This is because of shitty protobuf dependencies. They must be replaced with another protobuf implementation similar to the one used at lib/prompb or lib/prompbmarshal . |
||
|---|---|---|
| .. | ||
| base | ||
| builder | ||
| provisioning | ||
| victorialogs | ||
| alertmanager.yml | ||
| alerts-cluster.yml | ||
| alerts-health.yml | ||
| alerts-vmagent.yml | ||
| alerts-vmalert.yml | ||
| alerts.yml | ||
| docker-compose-cluster.yml | ||
| docker-compose.yml | ||
| Makefile | ||
| prometheus-cluster.yml | ||
| prometheus.yml | ||
| README.md | ||
Docker compose environment for VictoriaMetrics
Docker compose environment for VictoriaMetrics includes VictoriaMetrics components, Alertmanager and Grafana.
For starting the docker-compose environment ensure you have docker installed and running and access to the Internet. All commands should be executed from the root directory of the repo.
To spin-up environment for single server VictoriaMetrics run the following command:
make docker-single-up
To shut down the docker-compose environment for single server run the following command:
make docker-single-down
For cluster version the command will be the following:
make docker-cluster-up
To shut down the docker compose environment for cluster version run the following command:
make docker-cluster-down
VictoriaMetrics single server
VictoriaMetrics will be accessible on the following ports:
--graphiteListenAddr=:2003--opentsdbListenAddr=:4242--httpListenAddr=:8428
The communication scheme between components is the following:
- vmagent sends scraped metrics to
single server VictoriaMetrics; - grafana is configured with datasource pointing to
single server VictoriaMetrics; - vmalert is configured to query
single server VictoriaMetricsand send alerts state and recording rules back to it; - alertmanager is configured to receive notifications from
vmalert.
To access vmalert use link http://localhost:8428/vmalert.
To access vmui use link http://localhost:8428/vmui.
VictoriaMetrics cluster
VictoriaMetrics cluster environment consists of vminsert, vmstorage and vmselect components.
vmselect has exposed port :8481, vminsert has exposed port :8480 and the rest of components
are available only inside the environment.
The communication scheme between components is the following:
- vmagent sends scraped metrics to
vminsert; vminsertforwards data tovmstorage;vmselectis connected tovmstoragefor querying data;- grafana is configured with datasource pointing to
vmselect; - vmalert is configured to query
vmselectand send alerts state and recording rules tovminsert; - alertmanager is configured to receive notifications from
vmalert.
To access vmalert use link http://localhost:8481/select/0/prometheus/vmalert.
To access vmui use link http://localhost:8481/select/0/prometheus/vmui.
vmagent
vmagent is used for scraping and pushing time series to VictoriaMetrics instance. It accepts Prometheus-compatible configuration prometheus.yml with listed targets for scraping.
vmalert
vmalert evaluates alerting rules alerts.yml to track VictoriaMetrics health state. It is connected with AlertManager for firing alerts, and with VictoriaMetrics for executing queries and storing alert's state.
alertmanager
AlertManager accepts notifications from vmalert and fires alerts.
All notifications are blackholed according to alertmanager.yml config.
Grafana
To access service open following link.
Default credential:
- login -
admin - password -
admin
Grafana is provisioned by default with following entities:
VictoriaMetricsdatasourceVictoriaMetrics - clusterdatasourceVictoriaMetrics overviewdashboardVictoriaMetrics - clusterdashboardVictoriaMetrics - vmagentdashboardVictoriaMetrics - vmalertdashboard
Remember to pick VictoriaMetrics - cluster datasource when viewing VictoriaMetrics - cluster dashboard.