#Kill stream without alerts

1 messages · Page 1 of 1 (latest)

native marsh
#

Version 1.4.19

Hello everyone.

Is there a way to kill a stream without getting an alert that needs to be acknowledged or dismissed? Maybe just keep a log of the kill stream, but not have to personally act on the violation?

I have a rule that kills 4k transcodes. I always have both a 4k and 1080p file, so if a user transcodes the rule kills the streams and tells them to play the 1080p version.

I don't want to get rid of the rule, and I actually would love it if it kept a log of when it does this, but I don't want this being something that I have to manually acknowledge or dismiss every time, and I don't want it affecting trust scores.

Is there a way I'm missing to do this?

I just want it to kill the stream without adding an alert. Although still having a log would be cool.

sick owlBOT
# native marsh Version 1.4.19 Hello everyone. Is there a way to kill a stream without gettin...

Thanks for opening a support thread!
Please include the following so we can help:

Required Information

• Tracearr version
• Environment (Docker, LXC, Unraid, etc.)
• Docker compose file
• Logs (pastebin.com) or screenshots

Describe The Issue

• Expected behavior
• Actual behavior
• Steps to reproduce

Read The Docs

Docs · Logs · FAQ

native marsh
#

Running in unraid using supervised.

proven wolf
#

@native marsh There is not at this time - but maybe an "auto acknowlege" could be an action that could be added to a rule-set

#

#request-a-feature

If you throw something in there i can look to add it at some point

#

its not a heavy lift

native marsh
#

Only problem with the auto acknowledge is it's still affecting trust scores which I'm hoping to use to find people sharing their account (pretty sure my aunt is and I want evidence lol)

But otherwise copy. I'll post it in request a feature

proven wolf
#

Bc trust score additions should be controlled purely in rule actions now

#

must have missed something in the transition

native marsh
#

Really? Well let me test what it does if I acknowledge all these. It negative scored a few weeks ago when I first installed tracearr. I havent tried recently

proven wolf
#

I mean if you'd like that would at least confirm it

native marsh
#

Yup. Just acknowledged all of them and my mom now has a trust score of 75 from acking those.

proven wolf
#

JK lmao

#

Ok let me see what i wanna do here

#

It's just not transparent right now

#

so that's the issue

#

but its not transparent because i missed it lol

native marsh
#

Well, I'm not gonna pretend like I know the solution. I'm good at complaining about problems, not fixing them.

I will post a feature request to have auto approve in the rules. I think that would be great. That way I get the logged history and it doesn't effect trust score.

Was the intention for trust score to only be affected when the rule is explicitly set to change their trust score?

proven wolf
#

Yup that was it

#

V1 rules were predefined, and very limited in scope. It was the core of this tool, but was also me testing at a large scale to see how far i could push the concept

native marsh
#

Well. Fwiw. I love the concept and the tool in general works great for the actual purpose of killing the stream and giving the user a message 🙂

#

Feature request posted. Do you need me to post the bug with the trust score changing, or no?

#

Another idea.

You currently have the rules severity as I think Low, warning, high.

Maybe add a 4th that is Log only. Make that one not require acknowledgement, it's just a log of what happens.

#

Then you can keep the current functionality (it's a feature not a bug) of the other options affecting trust score

proven wolf
#

because the log is violations

#

so the combination of your FR + the bugfix is "log only"

native marsh
#

Copy. Well thanks for your help.

proven wolf
#

Do you mind putting in the bug? Sorry to be a pain

#

I just am so busy today and i do not want to lose track of it

native marsh
#

No problem. I'll do it.

proven wolf
#

TyVm!