Activity and Support

In day-to-day work, it is important not only to look at databases and graphs, but also to understand what exactly was done in the interface and how to quickly pass context to support. For that, Console has the Activity and Support sections.

Activity

Activity is the working log of actions initiated through Console.

It usually shows:

• time;
• action type;
• target object;
• status;
• additional details.

This section is especially useful for quickly answering questions such as:

• was the database actually created;
• was there a deletion attempt;
• did the operation end with an error;
• what was happening through the UI shortly before the failure.

Important: Activity is convenient for day-to-day work and for understanding recent actions in Console, but it does not replace the full diagnostic picture of a resource. For the actual database state, still use the database card, Metrics, and Logs.

Support from the interface

Console includes a built-in support form. This is convenient because you do not have to switch to external communication to quickly record a problem.

Usually, the request lets you:

• describe the situation;
• attach files or screenshots;
• send the request directly from the working interface.

What is useful to include in the request

A good request almost always contains:

• the tenant name;
• the database name;
• the approximate time when the problem occurred;
• the error text;
• a description of what you were doing before the error;
• if needed, worker_id or db id, if they are visible in the UI and help support.

Practical scenario

If an issue occurs, a convenient path is:

1. open the database card;
2. check the state;
3. open Metrics and Logs;
4. look at Active queries if needed;
5. then send a support request already backed by concrete facts.

This speeds up incident investigation and reduces the number of unnecessary follow-up questions.