-
Notifications
You must be signed in to change notification settings - Fork 86
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
Add specification for post event to an analytics collection #3363
Conversation
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
...on/search_application/post_behavioral_analytics_event/BehavioralAnalyticsEventPostRequest.ts
Show resolved
Hide resolved
...n/search_application/post_behavioral_analytics_event/BehavioralAnalyticsEventPostResponse.ts
Outdated
Show resolved
Hide resolved
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
1 similar comment
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
1 similar comment
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
…nt/BehavioralAnalyticsEventPostResponse.ts Co-authored-by: Laura Trotta <[email protected]>
…nt/BehavioralAnalyticsEventPostRequest.ts Co-authored-by: Laura Trotta <[email protected]>
bc083db
to
fc0037b
Compare
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
Co-authored-by: Laura Trotta <[email protected]> Co-authored-by: Quentin Pradet <[email protected]> (cherry picked from commit 2f57f6b)
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.17 8.17
# Navigate to the new working tree
cd .worktrees/backport-8.17
# Create a new branch
git switch --create backport-3363-to-8.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 2f57f6bbe10648cf0b45a8b7ed6ea37cbecf1494
# Push it to GitHub
git push --set-upstream origin backport-3363-to-8.17
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.17 Then, create a pull request where the |
…3431) Co-authored-by: Laura Trotta <[email protected]> Co-authored-by: Quentin Pradet <[email protected]> (cherry picked from commit 2f57f6b)
Co-authored-by: Laura Trotta <[email protected]> Co-authored-by: Quentin Pradet <[email protected]> (cherry picked from commit 2f57f6b)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
…3432) Co-authored-by: Laura Trotta <[email protected]> Co-authored-by: Quentin Pradet <[email protected]> (cherry picked from commit 2f57f6b)
Relates to #3377, #2482
This PR adds a specification so that we can retire https://www.elastic.co/guide/en/elasticsearch/reference/master/post-analytics-collection-event.html