-
Hey all, I did do a bit of searching on this, and I think I know what is going on, but I wanted to confirm. When I have vector watching my docker container logs using the docker_logs source, my vector logs fill up with a lot of errors like this:
There was another post a while back about a similar error with Kubernetes logs. The solution, I think, was to drop the labels or transform them into something without dots. So, is Vector looking at the labels and thinking that each individual label with dots in it is actually an object? Is there a way to tell Vector not to do that? Docker itself adds labels with dots in them, and I've seen many other systems do the same. Part of why I'm asking is that when I run docker inspect on a container, the json output clearly shows the labels as keys, not objects. So I kinda think it's a little odd that Vector would try to turn them into objects. And if it isn't doing that, then I need to figure out what is actually causing those errors... Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Right, you might need to "flatten" and de-dot the labels before inserting into Elasticsearch (note the error is coming from Elasticsearch, not Vector). |
Beta Was this translation helpful? Give feedback.
Right, you might need to "flatten" and de-dot the labels before inserting into Elasticsearch (note the error is coming from Elasticsearch, not Vector).