[
https://issues.apache.org/jira/browse/KUDU-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17834448#comment-17834448
]
ASF subversion and git services commented on KUDU-3561:
-------------------------------------------------------
Commit 832690f70ae039daf274744d617332895be8e541 in kudu's branch
refs/heads/branch-1.17.x from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=832690f70 ]
KUDU-3561 skip tablet entities in Prometheus format
Currently, the Prometheus metrics writer outputs only server-level
metrics. Prior to this patch, the Prometheus metrics writer would
output a warning message for every tablet it encounters while iterating
through all the existing metric entities.
This patch addresses the issue: the tablet entries are now silently
skipped, as they should.
I also added a TODO for KUDU-3563 to output tablet-level metrics
in Prometheus format as well.
Change-Id: I618bbc2caab7a8d9812eeaeb67ac42b0293b0654
Reviewed-on: http://gerrit.cloudera.org:8080/21226
Reviewed-by: Mahesh Reddy <mre...@cloudera.com>
Reviewed-by: Abhishek Chennaka <achenn...@cloudera.com>
Tested-by: Alexey Serbin <ale...@apache.org>
(cherry picked from commit dd4e37b445da7f367746fb83d92e21b8dc3d8eb8)
Reviewed-on: http://gerrit.cloudera.org:8080/21231
> Too Many Warning Log: "Entity is not relevant to Prometheus"
> ------------------------------------------------------------
>
> Key: KUDU-3561
> URL: https://issues.apache.org/jira/browse/KUDU-3561
> Project: Kudu
> Issue Type: Bug
> Components: metrics
> Affects Versions: 1.17.0
> Reporter: Liu Lin
> Assignee: Alexey Serbin
> Priority: Major
> Attachments: image-2024-03-30-22-54-28-735.png
>
>
> I encountered the same issue as KUDU-3549, so I recompiled Kudu using the
> master branch.
> Now Prometheus is able to collect metrics from Kudu correctly through the
> /metrics_prometheus endpoint.
> However, I noticed a large number of "Failed to write entity [xxx] as
> Prometheus: Not found: Entity is not relevant to Prometheus" warning logs in
> the Tserver's logs.
> !image-2024-03-30-22-54-28-735.png!
> Could you please confirm if this is a code issue? If not, how can I reduce
> these logs?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
