Analyse monitoring dashboard to improve alerting

Timebox to a meeting, result should be tickets on the backlog

Topic to discuss or to be done:

**Aviation Dashboard**:
API Gateway Logs.
- [x] Make the info in this panel clear/complete.

Lambda's Metrics. 
- [x] Define which info should be logged for the Lambda's Metrics Logs: START, END, Username, REPORT for every time 
Lambdas are called, unmanaged Errors.
- [x] Implement the Lambda's Metrics Logs for Sigmet, Airmet, Taf (correspondent TACs) and Authorizer.
- [x] Rediscuss about the alert for the Lambda Errors (rule, conditions, no-data, Error-handling, message)
- [x] Rediscuss if the notification  should be sent to slack AND/OR mail?

Application Errors & Warnings
- [x] Implement in Aviation BackEnd the logs with ERROR log_level for Sigmet, Sigmet TAC, Airmet, Airmet-TAC, Taf, Taf-TAC, Taf-Placeholder, Authorizer.
- [ ] Implement in Grafana the logs with ERROR log_level for Sigmet, Sigmet TAC, Airmet, Airmet-TAC, Taf, Taf-TAC, **Taf-Placeholder**, Authorizer.
- [ ] Implement in Aviation BackEnd the logs with WARNING log_level for Sigmet, Sigmet TAC, Airmet, Airmet-TAC, Taf, Taf-TAC, Taf-Placeholder, **Authorizer**.
- [ ] Implement in Grafana the logs with WARNING log_level for Sigmet, Sigmet TAC, Airmet, Airmet-TAC, Taf, Taf-TAC, **Taf-Placeholder**, Authorizer.
- [x] Discuss about the alert for the ERRORs (no-data, Error-handling, message)
- [x] Rediscuss if the ERROR notification  should be sent to slack AND/OR mail?
- [x] Discuss about the alert for the WARNINGs (no-data, Error-handling, message)
- [x] Rediscuss if the WARNING notification should be sent to slack AND/OR mail?

Application Info
- [ ] Implement in Aviation BackEnd the logs with INFO log_level for Sigmet, Sigmet TAC, Airmet, Airmet-TAC, Taf, Taf-TAC, Taf-Placeholder, **Authorizer**.
- [ ] Implement in Grafana the logs with INFO log_level for Sigmet, Sigmet TAC, Airmet, Airmet-TAC, Taf, Taf-TAC, **Taf-Placeholder**, Authorizer.
- [x] Discuss what should be reported as string in INFO. (at this moment the logs are very unclear)

Extra stuff:
- [x] Implement in Aviation BackEnd the logs with DEBUG log_level for Sigmet, Sigmet TAC, Airmet, Airmet-TAC, Taf, Taf-TAC, Taf-Placeholder, Authorizer.
- [ ] Discuss what should be reported as string in DEBUG. (at this moment the logs are too long)


**Spaceweather Dashboard**:
API Gateway Logs.
- [x] Make the info in this panel clear/complete.

Incoming data streams:
- [x] Adapting the alert time to the interval of incoming data streams.

Lambda's Metrics. 
- [x] Define which info should be logged for the Lambda's Metrics Logs: START, END, Username, REPORT for every time 
Lambdas are called, unmanaged Errors.

Application Errors & Warnings
- [x] Implement in Spaceweather BackEnd the logs with ERROR log_level for TimeseriesAPI, NotificationAPI, reqM, reqX, reqSw, reqKP, BulletinAPI, Notifications, EventIngest, Update Stream, Authorizer.
- [x] Implement in Grafana the logs with ERROR log_level for TimeseriesAPI, NotificationAPI, reqM, reqX, reqSw, reqKP, BulletinAPI, Notifications, EventIngest, Update Stream, Authorizer.
- [ ] Implement in Spaceweather BackEnd the logs with WARNING log_level for TimeseriesAPI, NotificationAPI, reqM, **reqX**, **reqSw**, **reqKP**, BulletinAPI, Notifications, EventIngest, **Update Stream**, **Authorizer**.
- [x] Implement in Grafana the logs with WARNING log_level for TimeseriesAPI, NotificationAPI, reqM, reqX, reqSw, reqKP, BulletinAPI, Notifications, EventIngest, Update Stream, Authorizer.
- [x] Discuss about the alert for the ERRORs (no-data, Error-handling, message)
- [x] Rediscuss if the ERROR notification  should be sent to slack AND/OR mail?
- [x] Discuss about the alert for the WARNINGs (no-data, Error-handling, message)
- [x] Rediscuss if the WARNING notification should be sent to slack AND/OR mail?

Application Info
- [ ] Implement in Spaceweather BackEnd the logs with INFO log_level for TimeseriesAPI, NotificationAPI, reqM, **reqX**, **reqSw**, **reqKP**, BulletinAPI, Notifications, EventIngest, Update Stream, **Authorizer**.
- [x] Implement in Grafana the logs with INFO log_level for TimeseriesAPI, NotificationAPI, reqM, reqX, reqSw, reqKP, BulletinAPI, Notifications, EventIngest, Update Stream, Authorizer.
- [x] Discuss what should be reported as string in INFO. (at this moment the logs are very unclear)

**Infrasctructure Dashboard**:
API Gateway - Infrastructure API
- [ ] This panel is always empty. Should be fixed.

API Gateway Logs.
- [x] Make the info in this panel clear/complete.

Token Lambda - Logs
- [ ] This panel is always empty. Should be fixed.

Story points: 3.0