Skip to content

Commit

Permalink
Merge pull request #175 from heitorlessa/chore/bump-1.6.0
Browse files Browse the repository at this point in the history
chore: bump to 1.6.0
  • Loading branch information
heitorlessa authored Sep 22, 2020
2 parents 0f170c1 + dc74a72 commit aeb52c9
Show file tree
Hide file tree
Showing 3 changed files with 12 additions and 3 deletions.
11 changes: 10 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [1.6.0] - 2020-09-22

### Added
- **Metrics**: Support adding multiple metric values to a metric name
- **Metrics**: Support adding multiple metric values to a single metric name
- **Utilities**: Add new `Validator` utility to validate inbound events and responses using JSON Schema
- **Utilities**: Add new `Event source data classes` utility to easily describe event schema of popular event sources
- **Docs**: Add new `Testing your code` section to both Logger and Metrics page, and content width is now wider
- **Tracer**: Support for automatically disable Tracer when running a Chalice app

### Fixed
- **Docs**: Improve wording on log sampling feature in Logger, and removed duplicate content on main page
- **Utilities**: Remove DeleteMessageBatch API call when there are no messages to delete

## [1.5.0] - 2020-09-04

Expand Down
2 changes: 1 addition & 1 deletion docs/content/core/logger.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -226,7 +226,7 @@ Sampling allows you to set your Logger Log Level as DEBUG based on a percentage

This is useful when you want to troubleshoot an issue, say a sudden increase in concurrency, and you might not have enough information in your logs as Logger log level was understandably set as INFO.

Sampling decision happens at the Logger class initialization, which only happens during a cold start. This means sampling may happen significant more or less than you expect if you have a steady low number of invocations and thus few cold starts.
Sampling decision happens at the Logger class initialization, which only happens during a cold start. This means sampling may happen significantly more or less than you expect if you have a steady low number of invocations and thus few cold starts.

<Note type="info">
If you want Logger to calculate sampling on every invocation, then please open a feature request.
Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[tool.poetry]
name = "aws_lambda_powertools"
version = "1.5.0"
version = "1.6.0"
description = "Python utilities for AWS Lambda functions including but not limited to tracing, logging and custom metric"
authors = ["Amazon Web Services"]
classifiers=[
Expand Down

0 comments on commit aeb52c9

Please sign in to comment.