Morgan Christiansson

Oh yeah it says in gpio/sysfs.txt > THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO > Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS > ARE SUPPOSED TO USE THE...

> use home assistant with an esp01 to control a relay I also considered this. I've seen you can integrate octoprint with homeassistant. And I have a couple Sonoff S20...

I saw PSU Control 1.0 was released with python periphery which should fix this. Thanks for testing it! https://github.com/kantlivelong/OctoPrint-PSUControl/releases

Yeah my home cluster is multi-architecture with Raspberry Pis and 1x fileserver Intel node. But I prefer to run everything on Pis/arm64. Also I think arm64 is useful for all...

I would imagine errors are retried per last ingested event from sincedb

Once you have configured IRSA (IAM Roles for Service Accounts) you can simply omit credentials/profile options to this plugin and it will just work as it does in other Kubernetes...

I'm concerned about data loss here.... Can graceful shutdown be implemented please?

logstash-input-cloudwatch_logs-1.0.0 Can upgrade to 1.0.1 latest but don't see this mentioned in the release notes?

Yeah. ``` [2017-09-20T17:01:25,165][WARN ][logstash.shutdownwatcher ] {"inflight_count"=>12682, "stalling_thread_info"=>{"other"=>[{"thread_id"=>57, "name"=>"[main]worker2", "current_call"=>"[...]/logstash-core/lib/logstash/util/wrapped_synchronous_queue.rb:147:in \`lock'"}, {"thread_id"=>37, "name"=>"[main]>worker3", "current_call"=>"[...]/logstash-core/lib/logstash/util/wrapped_synchronous_queue.rb:147:in \`lock'"}, {"thread_id"=>38, "name"=>"[main]>worker4", "current_call"=>"[...]/logstash-core/lib/logstash/instrument/metric_store.rb:55:in \`put_if_absent'"}, {"thread_id"=>40, "name"=>"[main]>worker6", "current_call"=>"[...]/logstash-core/lib/logstash/util/wrapped_synchronous_queue.rb:147:in \`lock'"}, {"thread_id"=>41, "name"=>"[main]>worker7", "current_call"=>"[...]/logstash-core/lib/logstash/util/wrapped_synchronous_queue.rb:147:in \`lock'"}], ["LogStash::Filters::Mutate", {"remove_field"=>["[cloudwatch_logs][log_stream]"], "id"=>"8c22843b6c1dbf765f64ce96fdf72cc0aaf5ad31-8"}]=>[{"thread_id"=>35, "name"=>"[main]>worker1",...

Here's full logs from logstash-plain.log ``` [2017-09-27T12:50:05,383][WARN ][logstash.runner ] SIGTERM received. Shutting down the agent. [2017-09-27T12:50:05,389][WARN ][logstash.agent ] stopping pipeline {:id=>".monitoring-logstash"} [2017-09-27T12:50:06,432][WARN ][logstash.agent ] stopping pipeline {:id=>"main"} [2017-09-27T12:50:11,460][WARN ][logstash.shutdownwatcher ]...