Support improvements week 43 #454
Draft
+73
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Users were confused about which join types are currently supported, leading to query failures when attempting to use leftouter, rightouter, or fullouter joins. The existing note was easy to miss. Changes: - Changed Note to Warning to make the limitation more prominent - Explicitly state that unsupported join types will cause query failures - Added Tip suggesting lookup operator as a workaround for some use cases - Improved discoverability of current limitations Related support ticket: - https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01K897KEWHRYYY8412F9CAM37H/
Users were unclear about the maximum number of rows they could retrieve using limit and take operators, leading to confusion when trying to export large datasets. The 50k limit was mentioned in some places but not prominently in the operator docs. Changes: - Added explicit 50,000 row limit to parameter descriptions - Added Note callout explaining the limit and suggesting alternatives - Provided guidance on pagination for larger datasets - Made the limitation discoverable where users configure these operators Related support ticket: - https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01K7WNSFCZHXFZHK50PZ0CKQPS/
Users with ingestion delays were missing alerts because their match monitors evaluated events before they arrived in Axiom. The secondDelay parameter exists to handle this but was not documented in the monitor guides. Changes: - Added new "Handle ingestion delays" section with step-by-step guidance - Explained how to measure ingestion delay using ingestion_time() function - Documented the secondDelay API parameter with practical examples - Added Tip explaining how match monitors evaluate events based on _time - Clarified the relationship between ingestion delay and monitor timing Related support ticket: - https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01K86V64NV96VW7W9KK215FF2D/
Users received unclear error messages when creating anomaly monitors without proper time binning. The requirement for bin(_time) was mentioned but not emphasized enough, leading to confusion about why monitors failed to create. Changes: - Added Warning callout explaining time series query requirement - Provided clear example of correct query structure with bin(_time) - Explained that summarize must bin by _time for anomaly detection - Made the requirement visible during the query definition step Related support ticket: - https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01K80W57WSN7G541TF0D8MDEY8/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.