Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Unable to easily suppress dependency exception using java agent

未关闭
  • 哪里不对？
#3,144 4 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@heyams 已经在做这个了。

开始于 2023年6月20日。

评估

这个 Issue 还没有评估数据。

描述

Needs: Attention :wave:
Expected behavior

I was hoping to suppress an exception using exception.message or exception.stacktrace that is flooding our logs - 900,000 times a day.

Actual behavior

I only appear to be able to suppress the exception using exception.type.

To Reproduce

I started off followed the steps detailed in Span Attributes Available for Sampling to look for the exception. Whilst I can see all the dependencies exported that way, it appears that the exceptions are exported differently and don't appear with text exporting span. In my case I can see the exception as json in the log, for example

{
  "ver": 1,
  "name": "Exception",
  "time": "2023-06-19T11:41:42.152Z",
  "iKey": "b44af8fc-1647-443d-8cea-55c5cfbd4518",
  "tags": {
    "ai.internal.sdkVersion": "java:3.4.13",
  },
  "data": {
    "baseType": "ExceptionData",
    "baseData": {
      "ver": 2,
      "exceptions": [
        {
          "typeName": "java.sql.SQLException",
          "message": "ORA-06550: line 1, column 28:",
          "stack": "java.sql.SQLException: ORA-06550: line 1, column 28:\nPLS-00302: component 'GETMAXIDENTIFIERLENGTH' must be declared..."
        }
      ]
    }
  }

I can get the suppression working with configuration such as

          "telemetryType": "exception",
          "attributes": [
            {
              "key": "exception.type",
              "value": "java.sql.SQLException",
              "matchType": "strict"
            }
          ],
          "percentage": 0

but would ideally like to match on the message or stacktrace instead. According to the opentelemetry exception documentation I think I should be matching on exception.message or exception.stacktrace, but can't get either to work. For example I think:

          "telemetryType": "exception",
          "attributes": [
            {
              "key": "exception.stacktrace",
              "value": ".*GETDBCOMPATMAJORVERSION.*",
              "matchType": "regexp"
            }
          ],
          "percentage": 0

should do the trick, but the exception still appears in the logs. I've also tried suppressing the dependency, which works fine with the above regexp but doesn't suppress the corresponding exception.

Please could you let me know the key that I need therefore to match on the stacktrace and / or message to suppress the exception. Looking at the Oracle code that throws the exception it appears to be caught and doesn't then affect the behaviour of the application, hence the reason for the suppression.

System information

Please provide the following information:

  • SDK Version: java:3.4.13
  • OS type and version: Based off docker image eclipse-temurin:19-jre-jammy so Java 19
  • Application Server type and version (if applicable): Spring Boot 3.1.0
  • Using spring-boot? Yes
主要语言
Java
星标
326
派生
223
平均合并
23 小时 6 分钟
30 天内合并 PR
13

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

microsoft/ApplicationInsights-Java 的其他 Issue

查看 microsoft/ApplicationInsights-Java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。