Challenge Overview
In a previous challenge, we created a log parser for our customer, Barton, to parse log data into a MongoDB. Now that Barton has collected some data, they would like to have an easy to use interface to aggregate and view the log data.
Design and build a UI for a log reporting engine. This interface should include the following elements:
The UI will get data from a MongoDB. This DB has already been filled with appropriate data for you to use. The connection details are in the forum. The DB has the following collection layout:
Design and build a UI for a log reporting engine. This interface should include the following elements:
- Must run on Microsoft Azure platform
- Time Period selection mechanism: This would allow a user to select time period increments last 24h, 12h, 6h, 1h. The mechanism should default to 24h
- Area for application data
- Area will have the name of the application as well as its environment (provided by configuration) selectable
- Each instance of the application will list all the errors found in the logs, grouped and counted by error. (For now, we are only looking at entries of type “Error”)
- The user should be able to drill down and see the individual errors inside the aggregation
The UI will get data from a MongoDB. This DB has already been filled with appropriate data for you to use. The connection details are in the forum. The DB has the following collection layout:
- Configurations: Contain the unique ID for each application instance
- LogEntries: The raw log entries
- Stats: Aggregated data from the LogEntries collection
Final Submission Guidelines
- Please submit a single zip file
- Provide documentation, (usage and deployment guide if needed ) for your solution in the main readme.md.
- Provide a quick < 5-minute video of your solution in action. (You may annotate or narrate)
- A code walkthrough video is desired but not required.
- Provide documentation, (usage and deployment guide if needed ) for your solution in the main readme.md.
- Provide a quick < 5-minute video of your solution in action. (You may annotate or narrate)
- A code walkthrough video is desired but not required.