Monitoring UI: Visibility of User Messages in the "Activity" Panel

[HannesStrohkopp]

Cheers,

first of all: Thank you for this great tool - it helps a ton!

However, I noticed that I as an admin are able to read all user messages and LLM answers via the /ui->activity->capture->view fields. Due to reasons of privacy, I would prefer not to have this option.

I tried to comb through the extensive config.example.yaml and found "captureBuffer: 0". This actually erases all data on llama-swap reboot. However, for the current session, the data is still logged.

My prefered solution would be to actually long-term retain all logged data but WITHOUT the actual inference-content.

Can someone maybe help me on this please?

[sousekd]

It would be great to have some flexibility in configuring this.

I'd like to be able to hide the messages from the Activity panel, too. We are a small team, and I allow my users unauthenticated access to llama-swap UI to resolve issues, see which models are loaded, etc. But the fact they can read each other messages is not exactly desired.

I understand that @mostlygeek likely does not want to deal with all the authentication/permissions related stuff, but even little things like to make configuration toggle to enable/disable the Activity tab would help.

For me, a naive "PIN protected" approach to access the Activity tab would be ideal :).

[mostlygeek]

Hi,

Setting captureBuffer: 0 disables the captures only. The basic metrics in the activity log are always available.

This actually erases all data on llama-swap reboot. However, for the current session, the data is still logged.

I'm not sure what you mean here. llama-swap is stateless and all data is cleared on restart. The captureBuffer doesn't have any effect on that property.

There's no log retention or state saving anywhere. When you restart llama-swap it starts from a clean slate state.

[HannesStrohkopp]

Oh okay, understood. Thanks for your answer - my bad on the general understanding.

So basically, what I look for is not available and therefore a feature request?

[XenoUniv3rse]

Hi,

Setting captureBuffer: 0 disables the captures only. The basic metrics in the activity log are always available.

This actually erases all data on llama-swap reboot. However, for the current session, the data is still logged.

I'm not sure what you mean here. llama-swap is stateless and all data is cleared on restart. The captureBuffer doesn't have any effect on that property.

There's no log retention or state saving anywhere. When you restart llama-swap it starts from a clean slate state.

Is there a way to preserve the activity data? I am the only one using it and would like to keep that there for performance debuging etc.