Shortcuts are context-sensitive, predefined filters that display as buttons at the top of the Observe and list pages. Only those shortcuts that are relevant to the current page display. By default, all shortcuts are grouped by entity type and health.
When you click a shortcut button, for example, Service Monitoring by Namespace, Cloud Native Application Observability filters and displays data according to the settings you program, removing any previous filters. The preset shortcut filter properties display on the Filter bar.
Manually setting the filters to the same state as those in a given shortcut does not activate the replicated shortcut. Deselecting a shortcut does not alter the current view.
Cloud Native Application Observability provides these shortcuts:
- Full-Stack Overview: Displays the entities in your stack by type, health status, and quantity.
- Service Topology: Displays the topology and interactions of your services; visible upon OpenTelemetry Collector configuration.
Group By Domain Shortcuts
Cloud Native Application Observability also creates shortcuts based on your tags. When Cloud Native Application Observability ingests your data and identifies key:value pairs, a tag management service assigns a tag value. If a value is not identified for an entity, the value of N/A is assigned to it. For example, if grouping by region, any entity that does not have a defined region is tagged N/A. Clicking the corresponding shortcut would display your entities by region for each region defined plus the region N/A, which includes all entities that did not include a region when ingested.
If you configure Kubernetes when you ingest your data, certain tags (such as region) propagate, the MELT data enriches, and a group-by-domain shortcut displays on the Observe page. These are examples of possible creations upon data ingestion:
- Service Monitoring by Namespace: Displays services by namespace; visible upon OpenTelemetry Collector configuration.
- Kubernetes By Region: Displays pods grouped by region and host; visible upon Kubernetes Collector configuration.
- Kubernetes by Namespace: Displays pods grouped first by Kubernetes namespace and then by region; visible upon Kubernetes Collector configuration.
When your data moves through Cloud Native Application Observability, attributes become tags. Enriched tags propagate to certain entity types. Every shortcut is grouped by entity type and health by default. Enriched tags are grouped by enriched tag names. For example, in Group by cluster, "cluster" is the enriched tag name. Group by service groups first by Service and then by Services and Service Instances. If you do not ingest tags, you will not see any data. For example, if you are only using Azure, you will not see any AWS tags.