Support improvements week 42 #447
Draft
+37
−2
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 why they couldn't access billing information after plan upgrades or downgrades. The documentation explained how to view billing but didn't emphasize that Owner role permissions are required. This change: - Adds a prominent Note at the beginning of the Billing section explaining the Owner role requirement - Adds a prerequisite step to the billing history procedure - Provides guidance for users who don't have Owner permissions - Links to RBAC documentation for more information Related support tickets: - https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01K7MCJ1A09Y3JXVYQGBMCGNG1/ - https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01K7HPWHBSS56F0QQ5TBAZ085T/
Users were experiencing query failures and couldn't see data in the Stream tab because they configured Fluent Bit with custom timestamp field names instead of the required _time field. Axiom's time-based indexing only works with _time. This change: - Adds a prominent Warning explaining that JSON_Date_Key must be _time - Explains the consequences of using custom timestamp field names - Provides examples of incorrect configurations to avoid - Links to field restrictions documentation for more details The warning appears immediately after the configuration example to catch users before they implement an incorrect configuration. Related support ticket: - https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01K7JQNW01C60EGM9BBXDTM0AX/
Users were confused about how PagerDuty incidents auto-resolve when monitors clear. The documentation mentioned that auto-resolution happens but didn't explain the mechanism, conditions required, or troubleshooting steps. This change: - Adds a detailed 'How automatic incident resolution works' section - Explains the complete incident lifecycle with trigger and resolve events - Documents the deduplication key mechanism - Provides troubleshooting guidance for common auto-resolution issues - Uses Steps component for clear, sequential explanation The new section helps users understand what to expect and how to diagnose issues when incidents don't auto-resolve as expected. Related support ticket: - https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01K6GJHB3YNFFVRX7704YTHYFD/
Users were struggling to configure role-based access for sharing dashboards with external vendors or partners. While RBAC and dashboard sharing were documented separately, there was no end-to-end guide for this common use case. This change: - Creates a new comprehensive guide for secure dashboard sharing - Provides step-by-step instructions for creating restricted viewer roles - Explains how to use groups to manage external user access - Includes best practices and troubleshooting guidance - Documents the complete workflow from role creation to dashboard sharing - Uses appropriate Mintlify components (Steps, AccordionGroup, etc.) The guide focuses on the specific use case of granting limited read-only access to external users while maintaining security and preventing access to sensitive data in other datasets. Related support ticket: - https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01K72QSR83PKF8V56EZ3BHGK5A/
| - For custom time ranges, add `?t_ts=START&t_te=END` to the dashboard URL. Replace `START` and `END` with the start and end times in ISO 8601 format. For example, `?t_ts=2023-01-01T00:00:00.000Z&t_te=2023-01-07T23:59:59.999Z` for January 1-7, 2023. | ||
| - To compare your current time range against a previous period, add `?t_qr=RANGE&t_against=COMPARISON` or `?t_ts=START&t_te=END&t_against=COMPARISON` to the dashboard URL. Replace `COMPARISON` with the comparison period. For example, `?t_qr=24h&t_against=-1d` to compare the last 24 hours against the same time yesterday. | ||
|
|
||
| ### Share dashboards with restricted access |
There was a problem hiding this comment.
Please take this one for a spin before merging. It might be worth advising on use of None role.
| When you configure a threshold monitor with a PagerDuty notifier in Axiom, the following happens: | ||
|
|
||
| 1. **Incident creation:** When your monitor enters the **alarm** state (the threshold condition is met), Axiom sends a `trigger` event to PagerDuty. This creates a new incident in PagerDuty with a unique deduplication key that links the incident to your specific monitor. | ||
| 1. **Automatic resolution** When your monitor returns to the **OK** state (the threshold condition is no longer met), Axiom automatically sends a `resolve` event to PagerDuty using the same deduplication key. This automatically resolves the open incident in PagerDuty. |
There was a problem hiding this comment.
Is this only relevant for PagerDuty or is the approach uniform across notifiers?
| </Info> | ||
|
|
||
| <Warning> | ||
| Ensure the data you send to Axiom contains a `_time` field that represents the timestamps of the events, and set the `JSON_Date_Key` parameter to `_time`. Axiom doesn’t support custom timestamp field names for Fluent Bit. |
There was a problem hiding this comment.
Unusual to encourage users to set a _time field themselves versus letting Axiom handle that. Is this for a specific scenario?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.