|
Each function has it's own header - changes, updated, bug-fixes, &etc are all noted in the header along with the date. On the occasion that it's a substantial change, details are included.
Also - the new/modified code is noted with the date of change and noted with a why.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
What does this have to do with logging errors?
Aren't you using source control to manager changes, bugs, etc.? (Git, SVN, something?)
|
|
|
|
|
Logging - essentially keeping a record with some chronology.
So - when there's an error I note it in the location where it was found.
On that basis, I guess I'll send a few ???'s to you w.r.t you question.
If the interpretation is supposed to be logon-attempt errors then it should have been made explicitly clear that it was limited to that scope. Or perhaps I should think like a lumberjack?
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
The question is how do you log errors. In other words, when your code generates an error do you log that error to a file, to a database, etc?
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
And I told you what I did.
Why does it have to be to a separate file or database to count, to you, as an answer?
In-situ is a place where it's relevance is not lost. Relevant history, if any, is contiguous.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
That's not the sort of error logging the survey's asking about.
It's asking when your application encounters an error (eg File Not Found); how is that error recorded/reported/etc at rutime to you so that it can be fixed.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
That's how you read it. File not found doesn't have to be an addressable error at all, but rather, user error. So - that view - as I see it, is altogether wrong.
The Apache error log records every nuance - an no rational human being would really want to go through that for things like file not found.
On the other hand, undefined index, a real error, is also there. That can be fixed. How many copies of that message ought you keep? More than one is ludicrous.
You, and some others, saw a narrow scope in what an error is and what logging it means.
For me, an error log of my code is something I can find useful - not just a huge list of what will surely be redundant complaints by the system.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
W∴ Balboos wrote: On the other hand, undefined index, a real error, is also there. That can be fixed. How many copies of that message ought you keep? More than one is ludicrous.
Not if troubleshooting the cause requires several examples in order to see a pattern, assuming you're logging more detail about the error than just the error number/message/location, or need to see if it only occurred once or several times but only at certain times of the day, etc.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
OK - you check the errors, discern the pattern, fix the problem.
Of what use, now are the individual errors? Instead, an explanation of what was done and why is far more useful - especially if in the vicinity of where the fix was made.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Now that the problem is fixed? Of no use at all. At this point I delete the email or event log and move on. If I'm keeping a journal of errors and fixes, which is what you seem to be calling a log, then I'll also note the problem and fix, and sure, one journal/log entry per problem is sufficient for journaling.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Don't make eye contact. Just back away slowly. No sudden movements.
My plan is to live forever ... so far so good
|
|
|
|
|
You are talking about code changes. The survey is talking about errors that happen when your code is running. You seem to be missing something in translation.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
If you never run the code it never has errors.
The survey asks how one logs errors. So - when an error occurs, it's either a code error, needs to be fixed and logged/documented/tattooed on your foreskin. If, on the other hand, it's a general error (like a user error), logging it will help nothing.
Either it gets prevented (code fix or kill user), or ignored because you cannot outwit stupid.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
It seems I, and a couple of others, do not understand what you are saying in reference to the survey. But I trust it makes sense in your head.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
You say tomato - I say potato.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Exactly!  
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
But it's a cucumber!
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
just for VB developers? On Error Resume Next
|
|
|
|
|
I once knew someone who had this in almost each of his methods as the first line...
|
|
|
|
|
Well, it was easier (vb6) than On Error Goto ErrorHandlerX where you probably would have returned back to the error source anyway. Or course, it should be followed up as quickly as possible with On Error Goto 0. I wouldn't expect to see this in VB.Net though where Try/Catch is available. Are people still using this directive?
"Go forth into the source" - Neal Morse
|
|
|
|
|
Oh yes I am talking about the VB6 time in the 90's.
Since .net I didn't have much contact with visual basic. All companies I worked for since then all switched to C#, so I can't tell whether it is still used today.
|
|
|
|
|
We have multiple schemes, some do it via file logging and some use kafka broker to log and then it can be visualized using Kibana
|
|
|
|
|
You have to track for unusual activities, warning and error in your logs and send email to administrator to investigate. Most companies dun track their logs, that's why many intruders can stay undetected on their servers for many years.
|
|
|
|
|
Quote: Errors? My applications don't produce errors!
Klingon software is always on the offensive; there is no need of logs when your users have been exterminated.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Klingon Programmer — Software Development
Quote: By filing this bug you have questioned my family honour. Prepare to die!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
