memphisx / netcheck-api Goto Github PK

Domain entities should also hold a check_frequency field in db. (to be used later by different schedulers)

• All domain endpoints should properly point to a resource.
• If that resource doesn't exist in db it probably needs to have a separate endpoint that won't conflict with an existing resource.
• All responses should contain links for their selves and any subresources the contains

• Have an optional parameter to filter domains.
• Optional parameter for ASC/DESC order by domain name and created Date

java.net.ConnectException: Connection refused (Connection refused)

The /states endpoint should only return entries that the status of a domain has changed. Instead due to the query checking for both http and https and certificate changes by default if we had a state change for https we will see that as a change to http too

• Add HATEOAS support to the endpoints
• Also use DTOs for data sent between repositories and controllers

• Spring batch writer to send notifications through a service
• Batch writer notification interface
• Init support for one of the services: Pushover, Pushbullet, Slack, Discord etc.
• Config of the notification service will be through properties.yml file at least until v2

GET /{domains}/ should also return the last status for each protocol of each domain along with the domain name

• Response time

• Running tests
• Building jar file
• Build and push docker image

ModelAssemblers should extend RepresentationModelAssemblerSupport

.HttpMessageNotWritableException: Could not write JSON: Conflicting getter definitions for property "dateAdded": om.bompotis.netcheck.api.model.DomainModel#getCheckFrequencyMinutes(

Reuse the previous ProtocolCheck entry and just store the metrics.

Include them in the building/deployment on circleci

• Create additional tables in DB to hold aggregate data for hourly, daily, and monthly average/lowest/highest response times and uptime percentages per domain.
• Create schedulers to calculate and fill the above tables per hour/day/month at the end of each hour, day, month respectively

• Check every x (minutes/hours) for availability/status of domain in db
• Store in db if status has changed

• Change configuration logic of notification handling to be per user and saved in DB.
• Add additional endpoints to create/update configuration.

Add any additional notification services that were not implemented in #63

• Pushover
• Slack
• Discord
• Pushbullet

• Should include hour/day/week/month filter.
• The response should include the worst response time, best response time, and average response time of checks.

• Create scheduler to delete historic checks older than 3 months.

javax.net.ssl.SSLHandshakeException: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed

• Add different schedulers depending on the frequency (mins) set per domain
• Update PUT /domains/{domain} to accept a frequency option in the payload and store it when creating the entity