Requested

In Progress

Done

Main Roadmap

All the agent to be configured to collect specific logs. Starting with systemctl (journalctl) logs for Linux distro’s

logs

Anthony Anderson

The agent owner (after being claimed) can setup agent specific alerts which skip all backend routing to be located closer to the source. This will ensure you get alerts as close to the event that triggered it as possible. Removes the ability for a service interruption leading to inadequate alert times.

agent alerts

Be able to configure and setup different notification channels to be alerted when one of the agents you’re tracking goes offline or reaches a specific resource allotment.

workspace alerts

Right now the agent collects metrics and we are collecting them on the backend. The user interface and status page need to leverage this data in creating the charts. Looking at including this as part of the public API to allow for custom dashboards for projects if they wish.

LOa