From 6bcbdb18fb61ccd3ad53ab079fec4ec91672359d Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Mon, 16 Nov 2020 15:34:20 +0200 Subject: [PATCH] docs/CHANGELOG.md: mention about Graphite Tags API implementation --- docs/CHANGELOG.md | 2 ++ docs/Single-server-VictoriaMetrics.md | 17 +++++++++++++---- 2 files changed, 15 insertions(+), 4 deletions(-) diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index d30bc3c21a..2ffedf4a47 100644 --- a/docs/CHANGELOG.md +++ b/docs/CHANGELOG.md @@ -21,6 +21,8 @@ * FEATURE: update Go builder from v1.15.4 to v1.15.5. This should fix [these issues in Go](https://github.com/golang/go/issues?q=milestone%3AGo1.15.5+label%3ACherryPickApproved). * FEATURE: added `/internal/force_flush` http handler for flushing recently ingested data from in-memory buffers to persistent storage. See [troubleshooting docs](https://victoriametrics.github.io/#troubleshooting) for more details. +* FEATURE: added [Graphite Tags API](https://graphite.readthedocs.io/en/stable/tags.html) support. + See [these docs](https://victoriametrics.github.io/#graphite-tags-api-usage) for details. * BUGFIX: do not return data points in the end of the selected time range for time series ending in the middle of the selected time range. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/887 and https://github.com/VictoriaMetrics/VictoriaMetrics/issues/845 diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 22812cf5e5..f581651eba 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -106,8 +106,9 @@ Click on a link in order to read the corresponding case study * [How to send data from OpenTSDB-compatible agents](#how-to-send-data-from-opentsdb-compatible-agents) * [Prometheus querying API usage](#prometheus-querying-api-usage) * [Prometheus querying API enhancements](#prometheus-querying-api-enhancements) -* [Graphite Metrics API usage](#graphite-metrics-api-usage) -* [Graphite Tags API usage](#graphite-tags-api-usage) +* [Graphite API usage](#graphite-api-usage) + * [Graphite Metrics API usage](#graphite-metrics-api-usage) + * [Graphite Tags API usage](#graphite-tags-api-usage) * [How to build from sources](#how-to-build-from-sources) * [Development build](#development-build) * [Production build](#production-build) @@ -528,7 +529,15 @@ Additionally VictoriaMetrics provides the following handlers: * `/api/v1/status/active_queries` - it returns a list of currently running queries. -### Graphite Metrics API usage +### Graphite API usage + +VictoriaMetrics supports the following Graphite APIs: + +* Metrics API - see [these docs](#graphite-metrics-api-usage). +* Tags API - see [these docs](#graphite-tags-api-usage). + + +#### Graphite Metrics API usage VictoriaMetrics supports the following handlers from [Graphite Metrics API](https://graphite-api.readthedocs.io/en/latest/api.html#the-metrics-api): @@ -542,7 +551,7 @@ VictoriaMetrics accepts the following additional query args at `/metrics/find` a that start with `node_`. By default `delimiter=.`. -### Graphite Tags API usage +#### Graphite Tags API usage VictoriaMetrics supports the following handlers from [Graphite Tags API](https://graphite.readthedocs.io/en/stable/tags.html):