Firebase Log Monitoring with LogMonitor

>_ why firebase apps need log monitoring

Firebase Cloud Functions logs are buried in the Google Cloud Console, which is slow to navigate and difficult to search. For Flutter+Firebase apps, client-side logs are invisible unless you set up explicit logging. LogMonitor gives you a single Live Console that streams logs from both your Cloud Functions and your client-side Firebase app.

>_ how logmonitor works with firebase

For Cloud Functions, install the logmonitor-js SDK and call logmonitor.init() in your function entry point. The SDK auto-patches console.log, console.info, console.warn, console.error, and console.debug. For Flutter apps using Firebase, add the logmonitor_flutter SDK. Both stream logs to the same LogMonitor Live Console, giving you end-to-end visibility across your entire Firebase stack. Logs are only sent in production (when process.env.NODE_ENV === 'production').

>_ quick start

const functions = require('firebase-functions');

const { logmonitor } = require('logmonitor-js');

logmonitor.init({ apiKey: 'your-api-key' });

exports.onUserCreated = functions.auth.user().onCreate((user) => {

  console.log('New user created', { uid: user.uid, email: user.email });

  return sendWelcomeEmail(user.email);

});

exports.processOrder = functions.firestore

  .document('orders/{orderId}')

  .onCreate(async (snap, context) => {

    console.log('Order created', { orderId: context.params.orderId, data: snap.data() });

    try { await fulfillOrder(snap.data()); }

    catch (err) { console.error('Order fulfillment failed', { error: err.message }); }

  });

>_ what you can monitor

• $Cloud Function invocation errors and timeouts
• $Firestore trigger and write failures
• $Authentication events and sign-in errors
• $Cloud Messaging delivery issues
• $Client-side Flutter or web app errors
• $Firebase Storage upload and download failures