Here is a list of features and enhancement ideas to help define priorities for the next release:
New features
Alerts
-
We currently have alerts for failed process/next and instantiation requests. Identify other failing requests that would be valuable to monitor (e.g., PATCH {org}/{app}/instances/{instanceOwnerPartyId:int}/{instanceGuid:guid}/data , PUT {org}/{app}/instances/{instanceOwnerPartyId:int}/{instanceGuid:guid}/data/{dataGuid:guid}, etc).
Should we also alert service owners when pods are down or stuck in a CrashLoopBackOff state?
-
Establish a process for monitoring alerts in the Slack channels:
Should alerts be split by squad (e.g., send failed process/next alerts to the Flyt squad)?
-
Show errors per instance. We currently only display errors at the application level
Contact points
- Allow users to select which applications and/or alert types (e.g., process/next, instantiation, etc) they want to be receive alerts for. Ensure that applications are updated or removed from the database when they are renamed or deleted/undeployed
- Allow users to activate/deactivate notifications per contact method (e.g., phone or email) rather than per contact
- On-call scheduling?
- Allow users to define own contact points in user settings?
- Should we use these contact points to notify service owners when a new app version is available or when their app is using an outdated version? Or will Renovate handle this?
- Show audit fields (who created/updated a contact point)
Instances
- Show backend and frontend versions directly in the app list to provide a better overview and avoid having to open each app
- Fix slow requests that retrieve instances in production
- Show more info on the instance page
- Improve filters (partyid, ). Index?
Enhancement ideas
- Show application logs directly in admin instead of having to open application insights
- Merge dashboard and published apps into a single view?
- Show a toast notification in Studio when an error occured in an application? Make it possible to deactivate it in settings
Here is a list of features and enhancement ideas to help define priorities for the next release:
New features
Alerts
We currently have alerts for failed
process/nextandinstantiationrequests. Identify other failing requests that would be valuable to monitor (e.g.,PATCH {org}/{app}/instances/{instanceOwnerPartyId:int}/{instanceGuid:guid}/data,PUT {org}/{app}/instances/{instanceOwnerPartyId:int}/{instanceGuid:guid}/data/{dataGuid:guid}, etc).Should we also alert service owners when pods are down or stuck in a CrashLoopBackOff state?
Establish a process for monitoring alerts in the Slack channels:
Should alerts be split by squad (e.g., send failed process/next alerts to the Flyt squad)?
Show errors per instance. We currently only display errors at the application level
Contact points
Instances
Enhancement ideas