Like Prometheus, but for logs.

prometheushacktoberfestgrafanacloudnativeloggingloki

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Elliot Dobson 6a8225d533 lambda-promtail: s3: update log parsing to support NLBs (#7194) ... <!-- Thanks for sending a pull request! Before submitting: 1. Read our CONTRIBUTING.md guide 2. Name your PR as `<Feature Area>: Describe your change`. a. Do not end the title with punctuation. It will be added in the changelog. b. Start with an imperative verb. Example: Fix the latency between System A and System B. c. Use sentence case, not title case. d. Use a complete phrase or sentence. The PR title will appear in a changelog, so help other people understand what your change will be. 3. Rebase your PR if it gets out of sync with main --> **What this PR does / why we need it**: Fixes the filename and timestamp regex for AWS Network Load Balancer (NLB) logs and adds logic to make NLB log timestamps RFC3339 compatible. Also adds a test to check the parsed timestamp is as expected. **Which issue(s) this PR fixes**: Fixes #6455 **Special notes for your reviewer**: <!-- Note about CHANGELOG entries, if a change adds: * an important feature * fixes an issue present in a previous release, * causes a change in operation that would be useful for an operator of Loki to know then please add a CHANGELOG entry. For documentation changes, build changes, simple fixes etc please skip this step. We are attempting to curate a changelog of the most relevant and important changes to be easier to ingest by end users of Loki. Note about the upgrade guide, if this changes: * default configuration values * metric names or label names * changes existing log lines such as the metrics.go query output line * configuration parameters * anything to do with any API * any other change that would require special attention or extra steps to upgrade Please document clearly what changed AND what needs to be done in the upgrade guide. --> **Checklist** - [x] Documentation added - [x] Tests updated - [ ] Is this an important fix or new feature? Add an entry in the `CHANGELOG.md`. - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md` --------- Signed-off-by: Callum Styan <callumstyan@gmail.com> Co-authored-by: Callum Styan <callumstyan@gmail.com>		2 years ago
..
aws	[Docs] Create top level Send data section, part 1 (#10192)	2 years ago
docker-driver	[Docs] Create top level Send data section, part 1 (#10192)	2 years ago
fluentbit	[Docs] Create top level Send data section, part 1 (#10192)	2 years ago
fluentd	[Docs] Create top level Send data section, part 1 (#10192)	2 years ago
k6	[Docs] Create top level Send data section, part 1 (#10192)	2 years ago
lambda-promtail	lambda-promtail: s3: update log parsing to support NLBs (#7194)	2 years ago
logstash	[Docs] Create top level Send data section, part 1 (#10192)	2 years ago
_index.md	[Docs] Create top level Send data section, part 1 (#10192)	2 years ago