-
Notifications
You must be signed in to change notification settings - Fork 468
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
[Atlassian JIRA & Confluence] Add support for Atlassian Cloud #2715
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
found some bugs, put back to draft |
I'm getting this issue |
I was able to get around the above issue but now with the current config whenever it paginates, instead of just updating the offset via the |
2fb214c
to
27801a6
Compare
I rebased this in order to apply the formatting of the pipeline test files in separate commits. This way it will be easier to digest the non-formatting changes during review. The JSON is now normalized due to elastic/elastic-package#644, but until all of the packages are normalized you'll get these large diffs the first time you make changes. |
b49488b
to
c89e547
Compare
/test |
even with the latest 8.0.0 docker image, I can't get past the error, #2715 (comment). Any thoughts? |
Do the tests not expose this problem? The CI checks are passing for this. It's using 7.16.0 for the tests. The 8.0 branch was missing a backport, and that has now been fixed, but not released. |
I have to keep playing with it as I'm testing it against an actual Atlassian cloud instance and I keep getting the error so idk if I have a bad docker image or something but I've cleared all my local images and still having issues. |
Try testing with either 7.17.0 or 8.1.0 (e.g. |
I'll try with 8.1. I didn't have any issues when I built filebeat from source on main branch using a basic input config to test. So it's definitely weird. |
@andrewkroh 8.1 appears to work and i'm no longer getting an error that the key doesn't exist but still having an issue with Pagination. I currently have
This should maintain the existing URL parameter so the pagination continues through the same time range. However it's being overridden by the cursor and the original request Transforms. Any thoughts on how to fix that?
|
@legoguy1000 In the current situation the request transforms run for each pagination, so I believe we might have to take another approach on this. If date is the only possible value here, we might have to drop the pagination and simply let it catch up with a smaller interval. Unless there is some sort of range query, or other values we can use from response headers or body to paginate. Let's catch up when you got time to discuss this! :) |
@P1llus copy. I'm artificially inducing pagination in order to make sure there is a valid solution as idk how many events/time is normal for these services. Unfortunately this seems like the only way to paginate but I can check again to see if there is anything in the headers. |
@legoguy1000 |
@P1llus Looks like instead of trying to set individual params, setting |
Just tested without the TZ offset and the |
a463197
to
2ad4c82
Compare
The value should be based as a YAML string. Prior to this change the final policy contained which is not what is expected. request.ssl: - object Object
The value should be based as a YAML string. Prior to this change the final policy contained which is not what is expected. request.ssl: - object Object
2ad4c82
to
1fcd66f
Compare
@andrewkroh @P1llus Can we rerun the tests to see where we are. I think it should be good now. Currently its just not using the Time Zone in the dates since its all in UTC but when 8.3 is released, we can use the URL encode template function I made for the httpjson input to add it back just to be safe. |
/test |
/test |
🌐 Coverage report
|
Does any of this depend on elastic/beats#30962? If so the kibana constrained will need change to |
Long term it should be updated to use that function, but I was able to get around it. Instead of wrapping the datetime with |
/test |
event.action event.category event.created event.kind event.original event.type
event.action event.category event.created event.kind event.original event.outcome event.type
/test |
What does this PR do?
Adds support for the SaaS versions of Confluence and JIRA in the Atlassian Cloud for the audit datastream.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots