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

Filter based on package logs send by the agent (3.7.2) to Application Insight

未关闭
#4,223 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
azure, java, scala, spark

调研方向

首先检查 instrumentation.logging 部分和 metric-filter 处理器,即 issue 中提到的两个配置路径。为 agent 发送的日志定义包级过滤,然后验证可以排除不需要的第三方包日志,同时不会抑制应用程序自身的日志。

由索引模型根据 Issue 内容生成。

描述

I have a lot of logs generated by 3rd party libraries in my application, which I do not need to have ingested into Application Insights, and those logs generate significant costs on Application Insights. Currently it is only possible to set global log level threshold, which is not sufficient, because the unwanted logs are either INFO or WARN, so to exclude them I would need to exclude also the logs from my application, which makes this solution useless.

In my current scenario I am running a Scala 2.12 Spark application on Azure Databricks runtime 16.3 as a jar task instrumented with -javaagent (agent version 3.7.2) parameter through spark config and APPLICATIONINSIGHTS_CONNECTION_STRING environment variable, and getting a lot of com.databricks.* and org.apache.spark.* logs. But this feature would be applicable to any other scenario.

I would like to be able to filter/configure logs that are send to Application Insight by the agent on package level.

This could be configured either in the instrumentation.logging section or as a log procesor in similar fashion to the metric-filter processor.

主要语言
Java
星标
326
派生
223
平均合并
1 天 1 小时
30 天内合并 PR
15

环境准备

在 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 摘要。