• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Missing log output
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Missing log output


  • Subject: Re: Missing log output
  • From: Alex Zavatone via Cocoa-dev <email@hidden>
  • Date: Thu, 12 Nov 2020 12:37:05 -0600

Gabe, let me share the decisions and solutions I went over in my attempting to
solve this on iOS.

In my first logging, all that I wanted was to be able to get the NSLogs out of
a file that ONLY had the logs from my app.  I sent you the code for that.

In another app, there were 3 sets of transactions that I cared about.  To keep
the issues relevent, I logged to 3 separate files and then could transfer each
as needed.

Some people hate this.  For me, I put a timestamp on each log event and it
helped me because I could instantly pay attention to ONLY the info that I
wanted to pay attention to by opening the file for the issues I cared about.

A concern was that “the file could get too big.”  So, I arbitrarily limited
each file to 10,000 lines of text when writing to them, trimming the oldest
line if the file length was > 10,000 lines.

Securlty.  Would the files need to be encrypted?  To get around this, I just
made sure not to log any PII and used a lookup to get any special info.

Just some background info on the thought process that was behind several of the
logging that I put in place over the years.

Cheers.
Alex Zavatone

> On Nov 9, 2020, at 3:23 PM, Gabriel Zachmann via Cocoa-dev
> <email@hidden> wrote:
>
>
>> At any rate, it's good to plan ahead and use a different logging mechanism,
>> one without all the complications and unknowns of the system log.
>
> Yes, I agree.
>
> I was thinking of implementing a way such that users can just click on kind
> of a "Send Log" button, and my app would filter out all the log info from,
> err ..., the system log
> and send it as an attachment with an email to me.
>
> Would there be an easy / fail-safe way to filter out all the lines in the
> system log that pertain to my app?
>
> Best regards, Gabriel
>
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Missing log output
      • From: Gabriel Zachmann via Cocoa-dev <email@hidden>
References: 
 >Re: Missing log output (From: Gabriel Zachmann via Cocoa-dev <email@hidden>)

  • Prev by Date: Re: How can I get horizontal scrollbars adequate to the widest list entry
  • Next by Date: Re: Missing log output
  • Previous by thread: Re: Missing log output
  • Next by thread: Re: Missing log output
  • Index(es):
    • Date
    • Thread