Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
#4,223 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, java, scala, spark
Domain
cloud, observability

Research direction

Start by reviewing the instrumentation.logging section and the metric-filter processor, the two configuration paths named in the issue. Define package-level filtering for logs sent by the agent, then verify that unwanted third-party package logs can be excluded without suppressing the application's own logs.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Java
Stars
327
Forks
222
Avg merge
22h 34m
Merged PRs (30d)
14

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/ApplicationInsights-Java

All issues in microsoft/ApplicationInsights-Java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.