# 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.

## 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.

## Span Name

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

## Cloud

Filters on various attributes of cloud-based services.

Includes [availability zone](https://docs.kloudfuse.com/platform/3.2.5/glossary/#availability-zone), [cloud account id](https://docs.kloudfuse.com/platform/3.2.5/glossary/#cloud-account-id), cloud instance id, cloud instance name, cloud platform, cloud provider, host, [instance type](https://docs.kloudfuse.com/platform/3.2.5/glossary/#instance-type), [project](https://docs.kloudfuse.com/platform/3.2.5/glossary/#project), and [region](https://docs.kloudfuse.com/platform/3.2.5/glossary/#region).

- **host**  
  The host where the trace ran.  
  Includes host arch, host id, and host name.

## Kubernetes

Filters on the attributes of Kubernetes services.

Includes [display container name](https://docs.kloudfuse.com/platform/3.2.5/glossary/#display-container-name), [image name](https://docs.kloudfuse.com/platform/3.2.5/glossary/#image-name), [image tag](https://docs.kloudfuse.com/platform/3.2.5/glossary/#image-tag), [kube cluster name](https://docs.kloudfuse.com/platform/3.2.5/glossary/#kube-cluster-name), [kube container name](https://docs.kloudfuse.com/platform/3.2.5/glossary/#kube-container-name), [kube deployment](https://docs.kloudfuse.com/platform/3.2.5/glossary/#kube-deployment), [kube namespace](https://docs.kloudfuse.com/platform/3.2.5/glossary/#kube-namespace), [kube node](https://docs.kloudfuse.com/platform/3.2.5/glossary/#kube-node), kube ownerref kind, kube ownerref name, [kube replica set](https://docs.kloudfuse.com/platform/3.2.5/glossary/#kube-replica-set), [kube service](https://docs.kloudfuse.com/platform/3.2.5/glossary/#kube-service), [pod name](https://docs.kloudfuse.com/platform/3.2.5/glossary/#pod-name), pod phase, and short image.

- **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](https://docs.kloudfuse.com/platform/3.2.5/glossary/#container-id).

## Custom

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

Includes [env](https://docs.kloudfuse.com/platform/3.2.5/glossary/#env), [environment](https://docs.kloudfuse.com/platform/3.2.5/glossary/#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.
