Cased excels for visualizations, so connect AWS or Datadog and get graphing. Add in Linear or GitHub and you'll be able to get a good sense of what's going with your application bugs and issues.
Mention @cased in Slack
Cased only listens if you mention it, so make sure to @cased and ask it questions.
You can ask particular questions, like:
@cased What's the latest pull request to acme/app?
Or ask for a number:
@cased What's been the highest memory usage on the database today?
Use conversations and threads
When you mention @cased in Slack, we start a new Slack thread. Follow-up messages in that thread that mention @cased with have the previous context of that conversation, so you can ask follow-up questions and reference earlier messages.
Each thread is currently independent, so Cased only has context of that particular thread conversation. Start a new thread to start fresh.
Use date ranges
Cased works best when you give it a range of dates for your data. If you don't give a range, Cased will usually ask you for one, or it will take a best guess at a reasonable date range.
Get some graphs and dive int further
Cased will create a visualization for you in real time.
@cased graph the last 24 hours of CPU usage
Anyone can modify a graph by jumping into the conversation, turning any channel in chat into a shared notebook.
Cased will also give you a link where you can further explore your graph interactively with a web UI.