Skip to content
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

Closed
dxniel7402 opened this issue Sep 11, 2023 · 2 comments
Closed

Missing metrics after first-time-install #74

dxniel7402 opened this issue Sep 11, 2023 · 2 comments

Comments

@dxniel7402
Copy link

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:
image

Manager:
image

DataPower: too much, more than documented ...

Analytics:
image

Cert monitoring: Is working as aspected.

Is it possible that I have a configuration error? Have the metrics simply been implemented yet?

trawler:
  frequency: 10
  use_kubeconfig: false
logging: 
  level: debug
  format: json
prometheus:
  port: 63512
  enabled: true
graphite:
  enabled: false
nets:
  datapower:
    enabled: true
    timeout: 5
    username: admin
    namespace: apic
  manager:
    enabled: true
    username: admin
    namespace: apic
    max_frequency: 300
    process_org_metrics: true
    grant_type: password
  analytics:
    enabled: true
    namespace: apic
  certs:
    enabled: true
  product:
    enabled: true
    username: admin
    namespace: apic
@rickymoorhouse
Copy link
Member

Thanks for the bug report - seems there are two key issues:

  • whilst the gateway_peering status code was added, it's not being called in the main loop
  • I have a mistake in the config sample in the docs - where it says product it should say apiconnect

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
@rickymoorhouse
Copy link
Member

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants