langgenius/dify

Search by conversation id

Open

#26 643 ouverte le 8 oct. 2025

Voir sur GitHub
 (5 commentaires) (1 réaction) (1 assigné)TypeScript (141 412 stars) (22 210 forks)batch import
good first issue

Description

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Logs should allow search by conversation id and/or message id

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.

Guide contributeur

Stack technique
typescriptpythonsql
Domaine
backendapidatabase
Type d'issue
feature
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
half day
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
blocked
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
mostly clear
Prérequis
Familiarity with Dify's logging systemBasic SQL querying
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
25
Direction de recherche
The issue requests adding search by conversation or message ID in logs. First, identify how logs are stored and queried (likely in a SQL database). Look at the existing log search functionality, probably in the backend API or frontend. Check the repository's data models for conversation and message IDs. Examine any existing search endpoints or UI components that filter logs. The assignee may have context; review any comments or linked PRs for implementation details.