Jesse Szwedko

Just bumping this as I ran into it today given the last movement was ~ a year ago. Is there anything that needs to change for this PR? I'm happy...

Thanks for the response @Velfi ! I missed that the request could be split into parts and reconstructed. We can give that a shot. Otherwise that UI you mentioned looks...

Me too, are there any workarounds?

Agreed @kenji-isuntv, this has been a personal annoyance of mine as well; you articulate the issue well here. I'll try to take a crack at this soon when I have...

@Strift PRs would definitely be welcome! I lost track of this issue and unfortunately won't have a ton of time over the next month or so to tackle the implementation...

Hi @Robin11, With ``` golang package main import ( "os" "github.com/urfave/cli" ) func main() { cli.HelpFlag = cli.BoolFlag{ Name: "help", Usage: "To show help for the tool", } cli.NewApp().Run(os.Args) }...

Aha, I see what you are saying now. This actually appears to be because of special handling of `-h` by the stdlib `flag` library (which we use under the hood...

Hi @danthegoodman1 ! It seems like some of the incoming events are not JSON. I might suggest augmenting your `remap` program to log the event that fails to parse as...

As an aside, you are currently parsing `.message` as JSON twice. I'd recommend making: ``` if !exists(parse_json!(.message).level) { ``` instead ``` f !exists(.temp.level) { ```

@danthegoodman1 ah, I see. The log messages you shared above just indicate JSON parsing failures. Are there more error logs?