diff --git a/dashboards/configure.mdx b/dashboards/configure.mdx index b75e7d1b..25c35ba1 100644 --- a/dashboards/configure.mdx +++ b/dashboards/configure.mdx @@ -36,7 +36,7 @@ To specify who can access a dashboard: 1. In the top right, click Share **Share**. 1. Select one of the following: - Select **Just Me** to make the dashboard private. Only you can access the dashboard. - - Select a group in your Axiom organization. Only members of the selected group can access the dashboard. For more information about groups, see [Access](/reference/settings). + - Select a group in your Axiom organization. Only members of the selected group can access the dashboard. For more information about groups, see [Role-Based Access Control](/reference/settings). - Select **Everyone** to make the dashboard accessible to all users in your Axiom organization. 1. At the bottom, click **Save** to save your changes to the dashboard. @@ -55,6 +55,21 @@ To share a dashboard with a specific time range: - 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 + +You can securely share dashboards with external users, vendors, or contractors while restricting their access to only the data they need to see. This is useful when you want to provide visibility into specific datasets and dashboards without granting broad access to your Axiom organization. + +1. [Create a custom role](/reference/settings#create-custom-role) with minimal permissions: + - Read-only organization-level permissions to dashboards. + - Read-only dataset-level permissions to the datasets you want to share. + + Don’t grant organization-level dataset permissions. Only grant access to individual datasets that the vendor needs to see. This ensures they can’t access other datasets in your organization. + +1. [Create a group](/reference/settings#create-new-group) for external users. +1. Add users to the group. +1. Add the custom role to the group. +1. [Share the dashboard](/dashboards/configure#share-dashboards) with the group. + ## Control display of annotations To specify the types of annotations to display in all dashboard elements: diff --git a/monitor-data/pagerduty.mdx b/monitor-data/pagerduty.mdx index e35f84cc..ff328b95 100644 --- a/monitor-data/pagerduty.mdx +++ b/monitor-data/pagerduty.mdx @@ -32,4 +32,19 @@ To create a PagerDuty notifier, follow these steps: 1. Enter the integration key you have previously generated. 1. Click **Create**. -You can now add your PagerDuty notifier to a specific monitor in Axiom. If any incident happens on your monitor, Axiom notifies you on the PagerDuty Service Activity dashboard. \ No newline at end of file +You can now add your PagerDuty notifier to a specific monitor in Axiom. If any incident happens on your monitor, Axiom notifies you on the PagerDuty Service Activity dashboard. + +## Incident lifecycle + +Axiom automatically opens and closes PagerDuty incidents based on your monitor state. This ensures that incidents in PagerDuty accurately reflect the current state of your system without manual intervention. + + +For automatic resolution, ensure the PagerDuty service accepts `resolve` events. Some PagerDuty services have settings that prevent automatic resolution. For more information, see the [PagerDuty documentation](https://support.pagerduty.com/docs/services-and-integrations#resolve-events). + + +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. + +The deduplication key ensures that if the same monitor triggers multiple times while already in an alarm state, PagerDuty doesn’t create duplicate incidents. All notifications for the same alarm are linked to the original incident. diff --git a/reference/usage-billing.mdx b/reference/usage-billing.mdx index 8ad9ab3f..d7ce0310 100644 --- a/reference/usage-billing.mdx +++ b/reference/usage-billing.mdx @@ -13,6 +13,7 @@ The Current breakdown section explains what you paid for in your last bill and w To view details about your billing history: +1. Ensure you have permissions to modify billing. For more information, see [Role-Based Access Control](/reference/settings). 1. Go to Settings icon **Settings > Billing**. 1. In the Current breakdown section, click **Billing history**. diff --git a/send-data/fluent-bit.mdx b/send-data/fluent-bit.mdx index ecfcfe3e..c4cbb852 100644 --- a/send-data/fluent-bit.mdx +++ b/send-data/fluent-bit.mdx @@ -42,3 +42,7 @@ Fluent Bit is an open-source log processor and forwarder that allows you to coll + + +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. +