Ticketeer | Devpost

Inspiration

One huge inspiration that actually recently came up was how mesmerized we were over the complexity of not only HPC, but the Data Centers themselves. One thing in particular is when we found out how much data was actually being piped through the servers to compute high-level data volumes. After we recognized that data technicians are always under (subtle) pressure not to mess up. This project is geared to give technicians a piece of mind when doing their work in Data Centers, where a lot of things can go wrong.

What it does

Ticketeer monitors all the "tickets" that come in from Engineers who work directly with users/clients. The engineers will load tickets into the application based on their severity(priority), the description of the issue, and who identified it (in this case, the engineers)

How we built it

We built the website using React and Vite for our front-end dashboard. From there, the website hits the API that we built in Flask and Python to act like a broker between the website and the database we used. Speaking of which, we used AWS RDS as our database, with Postgres being our provider.

Challenges we ran into

We ran into so many challenges, it's actually funny. Originally, the big challenge that we faced was that our project scope was too shallow. So we had to upscale it to fit the true markers of solving problems for tech. Some software-related problems that came up were the "ML problem," where we didn't know how we were going to get data that was computable, along with the computing resources to make accurate predictions without overusing our resources. Another problem came with the API routing problem, where we had to migrate our back end onto the cloud so that it could get direct access to the database, while the front end sat locally. Making that bridge was quite the complex problem we had never run into.

Accomplishments that we're proud of

We spent more time actually talking about how we want to design the product than building the product, and that actually led to a more efficient time in building our application. We finally got to use AWS and make full use of their EC2 and RDS instances for our project, which was one of our longtime dreams. And after putting it off for so long, we finally tackled the dreaded fear of making a front-end product that actually looks somewhat solid.

What's next for Ticketeer

We had a ton of ideas that we weren't able to implement for our project simply because the complexity of each component that we made was quite the struggle to get over the line with, so with this it not only gave us a alot of improvabilty in things we haven't implemented, it also has given us room for improvabilty on things we HAVE implemented, which we find a key factor in making a application successful.