Must Stop Reading Server Logs

Once the first visitor stopped by, I was delighted! Immediately I went and did a reverse DNS lookup -- first customer, from Atlanta! Hey. I like Atlanta! There are a lot of good restaurants down there. Home of CNN, right? Hey maybe CNN wanted to do a story on my blog!
LOL! No such luck, of course. People trickled in here and there, browsed around and left. Sometimes I could picture myself running a small roadside gift shop. People, as represented by IP numbers, would stop poke around the display cases and leave. Wonder which story they liked the most? Wonder what country of origin had the most referrers? Wonder which page they were most likely to exit on?
Hey. This was a fun game! It was like one of those strategy games where you try to run your numbers up. It was a real hoot, and gave me something to do between posts (and reading /.)
But at some point, the luster went out of the game. Traffic to the sight increased, and it was more than I could do to keep everything straight. Was that .155 guy the same .155 guy that dropped by this morning? Wonder who at Google is taking an interest in my blog? Was this Google browser the same as the one yesterday?
Then, heck, it all went to pot. Soon my visitors were been running in the thousands each day. I guess these are good numbers; I honestly don't have a clue for blog what is good traffic and what is not. What I do know is that with 3 thousand people dropping by your site, it makes your head spin to try to keep track of them all.
Now my eyes are red, I haven't had a good night sleep in several days, and I'm running on Diet Mountain Dew. I got to stop reading those server logs.
Maybe one more refresh, and that's it. Just one more. I can quit anytime I want. Just not right this minute.