DEV Community

loading...

DevAnalytics at DOHackathon: final steps

Sandor Dargo
Happy father. Principal Engineer. Author. Creator of dailycppinterview.com
・1 min read

This is my last post about DevAnalytics before the submission.

Since the last time, I did what I promised and some more.

What I promised

  • On the backend side I removed logging of the incoming HTTP requests, as they include the DEV API Key that is supposed to be secret. Now even me I don't have access to them, not to mention the unlikely(?) case that my account gets compromised.

This was quite easy to do. I'm using flask on BE side and I just had to add these two lines:

log = logging.getLogger('werkzeug')
log.setLevel(logging.ERROR)
Enter fullscreen mode Exit fullscreen mode
  • I added some error handling on the Frontend side. In case, you enter a wrong API key, or there is some other problem, you get a nice error message:

Error message

Additionally, once you ask for the stats the screen is cleared first.

The extra

I added some more statistics about average numbers.

Averages

What is next?

The submission. I have some more ideas, but I think I'll only implement them after the hackathon.

Thanks for following through and feel free to try DevAnalytics and leave a comment.

Discussion (1)

Collapse
casiimir profile image
casiimir

Woah, cool! Nice done Sandor, I really appreciate it. I tested it with my key and, really impressive, a complete post tracker appear on my window.
👏👏