That hasn't been glued up, but likely will be. Something similar for
k8s has been discussed. You could certainly use lua to do something
custom. I suspect lua to customize the canned ops-log will become an
option, too.
Matt
On Fri, May 7, 2021 at 5:51 PM David Orman wrote:
>
> Has anyone
Has anyone figured out an elegant way to emit this from inside cephadm
managed/containerized ceph, so it can be handled via the host's
journald and processed/shipped? We had gone down that path before, but
decided to hold off on the suggestion that the LUA-based scripting
might be a better option.
Hi David,
I think the solution is most likely the ops log. It is called for
every op, and has the transaction id.
Matt
On Fri, May 7, 2021 at 4:58 PM David Orman wrote:
>
> Hi Yuval,
>
> We've managed to get an upgrade done with the 16.2.3 release in a
> testing cluster, and we've been able
Hi Yuval,
We've managed to get an upgrade done with the 16.2.3 release in a
testing cluster, and we've been able to implement some of the logging
I need via this mechanism, but the logs are emitted only when
debug_rgw is set to 20. I don't need to log any of that level of data
(we used
Hi Folks,
A Red Hat SA (Mustafa Aydin) suggested, some while back, a concise
formula for relaying ops-log to syslog, basically a script executing
socat unix-connect:/var/run/ceph/opslog,reuseaddr UNIX-CLIENT:/dev/log &
I haven't experimented with it.
Matt
On Thu, Apr 1, 2021 at 12:22 PM Yuval
Hi David,
Don't have any good idea for "octopus" (other than ops log), but you can do
that (and more) in "pacific" using lua scripting on the RGW:
https://docs.ceph.com/en/pacific/radosgw/lua-scripting/
Yuval
On Thu, Apr 1, 2021 at 7:11 PM David Orman wrote:
> Hi,
>
> Is there any way to log
