github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-11-21 14:44:00 +00:00
Code Issues Projects Releases Packages Wiki Activity
VictoriaMetrics/app/vminsert
History
Andrii Chubatiuk 2d7b3b1a5c
doing similar changes for both vmagent and vminsert ends up with almost same implementations. one of the reasons is the same Timeseries structure from different prompb and prompbmarshal packages. My proposal is to use structures from prompb package only to marshal/unmarshal sent/received data, but for internal transformations use only structures from prompbmarshal package
2024-10-31 21:56:46 +02:00
..
common doing similar changes for both vmagent and vminsert ends up with almost same implementations. one of the reasons is the same Timeseries structure from different prompb and prompbmarshal packages. My proposal is to use structures from prompb package only to marshal/unmarshal sent/received data, but for internal transformations use only structures from prompbmarshal package 2024-10-31 21:56:46 +02:00
csvimport lib/protoparser/csvimport: extract stream parsing code into a separate stream package 2023-02-13 10:25:46 -08:00
datadogsketches app/{vmagent,vminsert}: follow-up after a1d1ccd6f2 2024-02-07 01:28:05 +02:00
datadogv1 app/{vminsert,vmagent}: preliminary support for /api/v2/series ingestion from new versions of DataDog Agent 2023-12-21 20:50:55 +02:00
datadogv2 lib/protoparser/datadogv2: take into account source_type_name field, since it contains useful value such as kubernetes, docker, system, etc. 2023-12-21 23:05:41 +02:00
graphite app/vmagent: code cleanup for Kafka and Google PubSub consumers / producers 2023-12-04 22:46:28 +02:00
influx doing similar changes for both vmagent and vminsert ends up with almost same implementations. one of the reasons is the same Timeseries structure from different prompb and prompbmarshal packages. My proposal is to use structures from prompb package only to marshal/unmarshal sent/received data, but for internal transformations use only structures from prompbmarshal package 2024-10-31 21:56:46 +02:00
native app/vminsert: replace hybrid sync.Pool+channel-based pool scheme for poolCtx with plain sync.Pool 2024-04-20 21:44:53 +02:00
newrelic app/{vmagent,vminsert}: follow-up for NewRelic data ingestion protocol support 2023-10-16 00:25:25 +02:00
opentelemetry app/vmagent: simplify code after 509df44d03 2024-04-02 17:58:13 +03:00
opentsdb lib/protoparser/opentsdb: extract stream parsing code into a separate stream package 2023-02-13 10:03:16 -08:00
opentsdbhttp lib/protoparser/opentsdbhttp: extract stream parsing code into a separate stream package 2023-02-13 10:16:03 -08:00
prometheusimport lib/promscrape: make concurrency control optional (#5073) 2023-10-02 21:32:11 +02:00
prompush app,lib: fix typos in comments (#3804) 2023-02-13 13:27:13 +01:00
promremotewrite lib/prompb: change type of Label.Name and Label.Value from []byte to string 2024-01-14 22:33:21 +02:00
relabel doing similar changes for both vmagent and vminsert ends up with almost same implementations. one of the reasons is the same Timeseries structure from different prompb and prompbmarshal packages. My proposal is to use structures from prompb package only to marshal/unmarshal sent/received data, but for internal transformations use only structures from prompbmarshal package 2024-10-31 21:56:46 +02:00
static/css all: follow-up after 8edb390e21 2022-06-07 00:57:09 +03:00
vmimport app/vminsert: replace hybrid sync.Pool+channel-based pool scheme for poolCtx with plain sync.Pool 2024-04-20 21:44:53 +02:00
main.go app/{vminsert,vmagent}: add healthcheck for influx ingestion endpoints (#6749) 2024-08-05 09:34:54 +02:00
README.md all: open-sourcing single-node version 2019-05-23 00:18:06 +03:00

README.md

vminsert routes the ingested data to vmstorage.