Conversation
6d755d9 to
0983159
Compare
|
Request logs still don't belong in application logs. |
0983159 to
bfe8b66
Compare
3f360f6 to
c2aa86c
Compare
|
As stated before in this project, we try not to reinvent the wheel. Given that file rotation is usually a solved problem, I think we can:
|
034b277 to
07e99d1
Compare
That seems like a reasonable approach. |
2a70a3b to
0ba76ab
Compare
1a15436 to
9ff502d
Compare
|
|
I have also added the query log format to the list of things considered unstable so we have the ability to make the format evolve in the future. |
|
Further questions @brian-brazil: Should we add a metric Should we log as INFO in the application log the slow query log activation / deactivation / filepath change ? (could be done as a separated PR) |
Sounds more debug to me offhand.
Makes sense, this may have performance impact. |
brian-brazil
left a comment
There was a problem hiding this comment.
Per the dev summit this should include IP addresses when it's coming from the query API.
Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu>
Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu>
Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu>
Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu>
Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu>
|
Exemple log line: With error: |
Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu>
|
Should we use a dedupe logger for the errors? That would imply to add another logger to the engine, specifically for the query log errors. |
|
Dedupe logger loses us line numbers, and disk filling up is fatal to Prometheus unlike remote storage going away. |
brian-brazil
left a comment
There was a problem hiding this comment.
Just some minor style stuff
Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu>
Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu>
|
Thanks! |
| } | ||
|
|
||
| // SetQueryLogger sets the query logger. | ||
| func (ng *Engine) SetQueryLogger(l QueryLogger) error { |
There was a problem hiding this comment.
Can we just drop this return value? Seems it only returns nil
|
|
||
| # File to which PromQL queries are logged. | ||
| # Reloading the configuration will reopen the file. | ||
| [ query_log_file: <string> ] |
There was a problem hiding this comment.
If I recall correctly we discussed at the devsummit that we should document how to allow people who want to to have this be part of the stdout log stream and have some docs around it. I assume that it's just a matter of setting this to /dev/stdout, I just wonder about stream syncronization.
There was a problem hiding this comment.
Probably best for other docs. Does CON still exist on Windows?
There was a problem hiding this comment.
Querying is for the PromQL language.
It wouldn't be part of the reference docs at all, this is generic Unix/Windows knowledge.
There was a problem hiding this comment.
Should it be a small post on the blog, with example with logrotate etc ?
There was a problem hiding this comment.
(blog post would be published after the release)
There was a problem hiding this comment.
I think a blog with examples for logrotate and stdout sounds like a great idea, or a user guide.
|
On 09 Jan 00:54, Frederic Branczyk wrote:
I think a blog with examples for logrotate and stdout sounds like a great idea, or a user guide.
Oh yes a user guide sounds even better.
|
|
/prombench v2.15.2 |
|
/prombench cancel |
|
Benchmark cancel is in progress. |

It is set in the configuration file to be changed online.
Fixes #1315
Signed-off-by: Julien Pivotto roidelapluie@inuits.eu