Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hello Guys, Can You Tell Me Where The Console Outputs Are Stored? For Some Reason, All Outputs Have Disappeared From All My Pipelines. Any Explanation, Does Anyone Have An Idea What Might Have Happened?

Hello guys, can you tell me where the console outputs are stored? For some reason, all outputs have disappeared from all my pipelines. Any explanation, does anyone have an idea what might have happened?
image

  
  
Posted 2 months ago
Votes Newest

Answers 5


I was digging around a bit, it seems that for the worker containers use default logging, that is: they use json.log files stored in /var/lib/docker/container/<hash> folders. When I do up/down of docker compose, these container folders are purged and with them my console log is gone.

  
  
Posted 2 months ago

Hi @<1702492411105644544:profile|YummyGrasshopper29> , console logs are saved in Elastic. I would check on the status of your container

  
  
Posted 2 months ago

Is there a possibility that it was using Elastic before (through some logging driver) but that it defaulted to using json.log (default) logger driver now?

  
  
Posted 2 months ago

Looks like that there was problem with elastic search docker container. Everything was good after restarting machine.

  
  
Posted one month ago

Looks like that docker-compose down && docker-compose up flush console output. I upgraded server to 1.16.2-502, didn't had that problem before. Any idea?

  
  
Posted 2 months ago
90 Views
5 Answers
2 months ago
one month ago
Tags