-
Notifications
You must be signed in to change notification settings - Fork 444
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
[Slack] Pagination formats 'oldest' query param in scientific notation #6402
Comments
httpjson does make use of https://pkg.go.dev/encoding/json#Decoder.UseNumber so all numbers parsed from JSON become a float64. So we need to be careful about how those values get used afterwards. In this case we expect |
Fixed by #4999. |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
Package slack - 1.4.0 containing this change is available at https://epr.elastic.co/search?package=slack |
Add details from Slack audit anomaly events to published events. See https://api.slack.com/admins/audit-logs-anomaly. Updated the system test with assert.hit_count and fixed elastic#6402 which was discovered as a result. Add better pipeline error message and set event.kind=pipeline_error. --------- Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
The Slack integration sends the
oldest
query param value formatted in scientific notation format (%e
). An example value (after URL decoding) isoldest=1.566215192e+09
. The API docs1 say the value should be an integer. I doubt it is expecting scientific notation (our system tests are not).Here's an example from our system tests. This is the request tracer output.
Footnotes
https://api.slack.com/admins/audit-logs-call#endpoints ↩
The text was updated successfully, but these errors were encountered: