support mix content (json and non-son) about fx HOT 6 CLOSED

For this purpose I have this https://github.com/antonmedv/eat

from fx.

Hum... not quite. That supports eating a whole file. I’m hoping to support interspersed text in the JSON. We have logs that are a mix of plain text and JSON

from fx.

Can you show an example?

from fx.

This is a REST backend service with a proxy in front of it. The proxy does plain text logging and the backend does JSON logging. The logs are streamed together from a kubernetes POD and a request looks like:
{
"comment": "",
"fields.time": "2019-01-20T22:32:38Z",
"ip": "100.65.12.18",
"latency": " 21.215983ms",
"level": "info",
"method": "PUT",
"msg": "[GIN] --------------------------------------------------------------- GinLogrusWithTracing ----------------------------------------------------------------",
"path": "/products/manasi-test-id",
"requestID": "36763cff53b68dce:532fdd959b064e8a:56b5f4bdec9a08af:0",
"status": 200,
"time": "2019-01-20T22:32:38Z",
"user-agent": "Go-http-client/1.1"
}
time="2019-01-20T22:32:38Z" level=info msg="proxyRequest took 27.679495ms" path=/products/manasi-test-id x-service-ticket=true requestID="36763cff53b68dce:393a4a39863433af:319aaa8a29f1957a:0" method=PUT
time="2019-01-20T22:32:38Z" level=debug msg="updateMetrics: proxyRequest / 31ms / 27.679495ms" path=/products/manasi-test-id x-service-ticket=true requestID="36763cff53b68dce:393a4a39863433af:319aaa8a29f1957a:0" method=PUT
time="2019-01-20T22:32:38Z" level=info msg="updateMetrics took 1.058µs" requestID="36763cff53b68dce:393a4a39863433af:319aaa8a29f1957a:0" method=PUT path=/products/manasi-test-id x-service-ticket=true
time="2019-01-20T22:32:38Z" level=info msg="[GIN] --------------------------------------------------------------- GinLogrusWithTracing ----------------------------------------------------------------" path=/products/manasi-test-id latency=" 28.62963ms" user-agent=Go-http-client/1.1 requestID="36763cff53b68dce:7fc8d054c277ae01:393a4a39863433af:0" status=200 comment= method=PUT ip=100.65.12.18 time="2019-01-20T22:32:38Z"

from fx.

you can see the mix content. it would be great if fx just wrapped the plain text in some sort of default JSON object or just ignored it.

from fx.

I think this can go inside eat tool to, if you can write a parser for it.

from fx.