Amazon CloudWatch Logs now supports log ingestion using HTTP-based protocol Amazon CloudWatch Logs now supports HTTP Log Collector (HLC), ND-JSON, Structured JSON and OTEL for sending logs using HTTP-based protocol with bearer token. With this launch, customers can ingest logs where AWS SDK integration is not feasible, such as with third-party or packaged software. The new endpoints are: HTTP Log Collector (HLC) Logs (https://logs .<region>.amazonaws.com/services/collector/event) — for JSON events, ideal for migrating existing log pipelines.  ND-JSON Logs (https://logs.<region>.amazonaws.com/ingest/bulk) — for newline-delimited JSON, where each line is an independent log event. Perfect for high-volume streaming and bulk log ingestion.  Structured JSON Logs (https://logs .<region>.amazonaws.com/ingest/json) — Send a single JSON object or a JSON array of objects. OpenTelemetry Logs (https://logs .<region>.amazonaws.com/v1/logs) — for OTLP-formatted logs in JSON or Protobuf encoding to CloudWatch. To enable the HLC endpoint, navigate to CloudWatch Settings in the AWS Console and generate an API key. CloudWatch creates the necessary IAM user with service-specific credentials and permissions. API keys can be configured with expiration periods of 1, 5, 30, 90, or 365 days. Customers must enable bearer token authentication on each log group before it can accept logs, which protects from unintended ingestion. Customers can use service control policies to block the creation of service-specific credentials. These endpoints are available in the following AWS Regions: US East (N. Virginia), US West (N. California), US West (Oregon), and US East (Ohio). To learn more about the HLC endpoint and security best practices, refer to the CloudWatch Logs Documentation.

🆕 Amazon CloudWatch Logs supports HTTP-based log ingestion via HLC, ND-JSON, Structured JSON, and OpenTelemetry, enabling third-party software to send logs without AWS SDK. Region-specific endpoints require bearer token auth. Available in US East, US West, and US East (…

#AWS #AmazonCloudwatchLogs

Amazon CloudWatch Logs now supports log ingestion using HTTP-based protocol Amazon CloudWatch Logs now supports HTTP Log Collector (HLC), ND-JSON, Structured JSON and OTEL for sending logs using HTTP-based protocol with bearer token. With this launch, customers can ingest logs where AWS SDK integration is not feasible, such as with third-party or packaged software. The new endpoints are: HTTP Log Collector (HLC) Logs (https://logs .<region>.amazonaws.com/services/collector/event) — for JSON events, ideal for migrating existing log pipelines.  ND-JSON Logs (https://logs.<region>.amazonaws.com/ingest/bulk) — for newline-delimited JSON, where each line is an independent log event. Perfect for high-volume streaming and bulk log ingestion.  Structured JSON Logs (https://logs .<region>.amazonaws.com/ingest/json) — Send a single JSON object or a JSON array of objects. OpenTelemetry Logs (https://logs .<region>.amazonaws.com/v1/logs) — for OTLP-formatted logs in JSON or Protobuf encoding to CloudWatch. To enable the HLC endpoint, navigate to CloudWatch Settings in the AWS Console and generate an API key. CloudWatch creates the necessary IAM user with service-specific credentials and permissions. API keys can be configured with expiration periods of 1, 5, 30, 90, or 365 days. Customers must enable bearer token authentication on each log group before it can accept logs, which protects from unintended ingestion. Customers can use service control policies to block the creation of service-specific credentials. These endpoints are available in the following AWS Regions: US East (N. Virginia), US West (N. California), US West (Oregon), and US East (Ohio). To learn more about the HLC endpoint and security best practices, refer to the https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CWL_HTTP_Endpoints.html. 

Amazon CloudWatch Logs now supports log ingestion using HTTP-based protocol

Amazon CloudWatch Logs now supports HTTP Log Collector (HLC), ND-JSON, Structured JSON and OTEL for sending logs using HTTP-based protocol with bearer token. With this launch, customers ca...

#AWS #AmazonCloudwatchLogs

Amazon CloudWatch Logs announces increased query concurrency and API limits Amazon CloudWatch Logs customers can now run up to 100 concurrent queries per account and execute 10 StartQuery and GetQueryResults API calls per second per account/per-region, using the Logs Insights Query Language (Logs Insights QL). These limit increases enable customers to support more users and execute more concurrent queries. With concurrency increasing from 30 to 100, more users can simultaneously run queries and leverage dashboards using Logs Insights QL. Customers using StartQuery and GetQueryResults APIs for Logs Insights QL benefit from higher limits without being throttled, enabling them to execute more queries and view results faster. The limit increases for Logs Insights queries is available in US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Canada (Central), Canada (Calgary), South America (São Paulo), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), Europe (Milan), Europe (Zurich), Europe (Spain), Africa (Cape Town), Middle East(Tel Aviv), Asia Pacific (Mumbai), Asia Pacific (Hyderabad), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Melbourne), Asia Pacific (Tokyo), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Hong Kong), Asia Pacific (Jakarta), Asia Pacific (Bangkok), Asia Pacific (Malaysia), Asia Pacific (Auckland), Asia Pacific (Taipei), and Mexico (Querétaro). For more information, visit the  Amazon CloudWatch Logs https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AnalyzingLogData.html. 

Amazon CloudWatch Logs announces increased query concurrency and API limits

Amazon CloudWatch Logs customers can now run up to 100 concurrent queries per account and execute 10 StartQuery and GetQueryResults API calls per second per account/per-reg...

#AWS #AmazonCloudwatch #AmazonCloudwatchLogs

Amazon CloudWatch Logs announces increased query concurrency and API limits Amazon CloudWatch Logs customers can now run up to 100 concurrent queries per account and execute 10 StartQuery and GetQueryResults API calls per second per account/per-region, using the Logs Insights Query Language (Logs Insights QL). These limit increases enable customers to support more users and execute more concurrent queries. With concurrency increasing from 30 to 100, more users can simultaneously run queries and leverage dashboards using Logs Insights QL. Customers using StartQuery and GetQueryResults APIs for Logs Insights QL benefit from higher limits without being throttled, enabling them to execute more queries and view results faster. The limit increases for Logs Insights queries is available in US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Canada (Central), Canada (Calgary), South America (São Paulo), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), Europe (Milan), Europe (Zurich), Europe (Spain), Africa (Cape Town), Middle East(Tel Aviv), Asia Pacific (Mumbai), Asia Pacific (Hyderabad), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Melbourne), Asia Pacific (Tokyo), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Hong Kong), Asia Pacific (Jakarta), Asia Pacific (Bangkok), Asia Pacific (Malaysia), Asia Pacific (Auckland), Asia Pacific (Taipei), and Mexico (Querétaro). For more information, visit the  Amazon CloudWatch Logs documentation.

🆕 Amazon CloudWatch Logs boosts query concurrency to 100 per account and API calls to 10/sec, enabling more users to run queries and view results faster across 26 regions. For details, see Amazon CloudWatch Logs documentation.

#AWS #AmazonCloudwatch #AmazonCloudwatchLogs

AWS expands Resource Control Policies support for Cognito and CloudWatch Logs AWS Resource Control Policies (RCPs) now provide support for https://aws.amazon.com/pm/cognito/?trk=de90528c-2450-48d7-9981-bc556d44c9ab&sc_channel=ps&trk=de90528c-2450-48d7-9981-bc556d44c9ab&sc_channel=ps&ef_id=EAIaIQobChMI1oPdpd-JkgMVEh-tBh0iWzpHEAAYASAAEgLl7_D_BwE:G:s&s_kwcid=AL!4422!3!652240143559!e!!g!!cognito!19878797452!155825919588&gad_campaignid=19878797452&gbraid=0AAAAADjHtp-6asfTXR8BCPoEoERBRak--&gclid=EAIaIQobChMI1oPdpd-JkgMVEh-tBh0iWzpHEAAYASAAEgLl7_D_BwE and https://aws.amazon.com/cloudwatch/?refid=de90528c-2450-48d7-9981-bc556d44c9ab. Resource control policies (RCPs) are a type of organization policy that you can use to manage permissions in your organization. RCPs offer central control over the maximum available permissions for resources in your organization. With this expansion, you can now use RCPs to manage permissions for Amazon Cognito and Amazon CloudWatch Logs resources. For example, you can create policies that prevent identities outside your organization from accessing these resources, helping you build a https://aws.amazon.com/identity/data-perimeters-on-aws/ and enforce baseline security standards across your AWS environment. RCPs are available in all AWS commercial Regions and AWS GovCloud (US) Regions. To learn more about RCPs and view the full list of supported AWS services, visit the https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html in the AWS Organizations User Guide.

AWS expands Resource Control Policies support for Cognito and CloudWatch Logs

AWS Resource Control Policies (RCPs) now provide support for aws.amazon.com/pm/cognito/

#AWS #AmazonCognito #AmazonCloudwatchLogs #AwsGovcloudUs

AWS expands Resource Control Policies support for Cognito and CloudWatch Logs AWS Resource Control Policies (RCPs) now provide support for Amazon Cognito and Amazon CloudWatch Logs. Resource control policies (RCPs) are a type of organization policy that you can use to manage permissions in your organization. RCPs offer central control over the maximum available permissions for resources in your organization. With this expansion, you can now use RCPs to manage permissions for Amazon Cognito and Amazon CloudWatch Logs resources. For example, you can create policies that prevent identities outside your organization from accessing these resources, helping you build a data perimeter and enforce baseline security standards across your AWS environment. RCPs are available in all AWS commercial Regions and AWS GovCloud (US) Regions. To learn more about RCPs and view the full list of supported AWS services, visit the Resource control policies (RCPs) documentation in the AWS Organizations User Guide.

🆕 AWS expands Resource Control Policies to manage permissions for Amazon Cognito and CloudWatch Logs, offering central control over resource access and enforcing security standards across your organization. Available in all AWS regions.

#AWS #AmazonCognito #AmazonCloudwatchLogs #AwsGovcloudUs

Amazon CloudWatch now supports deletion protection for logs Amazon CloudWatch now offers configuring deletion protection on your CloudWatch log groups, helping customers safeguard their critical logging data from accidental or unintended deletion. This feature provides an additional layer of protection for logs maintaining audit trails, compliance records, and operational logs that must be preserved. With deletion protection enabled, administrators can prevent unintended deletions of their most important log groups. Once enabled, log groups cannot be deleted until the protection is explicitly turned off, helping safeguard critical operational, security, and compliance data. This protection is particularly valuable for preserving audit logs and production application logs needed for troubleshooting and analysis. Log group deletion protection is available in all https://aws.amazon.com/about-aws/global-infrastructure/regions_az/ You can enable deletion protection during log group creation or on existing log groups using the Amazon CloudWatch console, AWS Command Line Interface (AWS CLI), AWS Cloud Development Kit (AWS CDK), and AWS SDKs. For more information, visit the https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/Working-with-log-groups-and-streams.html..

Amazon CloudWatch now supports deletion protection for logs

Amazon CloudWatch now offers configuring deletion protection on your CloudWatch log groups, helping customers safeguard their critical logging data from accidental or unintended deletion. This feature provi...

#AWS #AmazonCloudwatchLogs

Amazon CloudWatch now supports deletion protection for logs Amazon CloudWatch now offers configuring deletion protection on your CloudWatch log groups, helping customers safeguard their critical logging data from accidental or unintended deletion. This feature provides an additional layer of protection for logs maintaining audit trails, compliance records, and operational logs that must be preserved. With deletion protection enabled, administrators can prevent unintended deletions of their most important log groups. Once enabled, log groups cannot be deleted until the protection is explicitly turned off, helping safeguard critical operational, security, and compliance data. This protection is particularly valuable for preserving audit logs and production application logs needed for troubleshooting and analysis. Log group deletion protection is available in all AWS commercial Regions. You can enable deletion protection during log group creation or on existing log groups using the Amazon CloudWatch console, AWS Command Line Interface (AWS CLI), AWS Cloud Development Kit (AWS CDK), and AWS SDKs. For more information, visit the Amazon CloudWatch Logs User Guide..

🆕 Amazon CloudWatch now supports deletion protection for log groups, safeguarding critical logs from accidental deletion. Available in all regions, it can be enabled via console, CLI, CDK, or SDKs, ensuring audit trails and compliance records are preserved.

#AWS #AmazonCloudwatchLogs

Amazon CloudWatch now supports scheduled queries in Logs Insights Amazon CloudWatch Logs now supports automatically running Logs Insights queries on a recurring schedule for your log analysis needs. With scheduled queries, you can now automate log analysis tasks and deliver query results to Amazon S3 and Amazon EventBridge. With today's launch, you can track trends, monitor key operational metrics, and detect anomalies without needing to manually re-run queries or maintain custom automation. This feature makes it easier to maintain continuous visibility into your applications and infrastructure, streamline operational workflows, and ensure consistent insight generation at scale. For example, you can setup scheduled queries for your weekly audit reporting. The query results can also be stored in Amazon S3 for analysis, or trigger incident response workflows through Amazon EventBridge. The feature supports all CloudWatch Logs Insights query languages and helps teams improve operational efficiency by eliminating manual query executions. Scheduled queries is available in US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), and South America (São Paulo). You can configure a scheduled query using the Amazon CloudWatch console, AWS Command Line Interface (AWS CLI), AWS Cloud Development Kit (AWS CDK), and AWS SDKs. For more information, visit the https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/ScheduledQueries.html.

Amazon CloudWatch now supports scheduled queries in Logs Insights

Amazon CloudWatch Logs now supports automatically running Logs Insights queries on a recurring schedule for your log analysis needs. With scheduled queries, you can now automate log analysis tasks and...

#AWS #AmazonCloudwatchLogs

Amazon CloudWatch now supports scheduled queries in Logs Insights Amazon CloudWatch Logs now supports automatically running Logs Insights queries on a recurring schedule for your log analysis needs. With scheduled queries, you can now automate log analysis tasks and deliver query results to Amazon S3 and Amazon EventBridge. With today's launch, you can track trends, monitor key operational metrics, and detect anomalies without needing to manually re-run queries or maintain custom automation. This feature makes it easier to maintain continuous visibility into your applications and infrastructure, streamline operational workflows, and ensure consistent insight generation at scale. For example, you can setup scheduled queries for your weekly audit reporting. The query results can also be stored in Amazon S3 for analysis, or trigger incident response workflows through Amazon EventBridge. The feature supports all CloudWatch Logs Insights query languages and helps teams improve operational efficiency by eliminating manual query executions. Scheduled queries is available in US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), and South America (São Paulo). You can configure a scheduled query using the Amazon CloudWatch console, AWS Command Line Interface (AWS CLI), AWS Cloud Development Kit (AWS CDK), and AWS SDKs. For more information, visit the Amazon CloudWatch documentation.

🆕 Amazon CloudWatch now supports scheduled Logs Insights queries for automated log analysis, delivering results to S3 and EventBridge. Available in multiple regions, it helps maintain continuous visibility and operational efficiency.

#AWS #AmazonCloudwatchLogs

Amazon CloudWatch Agent adds support for Windows Event Log Filters Amazon CloudWatch agent has added support for configurable Windows Event log filters. This new feature allows customers to selectively collect and send system and application events to CloudWatch from Windows hosts running on Amazon EC2 or on-premises. The addition of customizable filters helps customers to focus on events that meet specific criteria, streamlining log management and analysis. Using this new functionality of the CloudWatch agent, you can define filter criteria for each Windows Event log stream in the agent configuration file. The filtering options include event levels, event IDs, and regular expressions to either "include" or "exclude" text within events. The agent evaluates each log event against your defined filter criteria to determine whether it should be sent to CloudWatch. Events that don't match your criteria are discarded. Windows event filters help you to manage your log ingestion by processing only the events you need, such as those containing specific error codes, while excluding verbose or unwanted log entries. Amazon CloudWatch Agent is available in all commercial AWS Regions, and the AWS GovCloud (US) Regions. To get started, see https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-Configuration-File-Details.html in the Amazon CloudWatch User Guide.

Amazon CloudWatch Agent adds support for Windows Event Log Filters

Amazon CloudWatch agent has added support for configurable Windows Event log filters. This new feature allows customers to selectively collect and send system and app...

#AWS #AwsGovcloudUs #AmazonCloudwatch #AmazonCloudwatchLogs

Amazon CloudWatch Agent adds support for Windows Event Log Filters Amazon CloudWatch agent has added support for configurable Windows Event log filters. This new feature allows customers to selectively collect and send system and application events to CloudWatch from Windows hosts running on Amazon EC2 or on-premises. The addition of customizable filters helps customers to focus on events that meet specific criteria, streamlining log management and analysis. Using this new functionality of the CloudWatch agent, you can define filter criteria for each Windows Event log stream in the agent configuration file. The filtering options include event levels, event IDs, and regular expressions to either "include" or "exclude" text within events. The agent evaluates each log event against your defined filter criteria to determine whether it should be sent to CloudWatch. Events that don't match your criteria are discarded. Windows event filters help you to manage your log ingestion by processing only the events you need, such as those containing specific error codes, while excluding verbose or unwanted log entries. Amazon CloudWatch Agent is available in all commercial AWS Regions, and the AWS GovCloud (US) Regions. To get started, see Create or Edit the CloudWatch Agent Configuration File in the Amazon CloudWatch User Guide.

🆕 Amazon CloudWatch Agent now supports Windows Event Log Filters, allowing selective collection of specific events from Windows hosts, streamlining log management and analysis. Available in all commercial AWS Regions and AWS GovCloud (US…

#AWS #AwsGovcloudUs #AmazonCloudwatch #AmazonCloudwatchLogs

Amazon CloudWatch launches Cross-Account and Cross-Region Log Centralization Amazon CloudWatch now offers cross-account and cross-region log centralization, allowing customers to copy log data from multiple AWS accounts and regions into a single destination account. This capability seamlessly integrates with AWS Organizations, enabling efficient aggregation of logs from workloads that span multiple accounts and regions into a single account without the need to manage custom solutions. The log centralization feature provides the ability to scope the centralization rules to copy log data from their entire organization, specific organizational units, or selected accounts into a single account. To maintain source context and data lineage, log events are enriched with new system fields (@aws.account and @aws.region) that identify the original source account and region. Additional capabilities include selective log group copying, automatic merging of same-named log groups in the destination account, and optional backup region setup, simplifying centralized log management. Log centralization is available in US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), and South America (São Paulo). To learn more, visit the https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs_Centralization.html. Customers can centralize one copy of logs for free. Additional copies are charged at $0.05/GB of logs centralized (the backup region feature is considered an additional copy). For details, visit the https://aws.amazon.com/cloudwatch/pricing/ page.

Amazon CloudWatch launches Cross-Account and Cross-Region Log Centralization

Amazon CloudWatch now offers cross-account and cross-region log centralization, allowing customers to copy log data from multiple AWS accounts and regions into a single de...

#AWS #AmazonCloudwatchLogs #AmazonCloudwatch

Amazon CloudWatch launches Cross-Account and Cross-Region Log Centralization Amazon CloudWatch now offers cross-account and cross-region log centralization, allowing customers to copy log data from multiple AWS accounts and regions into a single destination account. This capability seamlessly integrates with AWS Organizations, enabling efficient aggregation of logs from workloads that span multiple accounts and regions into a single account without the need to manage custom solutions. The log centralization feature provides the ability to scope the centralization rules to copy log data from their entire organization, specific organizational units, or selected accounts into a single account. To maintain source context and data lineage, log events are enriched with new system fields (@aws.account and @aws.region) that identify the original source account and region. Additional capabilities include selective log group copying, automatic merging of same-named log groups in the destination account, and optional backup region setup, simplifying centralized log management. Log centralization is available in US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), and South America (São Paulo). To learn more, visit the Amazon CloudWatch documentation. Customers can centralize one copy of logs for free. Additional copies are charged at $0.05/GB of logs centralized (the backup region feature is considered an additional copy). For details, visit the CloudWatch Pricing page.

🆕 Amazon CloudWatch centralizes logs across accounts and regions, integrating with AWS Organizations. Free centralization, $0.05/GB for extra copies. Available in multiple regions. Pricing details on CloudWatch Pricing page.

#AWS #AmazonCloudwatchLogs #AmazonCloudwatch

Amazon CloudWatch Logs Insights launches Query Results Summarization and OpenSearch PPL enhancements Amazon CloudWatch Logs Insights launches Query Results Summarization and OpenSearch PPL enhancements to help accelerate your logs analysis. The new logs summarizer generates a natural language summary of the query results, providing users with clear, actionable insights. Interpreting log entries can be time-consuming and this natural language summarization capability transforms complex query results into clear, concise summaries that help you quickly identify issues and gain actionable insights from your log data. With CloudWatch Logs Insights, you can interactively search and analyze your logs with Logs Insights query language, OpenSearch Service Piped Processing Language (PPL), and OpenSearch Service Structured Query Language (SQL). Customers using OpenSearch PPL can now analyze their logs more efficiently with new PPL commands and functions such as JOIN, SubQuery, Fillnull, Expand, Flatten, Cidrmatch and JSON functions. These new capabilities help accelerate your troubleshooting. For example, you can use subqueries to find those services which have more than 20 errors in the last day using an inner query, and then use the results of the inner query to get the average response times of those services from a different log group. The logs summarizer is available in the US East (N. Virginia) region. OpenSearch PPL query enhancements are available in regions where https://docs.aws.amazon.com/opensearch-service/latest/developerguide/direct-query-s3.html#direct-query-cloudwatch-logs-regions-table is available. To learn about the log summarizer in CloudWatch Logs Insights, visit the Amazon CloudWatch Logs https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs-Insights-Query-Results-Summary.html. To learn about the new PPL commands and functions, visit the CloudWatch Logs https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CWL_AnalyzeLogData_PPL.html.

Amazon CloudWatch Logs Insights launches Query Results Summarization and OpenSearch PPL enhancements

Amazon CloudWatch Logs Insights launches Query Results Summarization and OpenSearch PPL enhancements to help accelerate your logs analysis.

Th...

#AWS #AmazonCloudwatchLogs #AmazonCloudwatch

Amazon CloudWatch Logs Insights launches Query Results Summarization and OpenSearch PPL enhancements Amazon CloudWatch Logs Insights launches Query Results Summarization and OpenSearch PPL enhancements to help accelerate your logs analysis. The new logs summarizer generates a natural language summary of the query results, providing users with clear, actionable insights. Interpreting log entries can be time-consuming and this natural language summarization capability transforms complex query results into clear, concise summaries that help you quickly identify issues and gain actionable insights from your log data. With CloudWatch Logs Insights, you can interactively search and analyze your logs with Logs Insights query language, OpenSearch Service Piped Processing Language (PPL), and OpenSearch Service Structured Query Language (SQL). Customers using OpenSearch PPL can now analyze their logs more efficiently with new PPL commands and functions such as JOIN, SubQuery, Fillnull, Expand, Flatten, Cidrmatch and JSON functions. These new capabilities help accelerate your troubleshooting. For example, you can use subqueries to find those services which have more than 20 errors in the last day using an inner query, and then use the results of the inner query to get the average response times of those services from a different log group. The logs summarizer is available in the US East (N. Virginia) region. OpenSearch PPL query enhancements are available in regions where OpenSearch Service direct query is available. To learn about the log summarizer in CloudWatch Logs Insights, visit the Amazon CloudWatch Logs documentation. To learn about the new PPL commands and functions, visit the CloudWatch Logs documentation.

🆕 Amazon CloudWatch Logs Insights boosts log analysis with Query Results Summarization and OpenSearch PPL enhancements, including natural language insights and new JOIN and SubQuery commands. Available in US East (N. Virginia) and OpenSearch regions.

#AWS #AmazonCloudwatchLogs #AmazonCloudwatch

AWS Toolkit for Visual Studio Code now includes Amazon CloudWatch Logs Live Tail AWS Toolkit for Visual Studio Code now includes Amazon CloudWatch Logs Live Tail, an interactive log streaming and analytics capability which provides real-time visibility into your logs, making it easier to develop and troubleshoot your serverless applications. The Toolkit for VS Code is an open-source extension for the Visual Studio Code (VS Code) editor. This extension makes it easier for developers to develop, debug locally, and deploy serverless applications that use AWS. This new integration brings the power of Live Tail directly into the VS Code Command Palette. CloudWatch log events can now be streamed in the VS Code Editor as they are ingested in real-time. You can search, filter, and highlight log events of interest, to aid and accelerate troubleshooting, investigations, and root cause analysis. Amazon CloudWatch Logs Live Tail for AWS Toolkit for Visual Studio Code is available in all AWS Commercial regions. To learn more, please visit the https://docs.aws.amazon.com/toolkit-for-vscode/latest/userguide/cloudwatch-livetail.html. For pricing details, check https://aws.amazon.com/cloudwatch/pricing/.  

AWS Toolkit for Visual Studio Code now includes Amazon CloudWatch Logs Live Tail

AWS Toolkit for Visual Studio Code now includes Amazon CloudWatch Logs Live Tail, an interactive log streaming and analytics capability ...

#AWS #AwsToolkitForVisualStudioCode #AmazonCloudwatch #AmazonCloudwatchLogs

AWS Toolkit for Visual Studio Code now includes Amazon CloudWatch Logs Live Tail AWS Toolkit for Visual Studio Code now includes Amazon CloudWatch Logs Live Tail, an interactive log streaming and analytics capability which provides real-time visibility into your logs, making it easier to develop and troubleshoot your serverless applications. The Toolkit for VS Code is an open-source extension for the Visual Studio Code (VS Code) editor. This extension makes it easier for developers to develop, debug locally, and deploy serverless applications that use AWS. This new integration brings the power of Live Tail directly into the VS Code Command Palette. CloudWatch log events can now be streamed in the VS Code Editor as they are ingested in real-time. You can search, filter, and highlight log events of interest, to aid and accelerate troubleshooting, investigations, and root cause analysis. Amazon CloudWatch Logs Live Tail for AWS Toolkit for Visual Studio Code is available in all AWS Commercial regions. To learn more, please visit the documentation. For pricing details, check Amazon CloudWatch Pricing.

🆕 AWS Toolkit for Visual Studio Code now includes Amazon CloudWatch Logs Live Tail

#AWS #AwsToolkitForVisualStudioCode #AmazonCloudwatch #AmazonCloudwatchLogs

Amazon CloudWatch launches full visibility into application transactions AWS announces the general availability of an enhanced search and analytics experience in CloudWatch Application Signals. This feature empowers developers and on-call engineers with https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Transaction-Search.htmlhttps://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Transaction-Search.html, which are the building blocks of distributed traces that capture detailed interactions between users and various application components. This feature offers 3 core benefits. First, developers can answer any questions related to application performance or end-user impact through an interactive visual editor and enhancements to Logs Insights queries. They can correlate spans with end-user issues using attributes like customer name or order number. With the new JSON parse and unnest functions in Logs Insights, they can link transactions to business events such as failed payments and troubleshoot. Second, developers can diagnose rarely occurring issues, such as p99 latency spikes in APIs, with the enhanced troubleshooting capabilities in Amazon CloudWatch Application Signals that correlates application metrics with comprehensive transaction spans. Finally, CloudWatch Logs offers advanced features for transaction spans, including data masking, forwarding via subscription filters, and metric extraction. You can enable these capabilities for existing spans sent to X-Ray or by sending spans to a new OTLP (OpenTelemetry Protocol) endpoint for traces. This allows you to enhance your observability while maintaining flexibility in your setup. You can search and analyze spans in all regions where https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Sections.html. A new pricing option is also available , encompassing Application Signals, X-Ray traces, and complete visibility into transaction spans - see https://aws.amazon.com/cloudwatch/pricing/. Refer to https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Transaction-Search.html for more details.  

Amazon CloudWatch launches full visibility into application transactions

AWS announces the general availability of an enhanced search and analytics experience in CloudWatch Application Signals. This feature empowers developers and on-call engineers...

#AWS #AmazonCloudwatchLogs #AmazonCloudwatch

Amazon CloudWatch launches full visibility into application transactions AWS announces the general availability of an enhanced search and analytics experience in CloudWatch Application Signals. This feature empowers developers and on-call engineers with complete visibility into application transaction spans, which are the building blocks of distributed traces that capture detailed interactions between users and various application components. This feature offers 3 core benefits. First, developers can answer any questions related to application performance or end-user impact through an interactive visual editor and enhancements to Logs Insights queries. They can correlate spans with end-user issues using attributes like customer name or order number. With the new JSON parse and unnest functions in Logs Insights, they can link transactions to business events such as failed payments and troubleshoot. Second, developers can diagnose rarely occurring issues, such as p99 latency spikes in APIs, with the enhanced troubleshooting capabilities in Amazon CloudWatch Application Signals that correlates application metrics with comprehensive transaction spans. Finally, CloudWatch Logs offers advanced features for transaction spans, including data masking, forwarding via subscription filters, and metric extraction. You can enable these capabilities for existing spans sent to X-Ray or by sending spans to a new OTLP (OpenTelemetry Protocol) endpoint for traces. This allows you to enhance your observability while maintaining flexibility in your setup. You can search and analyze spans in all regions where Application Signals is available. A new pricing option is also available , encompassing Application Signals, X-Ray traces, and complete visibility into transaction spans - see Amazon CloudWatch pricing. Refer to documentation for more details.

🆕 Amazon CloudWatch launches full visibility into application transactions

#AWS #AmazonCloudwatchLogs #AmazonCloudwatch

Amazon CloudWatch Logs announces field indexes and enhanced log group selection in Logs Insights Amazon CloudWatch Logs introduces field indexes and enhanced log group selection to accelerate log analysis. Now, you can index critical log attributes like requestId and transactionId to accelerate query performance and scan relevant indexed data. This means faster troubleshooting, and easier identification of trends. You can create up to 20 field indexes per log group, and once defined, all future logs matching the defined fields will remain indexed for up to 30 days. Additionally, https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AnalyzingLogData.html now supports querying up to 10,000 log groups, across one or more accounts linked via https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Unified-Cross-Account.html. Customers using field indexes, will benefit from faster query execution times while searching across vast amounts of logs. CloudWatch Logs Insights queries using “filter field = value” syntax will automatically leverage indexes, when available. When combined with enhanced log group selection, customers can now gain faster insights across a much larger set of logs in Logs Insights. Customers can select up to 10,000 log groups via either log group prefix or "All" log groups option. To further optimize query performance and costs, customers can use the new "filterIndex" command to limit queries to indexed data only. Field indexes are available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where CloudWatch Logs is available and are included as part of standard log class ingestion at no additional cost. To get started, define index policy at account level or per log-group level within AWS console, or programmatically via API/CLI. See https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs-Field-Indexing.html to learn more about field indexes.  

Amazon CloudWatch Logs announces field indexes and enhanced log group selection in Logs Insights

Amazon CloudWatch Logs introduces field indexes and enhanced log group selection to accelerate log analysis. Now, you can index critical log attributes...

#AWS #AmazonCloudwatch #AmazonCloudwatchLogs

Amazon CloudWatch Logs launches the ability to transform and enrich logs Amazon CloudWatch Logs announces log transformation and enrichment to improve log analytics at scale with consistent, and context-rich format. Customers can add structure to their logs using pre-configured templates for common AWS services such as AWS Web Application Firewall (WAF), Route53, or build custom transformers with native parsers such as Grok. Customers can also rename existing attributes and add additional metadata to their logs such as accountId, and region. Logs emitted from various sources vary widely in format and attribute names, which makes analysis across sources cumbersome. With today’s launch, customers can simplify their log analytics experience by transforming all their logs into a standardized JSON structure. Transformed logs can be leveraged to accelerate analytics experience usinghttps://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs-Field-Indexing.html, discovered fields in https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AnalyzingLogData.html, provide flexibility in alarming using metric filters and forwarding via subscription filters. Customers can manage log transformations natively within CloudWatch without needing to setup complex pipelines. Log transformation and enrichment capability is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/, and included with existing Standard log class ingestion price. Logs Store (Archival) costs will be based on log size after transformation, which may exceed the original log volume. With a few clicks in the Amazon CloudWatch Console, customers can configure transformers at log group level. Alternatively, customers can setup transformers at account, or log group level using AWS Command Line Interface (AWS CLI), AWS CloudFormation, AWS Cloud Development Kit (AWS CDK), and AWS SDKs. Read the https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch-Logs-Transformation.html to learn more about this capability.  

Amazon CloudWatch Logs launches the ability to transform and enrich logs

Amazon CloudWatch Logs announces log transformation and enrichment to improve log analytics at scale with consistent, and context-rich format. Customers can add structure to their logs using pr...

#AWS #AmazonCloudwatchLogs

Amazon CloudWatch Logs announces field indexes and enhanced log group selection in Logs Insights Amazon CloudWatch Logs introduces field indexes and enhanced log group selection to accelerate log analysis. Now, you can index critical log attributes like requestId and transactionId to accelerate query performance and scan relevant indexed data. This means faster troubleshooting, and easier identification of trends. You can create up to 20 field indexes per log group, and once defined, all future logs matching the defined fields will remain indexed for up to 30 days. Additionally, CloudWatch Logs Insights now supports querying up to 10,000 log groups, across one or more accounts linked via cross-account observability. Customers using field indexes, will benefit from faster query execution times while searching across vast amounts of logs. CloudWatch Logs Insights queries using “filter field = value” syntax will automatically leverage indexes, when available. When combined with enhanced log group selection, customers can now gain faster insights across a much larger set of logs in Logs Insights. Customers can select up to 10,000 log groups via either log group prefix or "All" log groups option. To further optimize query performance and costs, customers can use the new "filterIndex" command to limit queries to indexed data only. Field indexes are available in all AWS Regions where CloudWatch Logs is available and are included as part of standard log class ingestion at no additional cost. To get started, define index policy at account level or per log-group level within AWS console, or programmatically via API/CLI. See documentation to learn more about field indexes.

🆕 Amazon CloudWatch Logs announces field indexes and enhanced log group selection in Logs Insights

#AWS #AmazonCloudwatch #AmazonCloudwatchLogs

Amazon CloudWatch Logs launches the ability to transform and enrich logs Amazon CloudWatch Logs announces log transformation and enrichment to improve log analytics at scale with consistent, and context-rich format. Customers can add structure to their logs using pre-configured templates for common AWS services such as AWS Web Application Firewall (WAF), Route53, or build custom transformers with native parsers such as Grok. Customers can also rename existing attributes and add additional metadata to their logs such as accountId, and region. Logs emitted from various sources vary widely in format and attribute names, which makes analysis across sources cumbersome. With today’s launch, customers can simplify their log analytics experience by transforming all their logs into a standardized JSON structure. Transformed logs can be leveraged to accelerate analytics experience using field indexes, discovered fields in CloudWatch Logs Insights, provide flexibility in alarming using metric filters and forwarding via subscription filters. Customers can manage log transformations natively within CloudWatch without needing to setup complex pipelines. Log transformation and enrichment capability is available in all AWS Commercial Regions, and included with existing Standard log class ingestion price. Logs Store (Archival) costs will be based on log size after transformation, which may exceed the original log volume. With a few clicks in the Amazon CloudWatch Console, customers can configure transformers at log group level. Alternatively, customers can setup transformers at account, or log group level using AWS Command Line Interface (AWS CLI), AWS CloudFormation, AWS Cloud Development Kit (AWS CDK), and AWS SDKs. Read the documentation to learn more about this capability.

🆕 Amazon CloudWatch Logs launches the ability to transform and enrich logs

#AWS #AmazonCloudwatchLogs