Update Notes:
Plans For Future: Due to the addition of the Audit log to Discord, details of this can be found here: https://blog.discordapp.com/5-3-17-change-log-a9239d5321dd The need for event logs are now minimally required. Although this still offers some uses that the audit log does not currently cover, the use is still reasonably minimal. We are now looking to cover alternate uses. This has yet to be decided whether or not Power BI will still be implemented into this project. Instead we are now looking into the use of ASP.NET web applications to take over the inter-activeness of Power BI. Potential alternative uses for this project may involve:
0 Comments
Update Notes:
Discord API Overview
C# APIThe C# API was collecting from a variety of sources, - UserJoined, UserLeft, UserUpdate. - RoleCreated, RoleDeleted, RoleUpdated - ChannelCreated, ChannelDeleted - ServerUpdated These events were designed to monitor the changes and maintain the overall live statistics of the discord server. SQL ServerSQL - The SQL Database has been structured as a Relational Database. I have created individual tables to match the various elements within Discord, eg. tblUsers, tblRoles, tblServers. These elements have all been related back to the primary table (tblServers). This made the most sense as the server contains all the information. Please see below the initial out come of the Discord API into Power BI. Power BI DashboardPower BI - With this being a new release the Dashboard has been modelled reasonably simply. The aim is to evolve the Dashboard as the API and Database evolve.
The Dashboard is aiming to allow the user to view their server information, view what has happened and filter events to navigate and monitor their server more easily. |