tibistibi / mtor Goto Github PK

this will make it more clear were to use what message.

when a project has a warning message. it will go into warning status. but when the warning is resolved it should not look at that message again.

to achieve this projects should have a base timestamp. only messages from this base and later will be used to set the project status.

see #51

the mTor client should send messages from all methods annotated with the mTorMessage annotation.

instead of adding each heartbeat message it should update the heartbeat message making sure it will only be one message

this will avoid large db and slow app

a user should not need all the default fields. a login which is the email address, a role and a name should be all

now he only gets project which he is member of but he should see all off them

there are menu items visible for company List project list and messages list which should not be vsible before the user is logged in

heart beat is a common used name for this

each project can have a list of users which belong to the project. a user can have a list of projects which he can see.

debug the found memory and the threshold

messages should be resolved on a project basis

messages should be send from plugins and can use the messageServerClient to send the messages

each project should have information about the message interval. ie when messages take longer than the interval to arrive mTor will assume the project is in ERROR state when there is no message send within the timeframe

the interval will be in seconds

There should be an annotation to annotate methods which will return messages to send to mTor

for the client part there should be a default timer which will send a default messages every 5 minutes.

in the config file the base package is provided. at this moment this can be only one base package. but should be multiple.

when logged in as admin, i can not add projects to a user.

now the admin can;t see the companies. not in the company overview page and not when creating a new project. the company list is empty

when i select 1 user it is sometimes not added and the other users are not removed from the selection

when an error or warning message arrives at mTor it should send mails to the users which belong to the project and have the right level (either warning and up or error only)

only an admin can assign projects to a user

when changing the email address in the profile page. the username (login) gets updated. the password fields have to be set as well to regenerate the password hash.

new matching is done on the text which will lead to bugs when some othere message will have the same text.

when running mvn site and checking the checkstyle issues there are more then 300

when creating the user the login should be an email address

there should be a default free memory provider. which will send warning message or error message to mTor when the memory is below a threshold.

see #51

when openeing the http://localhost:8080/messages page there are messages on top of the page which should be removed.

the field will be statusThreshold and in db STATUS_THRESHOLD

the user was simplified, the fields removed should be removed from the signup page

the alert level shoudl be either INFO, WARN, ERROR or none. so the user will receive messages on or above its level. ie a user with INFO will get messages with INFO, WARN and ERROR etc...

the work can be done more efficiently when done in the db instead of in java

the default appfuse names should be replace with either the project mTor my company Bhit.

after signing in the user should not be a full member. it should get the role signed up.

an admin can make him a user with the user role.

(otherwise every one can signup and start using the tool)

in the action there is code to make a list distinct (converting it to set and back to list)
this code should be in the dao with a clear mehtod name searchDistinct

The timer is configed from the applicationContext-timer.xml which is a default schedule.
A project using the mTor should be able to changes this time from a config file or method

there should be a default bhit look and feel.

these are:

dark green - #35847B
light green - #9CC39D
beige - #D4CDA9
light red - #B73A33
dark red - #8F241E

see #51

users should not see project which the do not own

a boolean monitoring could be added so when false it will not send any messages for this project

there should be a default i'm alive message provider which will just send an info message that the application is alive. mTor can use this message to make sure the app is still alive.

when the heartbeat message is not arrived within twice the hearbeat frequency of a project mTor should send out an error email

when a message is added to the db it should have a timestamp

there is a spring wireing error