APM Traces Filters

You can apply the following filters when using the Traces interface. Traces use these filter categories:

Service

Choose the service by its type and facet, or use the Search service option.

Note that these services may have duplicate names; however, each one is tagged with relevant facets that identify the service as unique.

Service filter for Traces
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

Component
Duration(ms)
Error
Service Name

Choose the service by its service name, or use the Search Service Name option.

Service name filter for Traces
Span Name

Choose the span by its span name, or use the Search Span Name option.

Span name filter for Traces
Cloud

Filters on various attributes of cloud-based services.

Includes availability zone, cloud account id, cloud instance id, cloud instance name, cloud platform, cloud provider, host, instance type, project, and region.

host

The host where the trace ran.

Includes host arch, host id, and host name.

Kubernetes

Filters on the attributes of Kubernetes services.

app

Filters on the name of the application.

code

Filters on the properties found in the code.

Includes code filepath, code function, and code namespace.

Container

Filters on the attributes of container services.

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

Includes container id.

Custom

Filters that Kloudfuse extracts from the data in the incoming time series.

Includes env, environment, and outcome (success or failure).

db

Filters on database attributes, such as db instance, db name, db redis database index, db system, db type, and db user.