2020-01-08 13:28:43 +00:00
|
|
|
// Copyright 2020 The Prometheus Authors
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
//
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
//
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
// limitations under the License.
|
|
|
|
|
|
|
|
package logging
|
|
|
|
|
|
|
|
import (
|
fix!: stop unbounded memory usage from query log
Resolves: #15433
When I converted prometheus to use slog in #14906, I update both the
`QueryLogger` interface, as well as how the log calls to the
`QueryLogger` were built up in `promql.Engine.exec()`. The backing
logger for the `QueryLogger` in the engine is a
`util/logging.JSONFileLogger`, and it's implementation of the `With()`
method updates the logger the logger in place with the new keyvals added
onto the underlying slog.Logger, which means they get inherited onto
everything after. All subsequent calls to `With()`, even in later
queries, would continue to then append on more and more keyvals for the
various params and fields built up in the logger. In turn, this causes
unbounded growth of the logger, leading to increased memory usage, and
in at least one report was the likely cause of an OOM kill. More
information can be found in the issue and the linked slack thread.
This commit does a few things:
- It was referenced in feedback in #14906 that it would've been better
to not change the `QueryLogger` interface if possible, this PR
proposes changes that bring it closer to alignment with the pre-3.0
`QueryLogger` interface contract
- reverts `promql.Engine.exec()`'s usage of the query logger to the
pattern of building up an array of args to pass at once to the end log
call. Avoiding the repetitious calls to `.With()` are what resolve the
issue with the logger growth/memory usage.
- updates the scrape failure logger to use the update `QueryLogger`
methods in the contract.
- updates tests accordingly
- cleans up unused methods
Builds and passes tests successfully. Tested locally and confirmed I
could no longer reproduce the issue/it resolved the issue.
Signed-off-by: TJ Hoplock <t.hoplock@gmail.com>
2024-11-23 19:20:37 +00:00
|
|
|
"context"
|
2022-06-27 16:16:58 +00:00
|
|
|
"fmt"
|
2024-09-10 01:41:53 +00:00
|
|
|
"log/slog"
|
2020-01-08 13:28:43 +00:00
|
|
|
"os"
|
|
|
|
|
2024-09-10 01:41:53 +00:00
|
|
|
"github.com/prometheus/common/promslog"
|
2020-01-08 13:28:43 +00:00
|
|
|
)
|
|
|
|
|
2024-09-10 01:41:53 +00:00
|
|
|
// JSONFileLogger represents a logger that writes JSON to a file. It implements the promql.QueryLogger interface.
|
2020-01-08 13:28:43 +00:00
|
|
|
type JSONFileLogger struct {
|
2024-09-10 01:41:53 +00:00
|
|
|
logger *slog.Logger
|
2020-01-08 13:28:43 +00:00
|
|
|
file *os.File
|
|
|
|
}
|
|
|
|
|
|
|
|
// NewJSONFileLogger returns a new JSONFileLogger.
|
|
|
|
func NewJSONFileLogger(s string) (*JSONFileLogger, error) {
|
|
|
|
if s == "" {
|
|
|
|
return nil, nil
|
|
|
|
}
|
|
|
|
|
2021-10-22 08:06:44 +00:00
|
|
|
f, err := os.OpenFile(s, os.O_APPEND|os.O_CREATE|os.O_WRONLY, 0o666)
|
2020-01-08 13:28:43 +00:00
|
|
|
if err != nil {
|
2024-09-10 01:41:53 +00:00
|
|
|
return nil, fmt.Errorf("can't create json log file: %w", err)
|
2020-01-08 13:28:43 +00:00
|
|
|
}
|
|
|
|
|
2024-09-10 01:41:53 +00:00
|
|
|
jsonFmt := &promslog.AllowedFormat{}
|
|
|
|
_ = jsonFmt.Set("json")
|
2020-01-08 13:28:43 +00:00
|
|
|
return &JSONFileLogger{
|
2024-09-10 01:41:53 +00:00
|
|
|
logger: promslog.New(&promslog.Config{Format: jsonFmt, Writer: f}),
|
2020-01-08 13:28:43 +00:00
|
|
|
file: f,
|
|
|
|
}, nil
|
|
|
|
}
|
|
|
|
|
2024-09-10 01:41:53 +00:00
|
|
|
// Close closes the underlying file. It implements the promql.QueryLogger interface.
|
2020-01-08 13:28:43 +00:00
|
|
|
func (l *JSONFileLogger) Close() error {
|
|
|
|
return l.file.Close()
|
|
|
|
}
|
|
|
|
|
2024-09-10 01:41:53 +00:00
|
|
|
// With calls the `With()` method on the underlying `log/slog.Logger` with the
|
|
|
|
// provided msg and args. It implements the promql.QueryLogger interface.
|
|
|
|
func (l *JSONFileLogger) With(args ...any) {
|
|
|
|
l.logger = l.logger.With(args...)
|
|
|
|
}
|
|
|
|
|
fix!: stop unbounded memory usage from query log
Resolves: #15433
When I converted prometheus to use slog in #14906, I update both the
`QueryLogger` interface, as well as how the log calls to the
`QueryLogger` were built up in `promql.Engine.exec()`. The backing
logger for the `QueryLogger` in the engine is a
`util/logging.JSONFileLogger`, and it's implementation of the `With()`
method updates the logger the logger in place with the new keyvals added
onto the underlying slog.Logger, which means they get inherited onto
everything after. All subsequent calls to `With()`, even in later
queries, would continue to then append on more and more keyvals for the
various params and fields built up in the logger. In turn, this causes
unbounded growth of the logger, leading to increased memory usage, and
in at least one report was the likely cause of an OOM kill. More
information can be found in the issue and the linked slack thread.
This commit does a few things:
- It was referenced in feedback in #14906 that it would've been better
to not change the `QueryLogger` interface if possible, this PR
proposes changes that bring it closer to alignment with the pre-3.0
`QueryLogger` interface contract
- reverts `promql.Engine.exec()`'s usage of the query logger to the
pattern of building up an array of args to pass at once to the end log
call. Avoiding the repetitious calls to `.With()` are what resolve the
issue with the logger growth/memory usage.
- updates the scrape failure logger to use the update `QueryLogger`
methods in the contract.
- updates tests accordingly
- cleans up unused methods
Builds and passes tests successfully. Tested locally and confirmed I
could no longer reproduce the issue/it resolved the issue.
Signed-off-by: TJ Hoplock <t.hoplock@gmail.com>
2024-11-23 19:20:37 +00:00
|
|
|
// Log calls the `Log()` method on the underlying `log/slog.Logger` with the
|
2024-09-10 01:41:53 +00:00
|
|
|
// provided msg and args. It implements the promql.QueryLogger interface.
|
fix!: stop unbounded memory usage from query log
Resolves: #15433
When I converted prometheus to use slog in #14906, I update both the
`QueryLogger` interface, as well as how the log calls to the
`QueryLogger` were built up in `promql.Engine.exec()`. The backing
logger for the `QueryLogger` in the engine is a
`util/logging.JSONFileLogger`, and it's implementation of the `With()`
method updates the logger the logger in place with the new keyvals added
onto the underlying slog.Logger, which means they get inherited onto
everything after. All subsequent calls to `With()`, even in later
queries, would continue to then append on more and more keyvals for the
various params and fields built up in the logger. In turn, this causes
unbounded growth of the logger, leading to increased memory usage, and
in at least one report was the likely cause of an OOM kill. More
information can be found in the issue and the linked slack thread.
This commit does a few things:
- It was referenced in feedback in #14906 that it would've been better
to not change the `QueryLogger` interface if possible, this PR
proposes changes that bring it closer to alignment with the pre-3.0
`QueryLogger` interface contract
- reverts `promql.Engine.exec()`'s usage of the query logger to the
pattern of building up an array of args to pass at once to the end log
call. Avoiding the repetitious calls to `.With()` are what resolve the
issue with the logger growth/memory usage.
- updates the scrape failure logger to use the update `QueryLogger`
methods in the contract.
- updates tests accordingly
- cleans up unused methods
Builds and passes tests successfully. Tested locally and confirmed I
could no longer reproduce the issue/it resolved the issue.
Signed-off-by: TJ Hoplock <t.hoplock@gmail.com>
2024-11-23 19:20:37 +00:00
|
|
|
func (l *JSONFileLogger) Log(ctx context.Context, level slog.Level, msg string, args ...any) {
|
|
|
|
l.logger.Log(ctx, level, msg, args...)
|
2020-01-08 13:28:43 +00:00
|
|
|
}
|