Logs in frontend apps

#discuss

I was having a discussion with my team and wanted to have everyone thoughts on how they configured logging in their frontend apps.

I happen to just reset console.log to an empty function on production builds but leave the warn and error in place.

But, is there any use of having logs enabled on production at all?

Top comments (5)

Basit Ali Mundia • Jun 8 '18

For frontend, specially when talking to an API, I feel there are several other things to keep in mind. For e.g. API failure (due to network issues and maybe session expiring) is not necessarily an issue with the app and does not need to be logged.

Meghan (she/her) • Jun 8 '18 • Edited

I'm not from them, but have you seen one of this month's sponsors, Timber? They specialize in logging and may be worth a look.

Basit Ali Mundia • Jun 9 '18

A quick glance at their page feels like they focus on the backend logging which is the whole point of the discussion.

Unlike backend and unless you push the logs to a server, logs in the frontend app makes no sense at all.
Frontend failures can be caused by factors outside of the app ranging from networks/firewall issues, content blockers or even malwares in the clients machine. How do you effectively log errors in such cases?

Dávid Szabó • Jun 8 '18

Have you thought about pushing error logs to a server on production?

Basit Ali Mundia • Jun 8 '18

Yep, that's definitely the next step. But the first part is silencing the logs I already have. And then, filtering logs that are worth pushing to server.

DEV Community

Logs in frontend apps

Top comments (5)

Read next

Query DynamoDB with SQL using Athena - Leveraging DynamoDB Exports to S3 (1/2)

What is Ambient Computing and How It Will Transform Our Interaction with Technology

Here’s how Lobechat applies typesafety to its environment variables in Next app

Docker + MariaDB 에서 ERROR: (conn:4, no: 45009, SQLState: 08S01) socket has unexpectedly been closed