From d9a61c0e356a741e0a28d090ac99f3bff186baa6 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Mon, 4 Nov 2024 13:53:41 +0200 Subject: [PATCH 01/14] temp --- .../admin/warm-tier/_category_.json | 8 +++ .../admin/warm-tier/warm-tier-intro.md | 63 +++++++++++++++++++ 2 files changed, 71 insertions(+) create mode 100644 docs/user-guide/admin/warm-tier/_category_.json create mode 100644 docs/user-guide/admin/warm-tier/warm-tier-intro.md diff --git a/docs/user-guide/admin/warm-tier/_category_.json b/docs/user-guide/admin/warm-tier/_category_.json new file mode 100644 index 00000000..a14894de --- /dev/null +++ b/docs/user-guide/admin/warm-tier/_category_.json @@ -0,0 +1,8 @@ +{ + "label": "Warm Tier", + "position": 3, + "link": { + "type": "generated-index", + "description": "Warm Tier - what is it and how can you utilize it." + } +} diff --git a/docs/user-guide/admin/warm-tier/warm-tier-intro.md b/docs/user-guide/admin/warm-tier/warm-tier-intro.md new file mode 100644 index 00000000..063b1597 --- /dev/null +++ b/docs/user-guide/admin/warm-tier/warm-tier-intro.md @@ -0,0 +1,63 @@ +--- +sidebar_position: 1 +title: What is Warm Tier? +image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg +description: Everything you need to know about Logz.io's Warm Tier solution +keywords: [manage, log redaction, admin controls, account administration, access control, warm, warm tier, warm logs, archive] +--- + +Logz.io offers a number of ways to store your data; Hot, Cold, and Warm tiers. + +The Warm tier is designed for logs that don't require frequent acessability, but still need to be readily available for analysis and troubleshooting when needed. + +It supports historical data and make it available when needed. + +## When should you use Warm tier? + +Warm tier is ideal for cases where data is needed periodically but doesn’t require the immediate speed of Hot tier. For example: + +* Historical analysis - Access past logs for insights, trend analysis, or event data for weeks or months after the logs' initial ingestion. + +* Root cause analysis - When troubleshooting issues, you oftern need to look back at recent historical data. With Warm tier, you'll be able to access it directly from Explore and get additional and needed context for your investigation. + +* Compliance - Compliance regulations often require data to be available for a certain period. The warm tier enables compliance by keeping data available without real-time access costs. + + + +## Why Use the Warm Tier? + +* Cost Efficiency: The Warm Tier offers significant cost savings compared to the Hot Tier, making it ideal for storing data long-term without the high expenses associated with real-time access. +* Extended Retention: Logs automatically transition from the Hot Tier to the Warm Tier after a defined period, allowing for longer retention and access to historical data. +* Performance Balance: While slightly slower than the Hot Tier, the Warm Tier maintains search and query capabilities at a moderate performance level, suitable for semi-active data. + + + + +The Warm Tier provides a valuable balance of cost, retention, and performance for data storage needs. It is designed for long-term data storage, offering significant cost savings over the Hot Tier, making it ideal for data that doesn’t require real-time access. This approach allows businesses to reduce storage expenses without sacrificing accessibility. Logs automatically transition from the Hot Tier to the Warm Tier after a set period, enabling longer data retention and easier access to historical data for analysis, compliance, and reporting purposes. Though slightly slower than the Hot Tier, the Warm Tier maintains reliable search and query functionality at a moderate performance level, well-suited for semi-active data that benefits from accessible yet cost-effective storage. + + + + + + + + + + +## Key Features and Limitations + +### Core Features +* Seamless UI Integration: Operates within the familiar Logz.io platform interface, allowing users to query and manage logs as usual. +* Flexible Retention: Data is retained longer than the Hot Tier, providing mid-term storage that’s cost-effective and accessible. +* Alerting and Exporting: While alerts cannot run directly on Warm Tier data, users can create alerts and export data as needed. + +### Performance Considerations +* Query Speed: Searches may take longer, especially for free-text or complex queries. Applying filters can improve response time. +* Visualization: Graphs and dashboards may load slower; the Hot Tier is recommended for critical real-time visualization needs. + +### Limitations +* Query Constraints: Certain limitations, like a maximum number of concurrent queries and daily scan quotas, ensure that the system isn’t overloaded. Complex queries might be restricted to maintain performance. +* Functionality Differences: Some features, such as real-time dashboards and alerting, are better suited for the Hot Tier due to performance and frequency requirements. + + +For more information, contact Logz.io support or visit the Warm Tier page on our website. \ No newline at end of file From af2c3154afa3fb8a6dc6955886cdd7f33183ff62 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Tue, 5 Nov 2024 14:02:46 +0200 Subject: [PATCH 02/14] warm tier --- .../admin/warm-tier/warm-tier-intro.md | 54 +++++-------------- 1 file changed, 13 insertions(+), 41 deletions(-) diff --git a/docs/user-guide/admin/warm-tier/warm-tier-intro.md b/docs/user-guide/admin/warm-tier/warm-tier-intro.md index 063b1597..dcfa6ea5 100644 --- a/docs/user-guide/admin/warm-tier/warm-tier-intro.md +++ b/docs/user-guide/admin/warm-tier/warm-tier-intro.md @@ -6,58 +6,30 @@ description: Everything you need to know about Logz.io's Warm Tier solution keywords: [manage, log redaction, admin controls, account administration, access control, warm, warm tier, warm logs, archive] --- -Logz.io offers a number of ways to store your data; Hot, Cold, and Warm tiers. +Logz.io provides flexible options for storing and accessing data with Hot, Warm, and Cold tiers, each tailored to different access needs. -The Warm tier is designed for logs that don't require frequent acessability, but still need to be readily available for analysis and troubleshooting when needed. - -It supports historical data and make it available when needed. - -## When should you use Warm tier? - -Warm tier is ideal for cases where data is needed periodically but doesn’t require the immediate speed of Hot tier. For example: - -* Historical analysis - Access past logs for insights, trend analysis, or event data for weeks or months after the logs' initial ingestion. - -* Root cause analysis - When troubleshooting issues, you oftern need to look back at recent historical data. With Warm tier, you'll be able to access it directly from Explore and get additional and needed context for your investigation. - -* Compliance - Compliance regulations often require data to be available for a certain period. The warm tier enables compliance by keeping data available without real-time access costs. - - - -## Why Use the Warm Tier? - -* Cost Efficiency: The Warm Tier offers significant cost savings compared to the Hot Tier, making it ideal for storing data long-term without the high expenses associated with real-time access. -* Extended Retention: Logs automatically transition from the Hot Tier to the Warm Tier after a defined period, allowing for longer retention and access to historical data. -* Performance Balance: While slightly slower than the Hot Tier, the Warm Tier maintains search and query capabilities at a moderate performance level, suitable for semi-active data. - - - - -The Warm Tier provides a valuable balance of cost, retention, and performance for data storage needs. It is designed for long-term data storage, offering significant cost savings over the Hot Tier, making it ideal for data that doesn’t require real-time access. This approach allows businesses to reduce storage expenses without sacrificing accessibility. Logs automatically transition from the Hot Tier to the Warm Tier after a set period, enabling longer data retention and easier access to historical data for analysis, compliance, and reporting purposes. Though slightly slower than the Hot Tier, the Warm Tier maintains reliable search and query functionality at a moderate performance level, well-suited for semi-active data that benefits from accessible yet cost-effective storage. +The Warm tier is designed to handle logs that don’t require frequent access but still need to be readily available for analysis and troubleshooting. By enabling Warm tier data, you can access historical data when necessary, making it a practical choice for mid-term storage. +## Warm tier use cases +The Warm Tier is ideal for scenarios where data is needed periodically but doesn’t demand the immediate speed of the Hot Tier. Key use cases include: +* **Historical Analysis**: Access past logs to gain insights, perform trend analysis, or examine event data weeks or months after ingestion. +* **Root Cause Analysis**: When troubleshooting, recent historical data often provides critical context. With the Warm Tier, logs can be accessed directly through Explore, allowing for in-depth investigations. +* **Compliance**: Many compliance regulations require data retention for a specified period. The Warm Tier facilitates compliance by keeping data accessible without incurring the costs of real-time storage. +Warm tier balances long-term retention and moderate performance for data storage needs. +Logs automatically shift from the Hot to Warm tier after a set period, extending retention and enabling easy access to historical data for analysis, compliance, and reporting. Though slightly slower than the Hot tier, the Warm tier offers reliable search and query functionality suited for semi-active data. + ## Key Features and Limitations -### Core Features -* Seamless UI Integration: Operates within the familiar Logz.io platform interface, allowing users to query and manage logs as usual. -* Flexible Retention: Data is retained longer than the Hot Tier, providing mid-term storage that’s cost-effective and accessible. -* Alerting and Exporting: While alerts cannot run directly on Warm Tier data, users can create alerts and export data as needed. - -### Performance Considerations -* Query Speed: Searches may take longer, especially for free-text or complex queries. Applying filters can improve response time. -* Visualization: Graphs and dashboards may load slower; the Hot Tier is recommended for critical real-time visualization needs. - -### Limitations -* Query Constraints: Certain limitations, like a maximum number of concurrent queries and daily scan quotas, ensure that the system isn’t overloaded. Complex queries might be restricted to maintain performance. -* Functionality Differences: Some features, such as real-time dashboards and alerting, are better suited for the Hot Tier due to performance and frequency requirements. - +Warm tier integrates seamlessly within the Logz.io platform. You can set alerts, export data, and perform queries, though search and visualization are slower compared to the Hot tier. -For more information, contact Logz.io support or visit the Warm Tier page on our website. \ No newline at end of file +For further details, contact Logz.io support. \ No newline at end of file From 992caff8b73b25c8c56b3ab0d2b27612dc376f7c Mon Sep 17 00:00:00 2001 From: Simplychee Date: Thu, 7 Nov 2024 17:55:02 +0200 Subject: [PATCH 03/14] Warming up --- .../admin/data-tiers/_category_.json | 8 ++++ .../data-tiers}/cold-tier.md | 3 +- .../admin/data-tiers/data-tiers-intro.md | 46 +++++++++++++++++++ docs/user-guide/admin/data-tiers/warm-tier.md | 28 +++++++++++ .../admin/warm-tier/_category_.json | 8 ---- .../admin/warm-tier/warm-tier-intro.md | 35 -------------- 6 files changed, 84 insertions(+), 44 deletions(-) create mode 100644 docs/user-guide/admin/data-tiers/_category_.json rename docs/user-guide/{log-management => admin/data-tiers}/cold-tier.md (98%) create mode 100644 docs/user-guide/admin/data-tiers/data-tiers-intro.md create mode 100644 docs/user-guide/admin/data-tiers/warm-tier.md delete mode 100644 docs/user-guide/admin/warm-tier/_category_.json delete mode 100644 docs/user-guide/admin/warm-tier/warm-tier-intro.md diff --git a/docs/user-guide/admin/data-tiers/_category_.json b/docs/user-guide/admin/data-tiers/_category_.json new file mode 100644 index 00000000..7c89ad16 --- /dev/null +++ b/docs/user-guide/admin/data-tiers/_category_.json @@ -0,0 +1,8 @@ +{ + "label": "Data Tiers", + "position": 3, + "link": { + "type": "generated-index", + "description": "Logz.io offers different levels of data access and retention: hot for frequently accessed data, warm for intermediate storage, and cold for long-term archival." + } +} diff --git a/docs/user-guide/log-management/cold-tier.md b/docs/user-guide/admin/data-tiers/cold-tier.md similarity index 98% rename from docs/user-guide/log-management/cold-tier.md rename to docs/user-guide/admin/data-tiers/cold-tier.md index 7c365ae3..08097a68 100644 --- a/docs/user-guide/log-management/cold-tier.md +++ b/docs/user-guide/admin/data-tiers/cold-tier.md @@ -1,9 +1,10 @@ --- -sidebar_position: 11 +sidebar_position: 3 title: Cold Tier description: Search your archived data before re-ingesting it with Cold Tier image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg keywords: [logz.io, cold tier, storage, archive, opensearch dashboards, log analysis, observability] +slug: /user-guide/log-management/cold-tier/ --- diff --git a/docs/user-guide/admin/data-tiers/data-tiers-intro.md b/docs/user-guide/admin/data-tiers/data-tiers-intro.md new file mode 100644 index 00000000..eaf8f836 --- /dev/null +++ b/docs/user-guide/admin/data-tiers/data-tiers-intro.md @@ -0,0 +1,46 @@ +--- +sidebar_position: 1 +title: Data Storage Tiers Overview +image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg +description: Everything you need to know about Logz.io's Warm Tier solution +keywords: [manage, log redaction, admin controls, account administration, access control, warm, warm tier, warm logs, archive] +--- + +Logz.io offers three distinct storage tiers: **Hot**, **Warm**, and **Cold**, designed to optimize data access, retention, and cost. Each tier suits different data usage patterns and needs, allowing you to tailor your storage to specific requirements. + +:::info note +Warm and Cold tier configurations can be set up by contacting the [Sales team](mailto:sales@logz.io). +::: + +## Hot Tier + +The Hot tier is designed for data that requires immediate and frequent access. It's the logs that are ingested daily into your account, providing the fastest retrieval speeds, ideal for recent logs, metrics, or traces actively used in analysis, monitoring, and troubleshooting. + +Hot tier data is available in real-time or near real-time, allowing you to identify, troubleshoot, and query ongoing active monitoring, alerts, and analytics, and is typically accessed within a shorter retention window. + +## Warm Tier + +The Warm tier is designed to handle logs that don’t require frequent access but still need to be readily available for analysis and troubleshooting. By enabling Warm tier data, you can access historical data when necessary, making it a practical choice for mid-term storage. + +Data in the Warm tier remains readily accessible, but with slightly slower retrieval times, making it ideal for historical analysis and trend monitoring. Use the Warm tier for data that: + +* Is relevant for medium-term retention and analysis +* Supports periodic reporting or trend analysis +* Balances cost with retrieval speed, allowing less-frequent access at a lower cost than the Hot tier + +## Cold Tier + +The Cold tier is intended for long-term data storage, optimized for cost over speed. This tier is ideal for archived data that rarely needs access but must be retained for compliance, auditing, or historical records. Data retrieval from the Cold tier may take longer, making it suitable for data that: + +* Requires long-term retention for regulatory compliance or record-keeping +* Is rarely accessed but must remain available if needed +* Offers the most cost-effective storage option for infrequently accessed data + + +## Choosing the right tier for your data + +When choosing which tier to store your data in, consider how often you need to access your data and the importance of immediate retrieval. + +The Hot tier is best for data that’s critical for immediate analysis and monitoring. The Warm tier is suitable for data that’s accessed occasionally but remains important for historical insights. The Cold tier is ideal for archived data that must be retained but is rarely accessed. + +By selecting the appropriate storage tier, you can effectively manage data access and costs based on your specific needs. \ No newline at end of file diff --git a/docs/user-guide/admin/data-tiers/warm-tier.md b/docs/user-guide/admin/data-tiers/warm-tier.md new file mode 100644 index 00000000..bf637d56 --- /dev/null +++ b/docs/user-guide/admin/data-tiers/warm-tier.md @@ -0,0 +1,28 @@ +--- +sidebar_position: 2 +title: Warm Tier +image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg +description: Everything you need to know about Logz.io's Warm Tier solution +keywords: [manage, log redaction, admin controls, account administration, access control, warm, warm tier, warm logs, archive] +--- + +:::info note +Warm tier configuration can be set up by contacting the [Sales team](mailto:sales@logz.io). +::: + +Once the Warm tier option is added to your Logz.io account, activate it by going to [Manage Accounts](https://app.logz.io/#/dashboard/settings/manage-accounts) > Select the account you want to enable and check the Warm Tier checkbox. + +warm-tier-button + + +## Accessing Warm Tier + +Once Warm data has been activated on your account, all users can access it through from [Explore](https://app.logz.io/#/dashboard/explore). + +You can identify available Warm Data by opening the time picker, where an indication appears at the bottom. As you hover over different dates, a tooltip will display whether each date contains Warm or Hot data. + +warm-data-tooltip + +When selecting a date that includes Warm Data, you’ll receive a notification indicating that retrieval may take longer, potentially several minutes. To proceed with the query, you'll need to click the **Apply Query** button at the top right to initiate the search. + +Results may take additional time to load. You can navigate away from Explore, and once the data is ready, you’ll be notified inside Logz.io's app. \ No newline at end of file diff --git a/docs/user-guide/admin/warm-tier/_category_.json b/docs/user-guide/admin/warm-tier/_category_.json deleted file mode 100644 index a14894de..00000000 --- a/docs/user-guide/admin/warm-tier/_category_.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "label": "Warm Tier", - "position": 3, - "link": { - "type": "generated-index", - "description": "Warm Tier - what is it and how can you utilize it." - } -} diff --git a/docs/user-guide/admin/warm-tier/warm-tier-intro.md b/docs/user-guide/admin/warm-tier/warm-tier-intro.md deleted file mode 100644 index dcfa6ea5..00000000 --- a/docs/user-guide/admin/warm-tier/warm-tier-intro.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -sidebar_position: 1 -title: What is Warm Tier? -image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg -description: Everything you need to know about Logz.io's Warm Tier solution -keywords: [manage, log redaction, admin controls, account administration, access control, warm, warm tier, warm logs, archive] ---- - -Logz.io provides flexible options for storing and accessing data with Hot, Warm, and Cold tiers, each tailored to different access needs. - -The Warm tier is designed to handle logs that don’t require frequent access but still need to be readily available for analysis and troubleshooting. By enabling Warm tier data, you can access historical data when necessary, making it a practical choice for mid-term storage. - -## Warm tier use cases - -The Warm Tier is ideal for scenarios where data is needed periodically but doesn’t demand the immediate speed of the Hot Tier. Key use cases include: - -* **Historical Analysis**: Access past logs to gain insights, perform trend analysis, or examine event data weeks or months after ingestion. - -* **Root Cause Analysis**: When troubleshooting, recent historical data often provides critical context. With the Warm Tier, logs can be accessed directly through Explore, allowing for in-depth investigations. - -* **Compliance**: Many compliance regulations require data retention for a specified period. The Warm Tier facilitates compliance by keeping data accessible without incurring the costs of real-time storage. - -Warm tier balances long-term retention and moderate performance for data storage needs. - -Logs automatically shift from the Hot to Warm tier after a set period, extending retention and enabling easy access to historical data for analysis, compliance, and reporting. Though slightly slower than the Hot tier, the Warm tier offers reliable search and query functionality suited for semi-active data. - - - -## Key Features and Limitations - -Warm tier integrates seamlessly within the Logz.io platform. You can set alerts, export data, and perform queries, though search and visualization are slower compared to the Hot tier. - -For further details, contact Logz.io support. \ No newline at end of file From 6165cf3c3777389206da29927157d5de8383c2da Mon Sep 17 00:00:00 2001 From: Simplychee Date: Thu, 28 Nov 2024 16:48:35 +0200 Subject: [PATCH 04/14] updating warm --- .../admin/data-tiers/data-tiers-intro.md | 15 ++++++++++ docs/user-guide/admin/data-tiers/warm-tier.md | 29 ++++++++++++++----- 2 files changed, 36 insertions(+), 8 deletions(-) diff --git a/docs/user-guide/admin/data-tiers/data-tiers-intro.md b/docs/user-guide/admin/data-tiers/data-tiers-intro.md index eaf8f836..b2f201f3 100644 --- a/docs/user-guide/admin/data-tiers/data-tiers-intro.md +++ b/docs/user-guide/admin/data-tiers/data-tiers-intro.md @@ -36,6 +36,21 @@ The Cold tier is intended for long-term data storage, optimized for cost over sp * Is rarely accessed but must remain available if needed * Offers the most cost-effective storage option for infrequently accessed data +## Archive & Restore + +Archiving allows you to move rarely accessed data to a more cost-effective, long-term storage solution of logs that don't need to be instantly searchable. When you need to investigate old logs after they have expired from your account, you can restore them to a temporary account with no additional storage costs. + + +When to Use Archiving: + +* When data is no longer actively used but must be retained for compliance, historical analysis, or regulatory requirements. +* To optimize storage costs without permanently deleting data. + +By effectively managing your data lifecycle with archiving and restoring, you can maintain performance and cost-efficiency while ensuring long-term accessibility of critical information. + +[Read more about Logz.io's Archive & Restore options](https://docs.logz.io/docs/user-guide/data-hub/archive-restore/archive-and-restore/). + + ## Choosing the right tier for your data diff --git a/docs/user-guide/admin/data-tiers/warm-tier.md b/docs/user-guide/admin/data-tiers/warm-tier.md index bf637d56..ac11c604 100644 --- a/docs/user-guide/admin/data-tiers/warm-tier.md +++ b/docs/user-guide/admin/data-tiers/warm-tier.md @@ -6,23 +6,36 @@ description: Everything you need to know about Logz.io's Warm Tier solution keywords: [manage, log redaction, admin controls, account administration, access control, warm, warm tier, warm logs, archive] --- +Warm tier is a storage option designed for data that is not frequently accessed but still needs to be readily available for analysis and troubleshooting. It provides a practical solution for mid-term storage ensuring you can retrieve historical data when required. + :::info note Warm tier configuration can be set up by contacting the [Sales team](mailto:sales@logz.io). ::: -Once the Warm tier option is added to your Logz.io account, activate it by going to [Manage Accounts](https://app.logz.io/#/dashboard/settings/manage-accounts) > Select the account you want to enable and check the Warm Tier checkbox. +## Setting Up the Warm Tier + +Once enabled on your Logz.io account, you can assign it to specific accounts or sub-accounts: + +Navigate to Manage Accounts. +Select the account you want to configure. +Choose the desired Warm Tier retention period. +Click Apply to save your changes. + + + +Once Warm Tier has been enabled on your Logz.io account, you can assign it to specific accounts or sub-accounts. To do so, navigate to [Manage Accounts](https://app.logz.io/#/dashboard/settings/manage-accounts), select the account you want to configure, choose the desired Warm Tier retention period, and click **Apply** to save your changes. -warm-tier-button +warm-tier-button -## Accessing Warm Tier +## Accessing Warm Tier Data -Once Warm data has been activated on your account, all users can access it through from [Explore](https://app.logz.io/#/dashboard/explore). +After activation, all users can access Warm Tier data through [Explore](https://app.logz.io/#/dashboard/explore). -You can identify available Warm Data by opening the time picker, where an indication appears at the bottom. As you hover over different dates, a tooltip will display whether each date contains Warm or Hot data. +Open the time picker, where indicators show the availability of Warm or Hot data. Hover over specific dates to view a tooltip specifying the type of data available. -warm-data-tooltip +When selecting a date with Warm Data, a notification will inform you that retrieval may take several minutes. To proceed, manually apply the query by clicking **Apply Query** in the top-right corner. This step ensures intentional data retrieval, as Warm Data may take longer to load and incur additional costs. -When selecting a date that includes Warm Data, you’ll receive a notification indicating that retrieval may take longer, potentially several minutes. To proceed with the query, you'll need to click the **Apply Query** button at the top right to initiate the search. +warm-data-tooltip -Results may take additional time to load. You can navigate away from Explore, and once the data is ready, you’ll be notified inside Logz.io's app. \ No newline at end of file +While waiting for results, you can navigate away from Explore. You’ll receive an in-app notification once the data is ready. From 2bf4497c145596e6ecb53c60d626c990ee9da4e7 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Thu, 28 Nov 2024 17:12:40 +0200 Subject: [PATCH 05/14] no trend --- docs/user-guide/admin/data-tiers/data-tiers-intro.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/user-guide/admin/data-tiers/data-tiers-intro.md b/docs/user-guide/admin/data-tiers/data-tiers-intro.md index b2f201f3..d2451f20 100644 --- a/docs/user-guide/admin/data-tiers/data-tiers-intro.md +++ b/docs/user-guide/admin/data-tiers/data-tiers-intro.md @@ -22,10 +22,9 @@ Hot tier data is available in real-time or near real-time, allowing you to ident The Warm tier is designed to handle logs that don’t require frequent access but still need to be readily available for analysis and troubleshooting. By enabling Warm tier data, you can access historical data when necessary, making it a practical choice for mid-term storage. -Data in the Warm tier remains readily accessible, but with slightly slower retrieval times, making it ideal for historical analysis and trend monitoring. Use the Warm tier for data that: +Data in the Warm tier remains readily accessible, but with slightly slower retrieval times. Use the Warm tier for data that: * Is relevant for medium-term retention and analysis -* Supports periodic reporting or trend analysis * Balances cost with retrieval speed, allowing less-frequent access at a lower cost than the Hot tier ## Cold Tier @@ -34,7 +33,6 @@ The Cold tier is intended for long-term data storage, optimized for cost over sp * Requires long-term retention for regulatory compliance or record-keeping * Is rarely accessed but must remain available if needed -* Offers the most cost-effective storage option for infrequently accessed data ## Archive & Restore From bda94ddd1977a79d0fe1969c687d2c8220b470d0 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Thu, 28 Nov 2024 17:16:56 +0200 Subject: [PATCH 06/14] oops --- docs/user-guide/admin/data-tiers/warm-tier.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/docs/user-guide/admin/data-tiers/warm-tier.md b/docs/user-guide/admin/data-tiers/warm-tier.md index ac11c604..f52482f0 100644 --- a/docs/user-guide/admin/data-tiers/warm-tier.md +++ b/docs/user-guide/admin/data-tiers/warm-tier.md @@ -14,16 +14,7 @@ Warm tier configuration can be set up by contacting the [Sales team](mailto:sale ## Setting Up the Warm Tier -Once enabled on your Logz.io account, you can assign it to specific accounts or sub-accounts: - -Navigate to Manage Accounts. -Select the account you want to configure. -Choose the desired Warm Tier retention period. -Click Apply to save your changes. - - - -Once Warm Tier has been enabled on your Logz.io account, you can assign it to specific accounts or sub-accounts. To do so, navigate to [Manage Accounts](https://app.logz.io/#/dashboard/settings/manage-accounts), select the account you want to configure, choose the desired Warm Tier retention period, and click **Apply** to save your changes. +Once Warm Tier has been enabled on your Logz.io account, you can assign it to one or more of your sub-accounts. To do so, navigate to [Manage Accounts](https://app.logz.io/#/dashboard/settings/manage-accounts), select the sub account you want to configure, choose the desired Warm Tier retention period, and click **Apply** to save your changes. warm-tier-button From f55b14e93a15478561adfb63dbe7d877b7cbe718 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Thu, 28 Nov 2024 17:25:40 +0200 Subject: [PATCH 07/14] new image --- docs/user-guide/admin/data-tiers/warm-tier.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/user-guide/admin/data-tiers/warm-tier.md b/docs/user-guide/admin/data-tiers/warm-tier.md index f52482f0..a99eb51c 100644 --- a/docs/user-guide/admin/data-tiers/warm-tier.md +++ b/docs/user-guide/admin/data-tiers/warm-tier.md @@ -27,6 +27,7 @@ Open the time picker, where indicators show the availability of Warm or Hot data When selecting a date with Warm Data, a notification will inform you that retrieval may take several minutes. To proceed, manually apply the query by clicking **Apply Query** in the top-right corner. This step ensures intentional data retrieval, as Warm Data may take longer to load and incur additional costs. -warm-data-tooltip + +![warm data activate](https://dytvr9ot2sszz.cloudfront.net/logz-docs/data-tiers/time-picker-and-run-query.png) While waiting for results, you can navigate away from Explore. You’ll receive an in-app notification once the data is ready. From 7a44397ab1c6f4f4f692197eafad41760cfde6cf Mon Sep 17 00:00:00 2001 From: Simplychee Date: Thu, 28 Nov 2024 17:32:22 +0200 Subject: [PATCH 08/14] chachachanges --- docs/user-guide/admin/data-tiers/warm-tier.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/user-guide/admin/data-tiers/warm-tier.md b/docs/user-guide/admin/data-tiers/warm-tier.md index a99eb51c..2d939315 100644 --- a/docs/user-guide/admin/data-tiers/warm-tier.md +++ b/docs/user-guide/admin/data-tiers/warm-tier.md @@ -21,11 +21,15 @@ Once Warm Tier has been enabled on your Logz.io account, you can assign it to on ## Accessing Warm Tier Data -After activation, all users can access Warm Tier data through [Explore](https://app.logz.io/#/dashboard/explore). +After activation, all sub account users can access Warm Tier data through [Explore](https://app.logz.io/#/dashboard/explore). -Open the time picker, where indicators show the availability of Warm or Hot data. Hover over specific dates to view a tooltip specifying the type of data available. +:::tip +When querying Warm Tier data, limit the time range, use filters, and focus on key information to improve speed. Warm Tier data has a 5-minute timeout; you'll be notified if retrieval fails. +::: + +Open the time picker, where indicators show the availability of Warm or Hot data. -When selecting a date with Warm Data, a notification will inform you that retrieval may take several minutes. To proceed, manually apply the query by clicking **Apply Query** in the top-right corner. This step ensures intentional data retrieval, as Warm Data may take longer to load and incur additional costs. +When selecting a date with Warm Data, a notification will inform you that retrieval may take several minutes. To proceed, confirm your date selection and click **Apply Query** in the top-right corner. This manual step ensures intentional data retrieval, as Warm Data may take longer to load and incur additional costs. ![warm data activate](https://dytvr9ot2sszz.cloudfront.net/logz-docs/data-tiers/time-picker-and-run-query.png) From 07ca36542c7462e54ab9c323671a81a1be9923f8 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Thu, 28 Nov 2024 17:52:09 +0200 Subject: [PATCH 09/14] image --- docs/user-guide/admin/data-tiers/warm-tier.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/admin/data-tiers/warm-tier.md b/docs/user-guide/admin/data-tiers/warm-tier.md index 2d939315..8cd524aa 100644 --- a/docs/user-guide/admin/data-tiers/warm-tier.md +++ b/docs/user-guide/admin/data-tiers/warm-tier.md @@ -29,9 +29,9 @@ When querying Warm Tier data, limit the time range, use filters, and focus on ke Open the time picker, where indicators show the availability of Warm or Hot data. -When selecting a date with Warm Data, a notification will inform you that retrieval may take several minutes. To proceed, confirm your date selection and click **Apply Query** in the top-right corner. This manual step ensures intentional data retrieval, as Warm Data may take longer to load and incur additional costs. +When selecting a date containing Warm Data, a notification will inform you that retrieval may take several minutes. To proceed, confirm your date selection by clicking **Apply** in the time picker, then click **Apply Query** in the main Explore query bar. This manual step ensures intentional data retrieval, as Warm Data may take longer to load and incur additional costs. -![warm data activate](https://dytvr9ot2sszz.cloudfront.net/logz-docs/data-tiers/time-picker-and-run-query.png) +![warm data activate](https://dytvr9ot2sszz.cloudfront.net/logz-docs/data-tiers/both-times-warm-data.png) While waiting for results, you can navigate away from Explore. You’ll receive an in-app notification once the data is ready. From 325c7d5317df2d58973bf1aa5e3a5edf4696d2bb Mon Sep 17 00:00:00 2001 From: Simplychee Date: Thu, 28 Nov 2024 17:55:06 +0200 Subject: [PATCH 10/14] tier not data --- docs/user-guide/admin/data-tiers/warm-tier.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/admin/data-tiers/warm-tier.md b/docs/user-guide/admin/data-tiers/warm-tier.md index 8cd524aa..73eaf584 100644 --- a/docs/user-guide/admin/data-tiers/warm-tier.md +++ b/docs/user-guide/admin/data-tiers/warm-tier.md @@ -29,7 +29,7 @@ When querying Warm Tier data, limit the time range, use filters, and focus on ke Open the time picker, where indicators show the availability of Warm or Hot data. -When selecting a date containing Warm Data, a notification will inform you that retrieval may take several minutes. To proceed, confirm your date selection by clicking **Apply** in the time picker, then click **Apply Query** in the main Explore query bar. This manual step ensures intentional data retrieval, as Warm Data may take longer to load and incur additional costs. +When selecting a date containing Warm Tier data, a notification will inform you that retrieval may take several minutes. To proceed, confirm your date selection by clicking **Apply** in the time picker, then click **Apply Query** in the main Explore query bar. This manual step ensures intentional data retrieval, as Warm Tier data may take longer to load and incur additional costs. ![warm data activate](https://dytvr9ot2sszz.cloudfront.net/logz-docs/data-tiers/both-times-warm-data.png) From 7e663b9eacc2abaa1ccdf9e9d2396d3224a97050 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Thu, 28 Nov 2024 20:01:30 +0200 Subject: [PATCH 11/14] run --- docs/user-guide/admin/data-tiers/warm-tier.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/admin/data-tiers/warm-tier.md b/docs/user-guide/admin/data-tiers/warm-tier.md index 73eaf584..74f2dc46 100644 --- a/docs/user-guide/admin/data-tiers/warm-tier.md +++ b/docs/user-guide/admin/data-tiers/warm-tier.md @@ -29,7 +29,7 @@ When querying Warm Tier data, limit the time range, use filters, and focus on ke Open the time picker, where indicators show the availability of Warm or Hot data. -When selecting a date containing Warm Tier data, a notification will inform you that retrieval may take several minutes. To proceed, confirm your date selection by clicking **Apply** in the time picker, then click **Apply Query** in the main Explore query bar. This manual step ensures intentional data retrieval, as Warm Tier data may take longer to load and incur additional costs. +When selecting a date containing Warm Tier data, a notification will inform you that retrieval may take several minutes. To proceed, confirm your date selection by clicking **Apply** in the time picker, then click **Run Query** in the main Explore query bar. This manual step ensures intentional data retrieval, as Warm Tier data may take longer to load and incur additional costs. ![warm data activate](https://dytvr9ot2sszz.cloudfront.net/logz-docs/data-tiers/both-times-warm-data.png) From d504cc6e9567577f320e9cb46d2684aabe477669 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Fri, 29 Nov 2024 10:06:23 +0200 Subject: [PATCH 12/14] more fixes --- docs/user-guide/admin/data-tiers/warm-tier.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/admin/data-tiers/warm-tier.md b/docs/user-guide/admin/data-tiers/warm-tier.md index 74f2dc46..1bfa4065 100644 --- a/docs/user-guide/admin/data-tiers/warm-tier.md +++ b/docs/user-guide/admin/data-tiers/warm-tier.md @@ -9,14 +9,20 @@ keywords: [manage, log redaction, admin controls, account administration, access Warm tier is a storage option designed for data that is not frequently accessed but still needs to be readily available for analysis and troubleshooting. It provides a practical solution for mid-term storage ensuring you can retrieve historical data when required. :::info note -Warm tier configuration can be set up by contacting the [Sales team](mailto:sales@logz.io). +Warm tier configuration can be set up by contacting the [Sales team](https://logz.io/contact-us/). ::: +Prerequisites + +Data gets to warm only after it's been to hot. All hot data goes to warm data according to the retention period configured by you. When you enable Warm Tier, the retention minimum for Hot tier is 4 days. + ## Setting Up the Warm Tier Once Warm Tier has been enabled on your Logz.io account, you can assign it to one or more of your sub-accounts. To do so, navigate to [Manage Accounts](https://app.logz.io/#/dashboard/settings/manage-accounts), select the sub account you want to configure, choose the desired Warm Tier retention period, and click **Apply** to save your changes. -warm-tier-button +warm-tier-button + +Data transitions to the Warm Tier **only after** residing in the Hot Tier. All Hot Tier data moves to the Warm Tier based on the retention period you configure. When enabling the Warm Tier, the minimum retention period for the Hot Tier is set to 4 days. ## Accessing Warm Tier Data From 1e4a49fa985ce5f11d13d3ae370968ee06ac76fb Mon Sep 17 00:00:00 2001 From: Simplychee Date: Fri, 29 Nov 2024 10:07:38 +0200 Subject: [PATCH 13/14] wording --- docs/user-guide/admin/data-tiers/warm-tier.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/admin/data-tiers/warm-tier.md b/docs/user-guide/admin/data-tiers/warm-tier.md index 1bfa4065..88e7c950 100644 --- a/docs/user-guide/admin/data-tiers/warm-tier.md +++ b/docs/user-guide/admin/data-tiers/warm-tier.md @@ -22,7 +22,7 @@ Once Warm Tier has been enabled on your Logz.io account, you can assign it to on warm-tier-button -Data transitions to the Warm Tier **only after** residing in the Hot Tier. All Hot Tier data moves to the Warm Tier based on the retention period you configure. When enabling the Warm Tier, the minimum retention period for the Hot Tier is set to 4 days. +Data transitions to the Warm Tier **only after** stored in the Hot Tier. All Hot Tier data moves to the Warm Tier based on the retention period you configure. When enabling the Warm Tier, the minimum retention period for the Hot Tier is set to 4 days. ## Accessing Warm Tier Data From 5e8c75291dccb3f41b7f6cafbd1fd87269d7d5f1 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Fri, 29 Nov 2024 10:08:43 +0200 Subject: [PATCH 14/14] note --- docs/user-guide/admin/data-tiers/data-tiers-intro.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/user-guide/admin/data-tiers/data-tiers-intro.md b/docs/user-guide/admin/data-tiers/data-tiers-intro.md index d2451f20..d542aad9 100644 --- a/docs/user-guide/admin/data-tiers/data-tiers-intro.md +++ b/docs/user-guide/admin/data-tiers/data-tiers-intro.md @@ -22,6 +22,8 @@ Hot tier data is available in real-time or near real-time, allowing you to ident The Warm tier is designed to handle logs that don’t require frequent access but still need to be readily available for analysis and troubleshooting. By enabling Warm tier data, you can access historical data when necessary, making it a practical choice for mid-term storage. +Data transitions to the Warm Tier **only after** stored in the Hot Tier. All Hot Tier data moves to the Warm Tier based on the retention period you configure. When enabling the Warm Tier, the minimum retention period for the Hot Tier is set to 4 days. + Data in the Warm tier remains readily accessible, but with slightly slower retrieval times. Use the Warm tier for data that: * Is relevant for medium-term retention and analysis