GithubHelp home page GithubHelp logo

jakobhviid / dashboard-interface-docker Goto Github PK

View Code? Open in Web Editor NEW
0.0 0.0 0.0 3.74 MB

License: MIT License

Dockerfile 1.38% C# 37.13% HTML 0.71% TypeScript 46.18% JavaScript 11.12% Shell 3.48%

dashboard-interface-docker's People

Contributors

dstoft avatar omvk97 avatar

Watchers

 avatar  avatar  avatar

dashboard-interface-docker's Issues

Notifications from SocketServer

At the moment a simple proof of concept notification design has been implemented.

In the future it should be the SocketServer which sends notifications to the UI.

These notifications is healthcheck, performance, uptime alerts described in other issues.

Load Templates from file

The user should be able to create their own templates for creating new containers. The container should read a file which the user can provide through volumes

Json Web Token too old

If the JWT is too old the SignalR package will throw an unauthorized error. This has to be caught and then the user should log in again.

Multiple docker image architecture support

Due to ASP.Net Core runtime requiring a different installation when running on different architectures, then a single Dockerfile cannot be used to support multiple architectures. Therefore, for each architecture that has to be supported, the following has to be implemented:

  • Dockerfile, which uses a different ASP.Net Core runtime installation.
  • Github action, which uses the new Dockerfile
  • Dockerhub tag, the Github action will push to a new tag, because it is not possible to build multiple images using different Dockerfiles and then push them to the same docker image tag.

I am removing the current multiple architectures from the Github action now, and then the image will only support amd64 for now.
The dockerhub repository: https://hub.docker.com/_/microsoft-dotnet-aspnet contains information about how a dockerfile should look when using other architectures.

SSH into server

With Dashboard-Interface it should be possible to ssh into a server and run a script which installs docker and dashboard-server-docker. When this is installed everything else should be controllable from the interface

FIX Container request hanging

Often when sending a request to a container it will be done, but the UI does not recieve a response from Dashboard-Server. This makes the UI loader hang

Email alerts

Once alerts are properly implemented the user should be able to choose which types of alerts should be sent to their email as well.

UI Redesign

Container Overview and Container Stats should be rewritten so that multiple containers can be selected and commands can be sent to all of them at the same time.

Create Container should also have some UI redesign. Environment variables should be in a table so that it's possible to delete environment variables in the middle of the list

Fetch historical data from Database

Dashboard-Server-Docker stores historical data in a database. This data needs to be displayed in the form of graphs (e.g. amount of crashes pr. day on a server), percentages (e.g. uptime for a server)

Monitoring

  • Status overview as a page

  • High CPU / Memory usage over a time period alert

  • Is about to run out of disk alert

  • Unhealthy Containers

  • Total ressource usage for host

Inspect Container

Send request to Dashboard-Server and recieve the equivelant of docker inspect <container_id> and display to user

Manual Stats Data Refetch

Like on overview page where it's possible to manually refetch container data it should be possible to refetch stats data

Container logs command

Send request to Dashboard-Server and recieve the equivelant of docker logs <container_id> and display to user

Compile Warnings

When the interface project is built it throws quite a few warnings, nothing severe, but it should be fixed at some point.

License

Link to license in this repo

Local development

It has to be easier to develop this code locally, without running this repository in a docker container and rebuilding it whenever a change has happened.
The stages provided by CFEI should be used as the Kafka and Zookeeper instances that are used to communicate.

Kafka Monitoring

Kafka has JMX Metrics. Dashboard-Interface should have an interface which displays the most important information such as topics, who is writing to these topics.

With these metrics it could be nice if the interface could detect abnormal writes and alert the user

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.