elastic / elastic/integrations

[teleport] teleport.audit.user.connector mapped as flattened but Teleport sends a plain string

Open
#19,242 2 comments 0 reactions 1 assignee Claimed by @efd6 View on GitHub
bug Integration:teleport Team:Security-Service Integrations
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
3d 4h
Merged PRs (30d)
209

Description

### Integration Name

Teleport [packages/teleport]

### Dataset Name

_No response_

### Integration Version

1.6.0

### Agent Version

9.2.6

### Agent Output Type

elasticsearch

### Elasticsearch Version

9.2.6

### OS Version and Architecture

RHEL 9.7 (amd64)

### Software/API Version

_No response_

### Error Message

```
document_parsing_exception: failed to parse field [teleport.audit.user.connector] of type [flattened]
```

### Event Original

_No response_

### What did you do?

Ingested Teleport audit log events where the user.connector field is populated with a plain string value (e.g. an authentication connector name).

### What did you see?

The flattened mapping type rejects plain string values — it expects an object.

### What did you expect to see?

The mapping for teleport.audit.user.connector should accept the plain string values that Teleport sends. A keyword mapping would be appropriate for this field.

### Anything else?

Suggested fix
Change the mapping type for teleport.audit.user.connector from flattened to keyword.

Current workaround
Using a convert processor with type: string in a custom pipeline to coerce the value before it reaches the mapping.

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.