elastic / elastic/integrations

[Cisco Nexus]: Processor date with tag date_set_timestamp in pipeline logs-cisco_nexus.log-1.4.0 failed

Open
#13,097 3 comments 0 reactions 0 assignees View on GitHub
bug Integration:cisco_nexus mapping/pipeline issue needs:triage Stalled Team:Security-Deployment and Devices
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
2d 17h
Merged PRs (30d)
225

Description

### Integration Name

Cisco Nexus [cisco_nexus]

### Dataset Name

cisco_nexus.log

### Integration Version

1.4.0

### Agent Version

8.17.2

### Agent Output Type

elasticsearch

### Elasticsearch Version

8.17.2

### OS Version and Architecture

Ubuntu 22.04.5 LTS

### Software/API Version

N/A

### Error Message

```
[Processor date with tag date_set_timestamp in pipeline logs-cisco_nexus.log-1.4.0 failed with message: Text '2025 Mar 13 08:33:33.646752 CET' could not be parsed at index 20, Processor date with tag date_set_timestamp_custom in pipeline logs-cisco_nexus.log-1.4.0 failed with message: Text '2025 Mar 13 08:33:33.646752 CET' could not be parsed at index 20]
```

### Event Original

```
<189>xxxxxx: 2025 Mar 13 08:33:33.646752 CET: %ETHPORT-5-IF_DOWN_PARENT_DOWN: Interface Ethernet1/52.4 is down (Parent interface is down)
```

### What did you do?

Activated the `Collect logs from Cisco Nexus via UDP` input.

### What did you see?

Date processors in the `logs-cisco_nexus.log-1.4.0` pipeline missing format.

### What did you expect to see?

Date processor having the correct format.

### Anything else?

Workaround: Adding the `yyyy MMM d HH:mm:ss.SSSSSS zzz` format to the Date processors in the `logs-cisco_nexus.log-1.4.0` pipeline.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.