I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

Thnaks birfincankafein@ for reaching out.

1. D/FirebasePerformance: Creating a new Non Verbose Session: XXXXX

Session ID is an anonymous information which is solely for the debugging purposes, see:
https://firebase.google.com/docs/perf-mon/auto_duration-traces-metrics_ios-android#more-detail-trace-samples.

2. D/FirebasePerformance: onResume(): XXXXX: 638220 microseconds

We print the time it took for an activity to become visible, which is also for debugging purposes.

For the rest of the logs, assigning to RC to take a look

I/FirebaseRemoteConfig: Fetch succeeded! Most Remote Config developers are generally interested in whether their Fetches are successful or not. As such, I'd consider this WAI. Firebase Performance uses Remote Config under the hood, so you'll get the Remote Config SDK info logs as part of the package.

W/FirebaseRemoteConfig: No value of type 'Boolean' exists for parameter key 'XXXXX'. is a warning that appears because of how Firebase Performance uses the Remote Config SDK. I'm going to assign this back to @ramanpreetSinghKhinda to see if his team can modify the way they call Remote Config to reduce those non-user relevant warnings.

The fix has been submitted for stopping Firebase Performance logging by default. (To enable debug logging, follow document here https://firebase.google.com/docs/perf-mon/get-started-android#debug_your_integration)

Expect it to be available in upcoming Firebase Performance release (around mid January, 2020).

New Performance Monitoring version is released: https://firebase.google.com/support/release-notes/android#performance_v19-0-5.