Asclepias
Diamond Member
Hey clown. You can only tell me that by reading logs. That is the first step in troubleshooting. This has nothing to do with whitey. This has everything to do with your claim you are a programmer and that troubleshooting is not essential.Retard, I alread explained that I can tell you what Trade was done by what Trader in what function on what Workstation on what Tables and Fields and what date/time.No dummy. You check software as well. You check configuration. You check latency and yes you check hardware.You are one dumb fuck."we'd have someone go diagnose the issue."Sure cupcake...every company worth it's salt has a guy running a script like you posted to find problems.No. Real engineers like me trouble shoot the issue then tell the service provider to fix their shit backed with supporting evidence the problem originates in their system. So take a situation where a voice call on a SIP network does not work correctly. Depending on the symptoms I track the call via error logging from originating device to the sip trunk my gateway connects to with the service provider. In real world conditions no one calls the service provider and tells them something is wrong please fix it. The first thing they will say is it isnt their issue. You have to prove its their issue.
Now let's deal with reality...
Tell me the last time you called a reputable company that couldn't tell you within 2 seconds of getting your phone number what the exact problem was and couldn't fix it almost immediately.
Heck, if a router went out at work we'd know it immediately and if it couldn't be restarted (an extremely rare occurence) we'd have someone go diagnose the issue.
You are obviously dealing with tiny operations.
Thousands of people call AT&T or Verizon when they have a problem and they let you know instantly what the issue is and whether or not it's a software or hardware issue.
Thats what trouble shooting is you moron.
The only time a field person “troubleshoots” is to actually check out hardware.
Tell the CSR at AT&T that they are troubleshooting and they’ll laugh in your ear.
No one writes ad hoc SQL anymore unless they’re working at the local Teamo stand.
The CSR would laugh because they dont know jack shit about trouble shooting. The engineers at level 3 and above do that. The CSRs are always level one.
Sounds like all you do is log errors. The problem is that logging errors only alerts you to a problem. A human troubleshooter tells you why the problem occurred.
But all your brain can process is “Hate Whitey”.