Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Ability to mark some database exceptions as not errors

Aberta
  • Algo errado?
#12,838 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java
Domínio
observability

Direção de pesquisa

Start by reading the JDBC instrumentation and TraceInterceptor APIs to see how exceptions are marked on instrumentation generated spans and what span relationship information the interceptor exposes. The issue names no files or tests, so first locate those entry points and check for existing exception suppression options. Done means callers can conditionally prevent expected exceptions from being reported as errors without reconstructing the span hierarchy.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

type: feature request
Library Name

jdbc

Library Version(s)

17

Describe the feature you'd like

I would like ability to conditionally suppress errors on instrumentation-generated spans.

Is your feature request related to a problem?

DataDog JDBC instrumentation reports all exceptions as errors.

This quite problematic because some exceptions might be expected (such as serialization errors up until final retry), yet there is no way to mark them as such, and so they create a lot of noise that makes error monitors useless.

Describe alternatives you've considered

The only workaround I know is registering TraceInterceptor and clear the errors from there.

To do it conditionally I need to somehow communicate decision to interceptor.

I can set error.suppress=true on application-controlled parent span of db span but unfortunately TraceInterceptor does not expose parent/child relationship between spans unless I do a lot of casts to io.opentracing.Span and DDSpanContext and reconstruct hierarchy from there (which can become expensive).

Additional context

No response

Linguagem predominante
Java
Estrelas
736
Forks
364
Merge médio
3d 9h
PRs com merge (30d)
219

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de DataDog/dd-trace-java

Todas as issues de DataDog/dd-trace-java

Issues semelhantes

Mais issues de Java

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.