Rank 2: Process
Hello 👋, when this will be fixed on Appwrite Sites? It's draining our quotas for Sentry, it must be a problem with the default logger which is always on for Appwrite Sites and cannot be turned off.
Votes
0
Replies
5
Participants
3
Messages
6
Rank 2: Process
Hello 👋, when this will be fixed on Appwrite Sites? It's draining our quotas for Sentry, it must be a problem with the default logger which is always on for Appwrite Sites and cannot be turned off.
Rank 2: Process
Rank 3: Container
// ESMimport {parse, stringify, toJSON, fromJSON} from 'flatted';
// CJSconst {parse, stringify, toJSON, fromJSON} = require('flatted');
const a = [{}];a[0].a = a;a.push(a);
stringify(a); // [["1","0"],{"a":"0"}]not sure why logging isnt being disabled. and yes we should handle circular jsons too here, cc @Meldiron
Heyy 👋
Right now, disabled logging only disables trackng console.log and console.error. Network logs are still created, so you see them in "Logs" tab.
Ill talk to Chen about possible re-wording to make this clearer. Is it troubling for you to see request logs - if so, what's the benefit from disabling it?
Rank 3: Container
Hey 👋@Meldiron, currently the access log is using the same code logic and throwing Circular JSON exceptions, that drained our Quota drastically.
There should be an option to disable access log for cases when other apps are already logging it to prevent data duplication. It must be separated from error and warning logs, i.e: 2 checkboxes
Definitely fix the Circular JSON exceptions as soon as possible. (Disable access logging can temporarily resolve our issue where we don't need the access logging and might be faster to implement (if condition), but it is not fixing the issue with Circular JSON exceptions for other developers).