Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Session data not available on console for custom code traces #10799

Closed
jbatra-umeey opened this issue Feb 9, 2023 · 2 comments
Closed

Session data not available on console for custom code traces #10799

jbatra-umeey opened this issue Feb 9, 2023 · 2 comments

Comments

@jbatra-umeey
Copy link

jbatra-umeey commented Feb 9, 2023

Description

There are no session data details available for custom log

Reproducing the issue

Add a custom code trace like the one below :

FIRTrace *traceObject = [[FIRPerformance sharedInstance] traceWithName:@"testing_code_trace"];
[traceObject start];
  • Run the code to send a trace multiple times

  • Go to firebase console -> Performance tab -> custom traces

Expected Output : You should be able to view testing_code_trace log with session data

Actual Output : There is no session data available for the log

Firebase SDK Version

Firebase/Performance (8.1.0):

Xcode Version

8.1.0

Installation Method

CocoaPods

Firebase Product(s)

Performance

Targeted Platforms

iOS

Relevant Log Output

2023-02-09 13:09:25.345385+0530 PS Express[631:39269] 8.1.0 - [Firebase/Performance][I-PRF100009] Logging trace metric - CollageMainViewController_applyLayoutUsingState:checkExisting:isAsync: 7.5000ms. In a minute, visit the Firebase console to view your data: https://console.firebase.google.com/project/api-project-1062112142483/performance/app/ios:com.xxx.PSMobile/metrics/trace/DURATION_TRACE/CollageMainViewController_applyLayoutUsingState:checkExisting:isAsync:?utm_source=perf-ios-sdk&utm_medium=ios-ide

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet
Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet
- Firebase/Analytics (8.1.0):
    - Firebase/Core
  - Firebase/Core (8.1.0):
    - Firebase/CoreOnly
    - FirebaseAnalytics (~> 8.1.0)
  - Firebase/CoreOnly (8.1.0):
    - FirebaseCore (= 8.1.0)
  - Firebase/Crashlytics (8.1.0):
    - Firebase/CoreOnly
    - FirebaseCrashlytics (~> 8.1.0)
  - Firebase/Performance (8.1.0):
    - Firebase/CoreOnly
    - FirebasePerformance (~> 8.1.0)
  - FirebaseABTesting (8.15.0):
    - FirebaseCore (~> 8.0)
  - FirebaseAnalytics (8.1.1):
    - FirebaseAnalytics/AdIdSupport (= 8.1.1)
    - FirebaseCore (~> 8.0)
    - FirebaseInstallations (~> 8.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.4)
    - GoogleUtilities/MethodSwizzler (~> 7.4)
    - GoogleUtilities/Network (~> 7.4)
    - "GoogleUtilities/NSData+zlib (~> 7.4)"
    - nanopb (~> 2.30908.0)
  - FirebaseAnalytics/AdIdSupport (8.1.1):
    - FirebaseAnalytics/Base (= 8.1.1)
    - FirebaseCore (~> 8.0)
    - FirebaseInstallations (~> 8.0)
    - GoogleAppMeasurement (= 8.1.1)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.4)
    - GoogleUtilities/MethodSwizzler (~> 7.4)
    - GoogleUtilities/Network (~> 7.4)
    - "GoogleUtilities/NSData+zlib (~> 7.4)"
    - nanopb (~> 2.30908.0)
  - FirebaseAnalytics/Base (8.1.1):
    - FirebaseCore (~> 8.0)
    - FirebaseInstallations (~> 8.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.4)
    - GoogleUtilities/MethodSwizzler (~> 7.4)
    - GoogleUtilities/Network (~> 7.4)
    - "GoogleUtilities/NSData+zlib (~> 7.4)"
    - nanopb (~> 2.30908.0)
  - FirebaseCore (8.1.0):
    - FirebaseCoreDiagnostics (~> 8.0)
    - GoogleUtilities/Environment (~> 7.4)
    - GoogleUtilities/Logger (~> 7.4)
  - FirebaseCoreDiagnostics (8.13.0):
    - GoogleDataTransport (~> 9.1)
    - GoogleUtilities/Environment (~> 7.7)
    - GoogleUtilities/Logger (~> 7.7)
    - nanopb (~> 2.30908.0)
  - FirebaseCrashlytics (8.1.0):
    - FirebaseCore (~> 8.0)
    - FirebaseInstallations (~> 8.0)
    - GoogleDataTransport (~> 9.0)
    - nanopb (~> 2.30908.0)
    - PromisesObjC (~> 1.2)
  - FirebaseInstallations (8.13.0):
    - FirebaseCore (~> 8.0)
    - GoogleUtilities/Environment (~> 7.7)
    - GoogleUtilities/UserDefaults (~> 7.7)
    - PromisesObjC (< 3.0, >= 1.2)
  - FirebasePerformance (8.1.0):
    - FirebaseCore (~> 8.0)
    - FirebaseInstallations (~> 8.0)
    - FirebaseRemoteConfig (~> 8.0)
    - GoogleDataTransport (~> 9.0)
    - GoogleUtilities/Environment (~> 7.4)
    - GoogleUtilities/ISASwizzler (~> 7.4)
    - GoogleUtilities/MethodSwizzler (~> 7.4)
    - Protobuf (~> 3.15)
  - FirebaseRemoteConfig (8.15.0):
    - FirebaseABTesting (~> 8.0)
    - FirebaseCore (~> 8.0)
    - FirebaseInstallations (~> 8.0)
    - GoogleUtilities/Environment (~> 7.7)
    - "GoogleUtilities/NSData+zlib (~> 7.7)"
@google-oss-bot
Copy link

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@rizafran
Copy link
Contributor

rizafran commented Feb 9, 2023

Hello @jbatra-umeey, I suspect that your session data is less than 1%. Note that the default sampling rate for sessions is 1%, therefore, to have a single visible session, your app needs to generate at least 100 sessions. After generating enough sessions, the random sampling of these user sessions will be displayed in the console.

I'll now be closing this ticket, but feel free to comment if the issue persists or if you have questions.

@rizafran rizafran closed this as completed Feb 9, 2023
@firebase firebase locked and limited conversation to collaborators Mar 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants