Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Filebeat] CEL / broken mito version #41486

Open
pudovd opened this issue Oct 30, 2024 · 1 comment
Open

[Filebeat] CEL / broken mito version #41486

pudovd opened this issue Oct 30, 2024 · 1 comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label

Comments

@pudovd
Copy link

pudovd commented Oct 30, 2024

I use an Agent CR with ECK to get logs from the Loki via CEL integration.

It works well on the agent versions 8.13.4 and 8.14.3
But it fails with version 8.15.3.

I've found out that the reason is the new version of mito.
There is compatible matrix the mito versions and my code (see attachements):

beats version mito version ok?
8.13.0 1.9.0 true
8.14.0 1.10.0 true
8.15.0 1.13.1 false
- 1.14.0 false
- 1.15.0 true

The error is:

$ go install github.com/elastic/mito/cmd/[email protected]
$ mito -data loki-gitlab-audit.state.json loki-gitlab-audit.cel 
failed program instantiation: failed compilation: ERROR: <input>:77:29: type 'list(map(string, dyn))' does not support field selection
 |                 val.map(v, v.timestamp != state.cursor.inputs.start_ts ? v : {}).drop_empty().as(filtered,
 | ............................^
ERROR: <input>:77:72: found no matching overload for '_?_:_' applied to '(bool, list(map(string, dyn)), map(dyn, dyn))'
 |                 val.map(v, v.timestamp != state.cursor.inputs.start_ts ? v : {}).drop_empty().as(filtered,
 | .......................................................................^

loki-gitlab-audit.cel.txt
loki-gitlab-audit.state.json

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Oct 30, 2024
@botelastic
Copy link

botelastic bot commented Oct 30, 2024

This issue doesn't have a Team:<team> label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

No branches or pull requests

1 participant