Firebase experiments count limit - firebase

Currently in firebase console for my project I have 2 remote config experiments(running), 4 notification experiments(running), 3 remote config experiments drafts and 0 completed experiments. When i am pressing to start one more remote config experiment, firebase console syas "Error starting experiment: Too many running experiments".
What is the limit of firebase experiments (remote config/notification) that can be active?

From the Firebase documentation for Create Firebase Remote Config Experiments with A/B Testing:
To start your experiment, click Start Experiment. You can run up to 24 experiments per project at a time.

Firebase supports now up to 24 simultaneous experiments
reference link:
firebase documentation

Related

Get rid of annoying logs by Firebase function "this may be a production service" & "External network resource requested"

When running a Firebase function, my logs are very noisy mostly because of those 2 messages
Be careful, this may be a production service.
⚠ External network resource requested!
I know I am running a production service, and yes I am requesting an external ressource 😅 can I disable them?
Thanks
Normally using --quiet would silence this message, however because there are so many emulators, the Firebase team couldn't reach a consensus on whether to allow this to be silenced when used with firebase emulators:start (see firebase-tools Issue #2859).
The official stance on this is to set the logs filter to only show "user" logs using the Emulator Suite UI's Logs Viewer and let the regular log feed log everything.

See Firebase Test Lab Usage

Normally, you can see under "Usage and billing" the usage of all Firebase Services. We have integrated integration test with Firebase Test Lab into our CI. Now I want to know how much usage we use and when do we need to pay for our usage.
Is there any view in Firebase or Google Cloud Platform to the use Firebase Test Lab usage of the current project?
It appears you are currently using the Firebase Spark free tier? On that plan you may run tests on 10 virtual devices and 5 physical devices each day.
If you're using the Blaze pay-as-you-go plan, you can see Test Lab device usage in the Cloud Console. Start at https://console.cloud.google.com/billing and select your project and billing plan. From there you can view usage graphs and generate billing reports.

Firebase: Budget and Daily Spending Limit

I've set a daily spending limit for my Firebase project.
Inside the same project, I added a NodeJS App Engine app.
So I've received this warning:
In that case, all spending limits are ignored?
If Firebase goes to $99999 it won't be stopped?
Thanks..
The warning you receives reflects reality, if your app is deployed in the App Engine Flexible environment. To avoid $99999 surprises, you can create a budget for a GCP project to protect somehow your bill and monitor all of your Google Cloud Platform charges from one place. To see how you create a budget, you may have a look at the "Managing GCP Projects, App Engine Applications, and Billing" documentation page.

Firebase Remote Config & A/B Testing with real time updates

I've implemented real time remote config updates via the documentation here.
In general, it works as expected, except when it comes to experiments via A/B Testing. Changes to A/B Testing that affect remote config do not fire the update cloud function hook.
Does anyone know if its possible to have the functions.remoteConfig.onUpdate cloud function hook trigger when a change to remote config is made via an A/B Testing experiment change?
The only workaround I can think of is to have a dummy value in remote config itself that I change whenever an experiment is created/updated.
firebaser here
There is nothing built into Remote Config for that at the moment. But thanks to the integration between Cloud Functions and Remote Config, you can build it yourself.
One of our engineers actually just gave a demo for this last week. I recommend you check it out here: https://youtu.be/lIzQJC21uus?t=3351.
In this demo, there are a few steps:
You publish a change from the Remote Config console.
This change triggers Cloud Functions through a functions.remoteConfig.onUpdate event.
The Cloud Function sends an FCM message to all apps through a topic.
When an app receives this message, it shows a prompt that the configuration is out of date.
When the user clicks the "fetch" button, the app fetches the new configuration data from Remote Config.

Stackdriver logs not available for Cloud ML jobs since migration to V2

Since migration to V2 logs from Cloud ML jobs are not accessible on the Stackdriver logging console anymore. The last log displayed is
Waiting for Tensorflow to start.
The job is executed and completed successfully, I just can't access outputs in the logs
All Stackdriver APIs are enabled for the project.
There are no known issues with Cloud ML's Stackdriver logging. The fact that you see "Waiting for Tensorflow to start." indicates you are seeing log messages from Cloud ML.
If logs from your Python/TensorFlow program are missing that usually indicates Cloud ML hasn't been authorized to send logs to Stackdriver logging for your project. To check permissions do the following
Identify the Cloud ML service account by following these instructions
In the Cloud Console select the IAM Tab
Verify that the Cloud ML service account is listed and has Logs Writer permissions
This problem also took me two weeks to search answers online with frustration, until I came across this post. I did not see "migration to V2" as OP mentions but I simply could not get any application logs in StackDriver, only system logs of job started/completed. Following what Jeremy replies solves the problem.
To make Jeremy's reply simpler to follow, essentially you add the ML service account
cloud-ml-service#<project-id>.iam.gserviceaccount.com
to your project's IAM members, with at least "Logs Writer" role.
You can get "project-id" by:
gcloud config list project --format "value(core.project)"
I also assigned Project->Editor role to allow Bucket access.

Resources