You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jfrog_rt_service_message_total parameter generates a lot of unnecessary data that has to be stored in our metrics endpoints for no real gain when these lines are difficult to query and somewhat of an antipattern for time series metrics.
Expected solution:
We would propose a replacement or alternative that can be toggled to instead emit categories of log line (SECURITY, ACCESS, GARBAGE COLLECTION) and their severity level (INFO,DEBUG,WARNING etc.) where other methods are being used to obtain high cardinality log lines.
Possible workaround:
Disable the jfrog_rt_service_message_total parameter.
<metric>
name jfrog_rt_service_message_total
type counter
desc artifactory service message
<labels>
host ${hostname}
message ${message}
</labels>
</metric>
The text was updated successfully, but these errors were encountered:
Description:
jfrog_rt_service_message_total parameter generates a lot of unnecessary data that has to be stored in our metrics endpoints for no real gain when these lines are difficult to query and somewhat of an antipattern for time series metrics.
Expected solution:
We would propose a replacement or alternative that can be toggled to instead emit categories of log line (SECURITY, ACCESS, GARBAGE COLLECTION) and their severity level (INFO,DEBUG,WARNING etc.) where other methods are being used to obtain high cardinality log lines.
Possible workaround:
Disable the jfrog_rt_service_message_total parameter.
The text was updated successfully, but these errors were encountered: