Replies: 2 comments 5 replies
-
The reason for my question above is because I created a toml using csv.lua, and sending to Victoria Metrics via Prometheus Remote Write. the metrics are written fine for a random amount of time but then Victoria Metrics stops receiving metrics. The logs for Vector have no errors or warnings it just keeps watching new files. I've tried using buffer memory, and then disc. I've increased disc size, I've tried to increase batch.timeout_secs just incase that was where it was backing up, and I've tried to increase fingerprint just incase it was an issue with same values across the top. nothing seems to work. Below is my source and sink toml configs my transform is using csv.lua to put all values into a 2d array and then spinning through every Message/Event for each realm and sending the value for each metric header. Change this to use a non-default directory for Vector data storage:data_dir = "/.../.../vector" Random Syslog-formatted logs[sources.vectorsiprealmmethod] include = ["/.../.../.../sip-realm-method/*.csv"] Sink:
|
Beta Was this translation helpful? Give feedback.
-
The easiest way to parse CSV data in Vector is to use the https://vector.dev/docs/reference/vrl/functions/#parse_csv function in a |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What is the best way to parse a multiline csv into metrics? The first row is header row, 1st column is to be ignored, metrics are nested 2nd column then 3rd column. 4th-115th columns are the actual metrics values.
(Not sure if it makes a difference but each csv will have a different name based on timestamp)
New csv will come in every minute.
<style> </style>here is a sample of the the csv:
Beta Was this translation helpful? Give feedback.
All reactions