angular / angular/angularfire

Performance traces are not being reported to firebase anymore

Open
#3,282 9 comments 0 reactions 0 assignees View on GitHub
comp: performance needs: recheck type: bug version: current (v17+)
Dominant language
TypeScript
Stars
7.8k
Forks
2.2k
Avg merge
22h 28m
Merged PRs (30d)
6

Description

### Version info

**Angular:**14.2.4

**Firebase:**9.10.0

**AngularFire:**7.4.1

### How to reproduce these conditions
```
...
imports: [
provideFirebaseApp(() => initializeApp(environment.firebase)),
providePerformance(() => (environment.production ? getPerformance() : undefined)),
]
```

Note that the environment is in fact production, I've verified it, so the `getPerformance()` should be evaluated.

### Debug output

** Screenshots **
![image](https://user-images.githubusercontent.com/22910115/197647332-f196407b-bf48-467b-82e2-c9832c594afe.png)

### Expected behavior

AngularFire Performance reporting performance data to Firebase.

### Actual behavior

Not even network requests to `firebaselogging.googleapis.com` are happening. I've received data only between 11 and 20 of October. The relevant code did not change, so I have no clue why trace reporting stopped after the 20th.

Contributor guide

Open the contributing guide

Research direction

Start with the AngularFire `providePerformance` integration and the `getPerformance()` call shown in the reproduction, using the listed Angular, Firebase, and AngularFire versions. Reproduce in a production environment and inspect whether requests reach `firebaselogging.googleapis.com`; done means performance traces are reported to Firebase again.

Written by the indexing model from the issue text.

Assessment

Tech stack
firebase, typescript
Domain
observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.