Thread: [Venom] Log Panel

Results 1 to 9 of 9
  1. #1 [Venom] Log Panel 
    Registered Member
    Join Date
    Nov 2014
    Posts
    85
    Thanks given
    10
    Thanks received
    30
    Rep Power
    26
    Decided to do server logging in a different way!
    Any feedback is welcome!

    Latest Update: 06/02/2019

    Spoiler for Updates:

    06/02/2019

    - New member in the team (Zac)
    - Design mobile application (started)
    - Simple implementation of networking (Client / Server communication)


    Spoiler for Mobile Application:





    Spoiler for (PC) Application:






    Credits
    Me (Nerik) / Zac
    Reply With Quote  
     

  2. Thankful user:


  3. #2  
    Developer

    Corey's Avatar
    Join Date
    Feb 2012
    Posts
    1,071
    Thanks given
    793
    Thanks received
    693
    Rep Power
    2798
    Would do this via a web panel instead but gj either way


    Reply With Quote  
     

  4. #3  
    Skotos OS Founder #1 OSRS

    Mantvis's Avatar
    Join Date
    Jan 2017
    Age
    19
    Posts
    527
    Thanks given
    52
    Thanks received
    82
    Rep Power
    84
    not bad gl
    Reply With Quote  
     

  5. #4  
    Registered Member
    Join Date
    Nov 2014
    Posts
    85
    Thanks given
    10
    Thanks received
    30
    Rep Power
    26
    Quote Originally Posted by Corey View Post
    Would do this via a web panel instead but gj either way
    Thanks! and just decided to give a little twist by not doing it through a web panel.

    Quote Originally Posted by Mantvis View Post
    not bad gl
    Thank you!
    Reply With Quote  
     

  6. #5  
    Registered Member

    Join Date
    Oct 2017
    Age
    18
    Posts
    150
    Thanks given
    144
    Thanks received
    52
    Rep Power
    132
    gj
    end me
    Reply With Quote  
     

  7. #6  
    of the House Targaryen

    Khaleesi's Avatar
    Join Date
    Jul 2015
    Posts
    744
    Thanks given
    155
    Thanks received
    358
    Rep Power
    255
    Why? Looks like you're pulling from SQL / db.... please don't store logs there. Something like an ELK stack would serve your purpose and be a lot more flexible / multi-purpose.
    Reply With Quote  
     

  8. Thankful user:


  9. #7  
    Registered Member
    Join Date
    Nov 2014
    Posts
    85
    Thanks given
    10
    Thanks received
    30
    Rep Power
    26
    Quote Originally Posted by Khaleesi View Post
    Why? Looks like you're pulling from SQL / db.... please don't store logs there. Something like an ELK stack would serve your purpose and be a lot more flexible / multi-purpose.
    Why shouldn't i be doing it this way?
    Btw Appreciate the feedback.
    Reply With Quote  
     

  10. #8  
    of the House Targaryen

    Khaleesi's Avatar
    Join Date
    Jul 2015
    Posts
    744
    Thanks given
    155
    Thanks received
    358
    Rep Power
    255
    Quote Originally Posted by harryl View Post
    Why shouldn't i be doing it this way?
    Btw Appreciate the feedback.
    A single table with a log per row isn't scalable for one. Also what happens in your application/server if the DB goes down? You want the asynchronicity of dumping your logs to stdout or a file and having the shipping handled for you. Plus you should be doing something with the rest of your logs, not just the specific interactions you decide to explicitly store in sql. Ship them all to your ELK stack, and then you can query for whatever the hell you want.

    This goes for all services that you're deploying. Ship logs from your web store, game server, login server, etc. Then you can debug across the stack. (e.g. request comes in through web store for user:john, see user:john logs in, exception in server for user:john because of $x.) You can see this entire cross-cutting timeline just by querying 'user:john' in kibana
    Reply With Quote  
     

  11. Thankful user:


  12. #9  
    Registered Member
    Join Date
    Nov 2014
    Posts
    85
    Thanks given
    10
    Thanks received
    30
    Rep Power
    26
    Quote Originally Posted by Khaleesi View Post
    A single table with a log per row isn't scalable for one. Also what happens in your application/server if the DB goes down? You want the asynchronicity of dumping your logs to stdout or a file and having the shipping handled for you. Plus you should be doing something with the rest of your logs, not just the specific interactions you decide to explicitly store in sql. Ship them all to your ELK stack, and then you can query for whatever the hell you want.

    This goes for all services that you're deploying. Ship logs from your web store, game server, login server, etc. Then you can debug across the stack. (e.g. request comes in through web store for user:john, see user:john logs in, exception in server for user:john because of $x.) You can see this entire cross-cutting timeline just by querying 'user:john' in kibana
    My logs aren't loaded from a single table and for the the question when the server goes down, the log system is fully independent from the server, so when the server goes down it won't have any effect on the application and i am also currently looking at the second part what u have suggested me and ill try to adjust my application on it. Thanks again for your feedback and sorry for the late reply

    Updated Thread
    Reply With Quote  
     


Thread Information
Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Fixing Log In\Out Problem
    By _Fear in forum Tutorials
    Replies: 11
    Last Post: 04-14-2010, 10:35 PM
  2. log in spawn
    By Ghetto Beef in forum Tutorials
    Replies: 1
    Last Post: 07-31-2007, 01:50 AM
  3. Trades log files.
    By Simox in forum Tutorials
    Replies: 2
    Last Post: 07-24-2007, 10:11 PM
  4. Starter Command (with logs)
    By Systəx in forum Tutorials
    Replies: 11
    Last Post: 07-23-2007, 08:57 PM
Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •