-
**What changed?**
- new option to launch an app from the workspace list or to start a workspace (requested by customers)
- UX improvements e.g. simplifying filtering and bulk actions
- new option to v…
-
The title says everything.
There are often too much nodes and relationships to see all at the same time. So to make good use of your data, you use the filtering option. To make the filtering option…
-
### Bug report
### Reproduction of the problem
[Dojo](https://dojo.telerik.com/IdOqaKEd/12) example (provided in ticket id: 1342161)
1. Press the "Dump (using data property)" button => the inde…
-
# Feature Request: Content-based filtering for Gossip client rebroadcasts
## Current Behavior
The Gossip client in Iroh's Node currently rebroadcasts all messages associated with a topic that the …
-
if there are many nodes to select from, a filter will be required.
-
### Proposal
Add a policy which allows to list a summary of allocations or a topology-tailored resource so that the topology view can be filled with relevant data without exposing all job prope…
-
Error [example](https://github.com/getappmap/navie-benchmark/actions/runs/10949246453/job/30402054109#step:7:1216):
```
Handling exception: Error: Failed to complete: SSE Error: {"type":"error","e…
-
As a design issue, we need to decide
* Level of selection: i.e. just success, failure, not run as we have been doing or should we support the full range of possible outcomes, including Inconclusive, …
-
### Bug Description
When executing a search query in the Elasticsearch node, the intended filtering is not applied. Instead of returning the correct subset of matching documents, the search retrieves…
-
Currently the DB Console UI allows filtering metrics by node. There is no way to filter metrics which are tagged by StoreID as well:
In the DB Console UI metrics dashboards:
![image](https://use…