APM Filters

APM Filters allow you to narrow down observability data across the Services, Databases, and Service Map interfaces based on specific criteria. You can filter by distributed tracing usage and by the programming language of your instrumented services, including Go, Node.js, C++, Java, .NET, Rust, Python, PHP, and Ruby. Custom filters are also available to support additional filtering needs.

You can apply filters to all services in the Services, Databases, and Service Map interfaces.

APM uses these filter categories:

Telemetry type: Uses Distributed tracing
Span Type: Kloudfuse associates every service monitored by your application with a type. It automatically determines the type based on the span.type attribute. The type specifies the name of the application or framework with which the Kloudfuse agent integrated.

Options include cache, custom, db, http, grpc, queue, and web.

Examples:

cache - Redis, Memcache
custom - Custom application
db - PostgreSQL, MySQL, Cassandra
web- Flask integrations

Language: Filters on the programming language of the integrated telemetry software development kit (SDK), including go, nodejs, cpp, java, dotnet, rust, python, php, and ruby.

The language filter includes a search function.
Version: Version of the service; you can attach it as a descriptor to the time series from the services.
Cloud: Filters on various attributes of cloud-based services.

Includes availability zone, cloud account id, instance type, project, and region.
Container: Filters on the attributes of container services.

You can run containers on Docker, EC2/Baremetal, and so on.

Includes container id.
Kubernetes: Filters on the attributes of Kubernetes services.

Includes display container name, image name, image tag, kube cluster name, kube container name, kube cronjob, kube daemon set, kube deployment, kube job, kube namespace, kube node, kube replica set, kube service, kube stateful set, and pod name.
Custom: Filters that Kloudfuse extracts from the data in the incoming time series.