### Lexically Correct and Verified Identifier Example

Source: https://docs.silabs.com/network-analyzer/latest/network-analyzer-filtering-captured-data

This example shows a lexically correct expression where an identifier is compared to itself. Even though 'foo' is unverified, the expression will return all events because 'foo' is known to equal itself.

```text
foo == foo
```

--------------------------------

### Verified Event Key Example

Source: https://docs.silabs.com/network-analyzer/latest/network-analyzer-filtering-captured-data

This expression demonstrates a verifiable event key, 'fifteenFour.dest', which represents real data in an event or transaction, ensuring accurate filtering.

```text
fifteenFour.dest == 0xffff
```

--------------------------------

### Lexically Correct but Unverified Identifier Example

Source: https://docs.silabs.com/network-analyzer/latest/network-analyzer-filtering-captured-data

This example demonstrates a lexically correct filter expression where the identifiers 'foo' and 'bar' are unverified. Network Analyzer will warn the user about potential unexpected results.

```text
foo == bar
```

--------------------------------

### Filter Expression Examples for Network Analyzer

Source: https://docs.silabs.com/network-analyzer/latest/network-analyzer-filtering-captured-data

Demonstrates various filter expressions used in Network Analyzer to match specific events and data patterns. These examples showcase filtering by sequence number, ACK requirements, source addresses, presence of fields, string matching, event types, and frame byte patterns.

```network-analyzer-filter
isType(Route)
```

```network-analyzer-filter
fifteenFour.sequence == 0x52
```

```network-analyzer-filter
fifteenFour.ackRequired == true && fifteenFour.source == 0x035f
```

```network-analyzer-filter
isPresent(zigbeeSecurity.frameCounter)
```

```network-analyzer-filter
event.summary | "string"
```

```network-analyzer-filter
isType(Packet)
```

```network-analyzer-filter
frameMatch(fifteenFour,"**88**EF/********")
```

```network-analyzer-filter
event.summary == "APS Ack"
```

```network-analyzer-filter
event.linkStatus
```

--------------------------------

### Payload Access with Special Identifiers

Source: https://docs.silabs.com/network-analyzer/latest/network-analyzer-filtering-captured-data

The 'payload.xxx' special identifier allows access to payload bytes for a given layer 'xxx'. Expressions can be formed to match specific payload byte sequences.

```text
payload.raw == {001122aabbcc}
```