-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing metrics after first-time-install #74
Comments
Thanks for the bug report - seems there are two key issues:
|
rickymoorhouse
added a commit
that referenced
this issue
Sep 12, 2023
rickymoorhouse
added a commit
that referenced
this issue
Sep 12, 2023
#74 fix: update tests for peering Signed-off-by: Ricky Moorhouse <[email protected]>
rickymoorhouse
added a commit
that referenced
this issue
Sep 12, 2023
#74 fix: update tests for peering Signed-off-by: Ricky Moorhouse <[email protected]>
rickymoorhouse
added a commit
that referenced
this issue
Sep 12, 2023
The gateway peering function fix is now in and v1.8.0 should be shortly available containing that and the custom analytics intervals and I've corrected the README as well Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Simply put, my problem is that I am not seeing the "promised" metrics in Prometheus that are linked here.
I have apiconnect-trawler installed in a cluster on which API Connect is installed in a namespace in my "monitoring" namespace. After some initial problems, it has been running for a week now. Now I wanted to use metrics like apiconnect_health_status or datapower_gateway_peering_primary_info.
API Connect:
Manager:
DataPower: too much, more than documented ...
Analytics:
Cert monitoring: Is working as aspected.
Is it possible that I have a configuration error? Have the metrics simply been implemented yet?
The text was updated successfully, but these errors were encountered: