[GH-ISSUE #366] Disable Pipelines for Task Models #166

Open
opened 2026-10-18 21:03:16 +00:00 by bsakaguchi · 2 comments
Owner

Originally created by @darebfh on GitHub (Dec 12, 2024).
Original GitHub issue: https://github.com/open-webui/pipelines/issues/366

Feature Request

Is your feature request related to a problem? Please describe.
I monitor usage statistics using langfuse and the associated pipeline. However, in langfuse also all requests from task models show up and there is no way of filtering these requests from tasks models.

Describe the solution you'd like
I suggest adding a checkbox to the "Pipelines" page in the Admin settings called "include task models". This should be deactived by default.

Describe alternatives you've considered
It would be possible to set the "Pipelines" parameter with the pipeline definition file to the specific models to monitor. Currently, this parameter is set to "*" as I do not know the identifiers of task model pipelines.

Additional context
Add any other context or screenshots about the feature request here.

Originally created by @darebfh on GitHub (Dec 12, 2024). Original GitHub issue: https://github.com/open-webui/pipelines/issues/366 # Feature Request **Is your feature request related to a problem? Please describe.** I monitor usage statistics using langfuse and the associated pipeline. However, in langfuse also all requests from task models show up and there is no way of filtering these requests from tasks models. **Describe the solution you'd like** I suggest adding a checkbox to the "Pipelines" page in the Admin settings called "include task models". This should be deactived by default. **Describe alternatives you've considered** It would be possible to set the "Pipelines" parameter with the pipeline definition file to the specific models to monitor. Currently, this parameter is set to "*" as I do not know the identifiers of task model pipelines. **Additional context** Add any other context or screenshots about the feature request here.
Author
Owner

@audrzejq commented on GitHub (Jan 10, 2025):

That would be good! Thanks for this report!

<!-- gh-comment-id:2584391400 --> @audrzejq commented on GitHub (Jan 10, 2025): That would be good! Thanks for this report!
Author
Owner

@veleinfobip commented on GitHub (Feb 12, 2025):

Maybe you can add to beginning of inlet and outlet some code, like this:

         if "task" in body.get("metadata", {}):
            mtask = body["metadata"]["task"]
            error_message = f"This is task: {mtask}"
            print(f"Skip: {error_message}")
            return body
<!-- gh-comment-id:2654210360 --> @veleinfobip commented on GitHub (Feb 12, 2025): Maybe you can add to beginning of inlet and outlet some code, like this: ``` if "task" in body.get("metadata", {}): mtask = body["metadata"]["task"] error_message = f"This is task: {mtask}" print(f"Skip: {error_message}") return body ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
open-webui/pipelines#166
No description provided.