Skip to content

Commit

Permalink
edits
Browse files Browse the repository at this point in the history
  • Loading branch information
@Simplychee
Simplychee committed Aug 7, 2024
1 parent 80f203e commit b731b52
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 6 deletions.
8 changes: 4 additions & 4 deletions docs/shipping/AWS/aws-amplify.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -64,10 +64,10 @@ git clone https://github.com/logzio/logzio_aws_serverless.git \
| Parameter | Description |
| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| TOKEN (Required) | The [token](https://app.logz.io/#/dashboard/settings/general) of the account you want to ship to. Only Admin users have access to the token. |
| LISTENER_URL (Required) | Determines protocol, listener host, and port. For example, `https://<<LISTENER-HOST>>:8071`. <br /> Replace `<<LISTENER-HOST>>` with your region's listener host (for example, `https://listener.logz.io:8071`). Use port 8070 for HTTP or 8071 for HTTPS. For more information on finding your account's region, see [Account region](https://docs.logz.io/docs/user-guide/admin/hosting-regions/account-region/) . |
| AMPLIFY_DOMAIN (Required) | Amplify domain URL can be found in the Amplify admin dashboard in **General** under **Production branch URL**. This URL will be available after your application has been deployed. |
| TYPE (Default: `logzio_amplify_access_lambda`) | The log type you'll use with this Lambda. This can be a [type that supports default parsing](https://docs.logz.io/docs/user-guide/data-hub/log-parsing/default-parsing/#built-in-log-types), or a custom log type. <br /> You'll need to create a new Lambda for each log type you use. |
| AMPLIFY_APP_ID (Required) | You can find the app ID in your Amplify admin dashboard in **General** under the **App ARN** field arn:aws:amplify:`REGION`:`AWS_ID`:apps/`APP_ID`. |
| LISTENER_URL (Required) | Determines protocol, listener host, and port. For example, `https://<<LISTENER-HOST>>:8071`. Replace `<<LISTENER-HOST>>` with your region's listener host. Use port 8070 for HTTP or 8071 for HTTPS. To find you account region, see [Account region](https://docs.logz.io/docs/user-guide/admin/hosting-regions/account-region/). |
| AMPLIFY_DOMAIN (Required) | Find the Amplify domain URL in the **Amplify admin dashboard** > **General** > **Production Branch URL**. This URL is available after deploying your application. |
| TYPE (Default: `logzio_amplify_access_lambda`) | Specify the log type for this Lambda, which can be a [default parsable type](https://docs.logz.io/docs/user-guide/data-hub/log-parsing/default-parsing/#built-in-log-types) or a custom log type. A new Lambda is required for each log type used. |
| AMPLIFY_APP_ID (Required) | You can find the app ID in your **Amplify admin dashboard** > **General** under the **App ARN** field: arn:aws:amplify:`REGION`:`AWS_ID`:apps/`APP_ID`. |
| TIMEOUT | Period in minutes, over which the Lambda function fetches Amplify logs. |

### Set the EventBridge (CloudWatch Events) trigger
Expand Down
2 changes: 1 addition & 1 deletion docs/user-guide/data-hub/cost-optimization.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ keywords: [Data hub, data optimization, optimization, drop filters, recommendati



Logz.io Data Optimization helps you manage and optimize your Logz.io products by offering tailored recommendations and a quick and easy way to drop your logs and metrics.
Logz.io Data Optimization helps Account Admins manage and optimize Logz.io products by offering tailored recommendations and a quick and easy way to drop logs and metrics.

:::note
You will receive tailored recommendations based on Log data from the last 24 hours and based on Metrics data from the previous 1 hour.
Expand Down
4 changes: 4 additions & 0 deletions docs/user-guide/data-hub/data-rollups.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,10 @@ keywords: [Data hub, data optimization, optimization, drop filters, rollups, met

You can compact and discard some of your metrics as it ages to focus on the data that matters. **Rollups** let you aggregate many time series by excluding labels, optimizing your costs and performance.

:::info note
Only Account Admins can access the Data Hub and utilize Metric rollups.
:::



## Create a Rollup
Expand Down
2 changes: 1 addition & 1 deletion docs/user-guide/quick-start.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -146,7 +146,7 @@ The following list explores the more common use cases for Logz.io's account admi
* **[Setting up SSO access](https://docs.logz.io/docs/user-guide/admin/sso/single-sign-on/)**
* **[Archiving and restoring data](https://docs.logz.io/docs/user-guide/data-hub/archive-restore/archive-and-restore/)**

In addition, Logz.io's Data Hub helps you manage and optimize your Logz.io products by offering tailored recommendations and a quick and easy way to control your logs and metrics usage. You can use Data Hub to:
In addition, Logz.io's Data Hub helps you manage and optimize your Logz.io products by offering tailored recommendations and a quick and easy way to control your logs and metrics usage. Account Admins can use Data Hub to:

* **[Analyze and optimize logs and metrics usage](/docs/user-guide/data-hub/cost-optimization/)**
* **[Create graphs and dashboards from your logs](/docs/user-guide/data-hub/logstometrics/)**
Expand Down

0 comments on commit b731b52

Please sign in to comment.