Tags: lablabs/cloudflare-exporter
Tags
Go 1.22 update (#111) * Bump GO to 1.22 * Extending firewall metrics with rule names * Adding account specific rule to firewall metrics * Add Cloudflare Logpush metrics for account and zone * Selector is included in labels Bump chart version * Add Account Label to Metrics This commit adds the Account label to the metrics label list. The Account label provides additional context to the metrics, allowing for better categorization and analysis of data. This change enhances the accuracy and granularity of the metrics collected. - Added Account label to metrics - Improved data categorization and analysis Signed-off-by: Denys Lemeshko <lde@linuxhelp.com.ua> Fix missing label * Add account to labels on logpush events, bump golangci fix golang-ci lint action some golangci-lint fixes * Use cobra and viper as maintained alternatives to namsral/flag library. Add basic tests just make sure you provide .env file with right variables. --------- Co-authored-by: Oleksii Serhiienko <oleksii.serhiienko@getyourguide.com> Co-authored-by: Bhushan Thakur <bhthakur@redhat.com> Co-authored-by: Mark Pierce <mark.pierce@debijenkorf.nl> Co-authored-by: Denys Lemeshko <lde@linuxhelp.com.ua>
Go 1.22 update (#111) * Bump GO to 1.22 * Extending firewall metrics with rule names * Adding account specific rule to firewall metrics * Add Cloudflare Logpush metrics for account and zone * Selector is included in labels Bump chart version * Add Account Label to Metrics This commit adds the Account label to the metrics label list. The Account label provides additional context to the metrics, allowing for better categorization and analysis of data. This change enhances the accuracy and granularity of the metrics collected. - Added Account label to metrics - Improved data categorization and analysis Signed-off-by: Denys Lemeshko <lde@linuxhelp.com.ua> Fix missing label * Add account to labels on logpush events, bump golangci fix golang-ci lint action some golangci-lint fixes * Use cobra and viper as maintained alternatives to namsral/flag library. Add basic tests just make sure you provide .env file with right variables. --------- Co-authored-by: Oleksii Serhiienko <oleksii.serhiienko@getyourguide.com> Co-authored-by: Bhushan Thakur <bhthakur@redhat.com> Co-authored-by: Mark Pierce <mark.pierce@debijenkorf.nl> Co-authored-by: Denys Lemeshko <lde@linuxhelp.com.ua>
Bump alpine from 3.16 to 3.17 (#82) Bumps alpine from 3.16 to 3.17. --- updated-dependencies: - dependency-name: alpine dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Feat: Allow adding annoations to the Deployment (#75) * Feat: Allow adding annoations to the Deployment * Bumping chart version Signed-off-by: David Collom <david.collom@jetstack.io> Signed-off-by: David Collom <david.collom@jetstack.io>
Introduce requests per LB pool metric & fix LB pool health status met… …ric (#65) * fix: Report LB pool health properly The `cloudflare_zone_pool_health_status` metric introduced with goal to report the actual pools health status during the time, regardless if this pool is the selected one or not. The initial implementation uses the `loadBalancingRequestsAdaptiveGroups` type which returns aggregated Load Balancing origin requests with adaptive sampling and contains information only about the selectedPool (Name, Health, AvgRttMs, etc), rather than for all LB pools. This leads on reporthing back the status only of the selectedPool (which normally is always 1) and not the overall status of all LB's pools. According to Cloudflare's documentation about LoadBalancing GraphQL Analytics API[1], the `loadBalancingRequestsAdaptive` schema can be used to fetch analytics about the Raw Load Balancing origin requests with adaptive sampling. These analytics exposes infromation about the selected pool like: * Selected Pool - Name/Health/ID/Average RTT * Session Affinity - Type/Status But it also exposes information about LB's pools and origins regardless the selection decision, like: * Pools ID/Name/Health/Average RTT/Selected * Origins Name/FQDN/Ipv4/Ipv6/Selected The latter metrics can be used to report the health of all pools associated with account's LBs. For this reason, this commit adds the required `loadBalancingRequestsAdaptive` schema struct on the lbResp struct and configures it as the source for the `cloudflare_zone_pool_health_status` metric. 1. https://developers.cloudflare.com/load-balancing/reference/load-balancing-analytics/#graphql-analytics * feat: Add poolRequestsTotal metric This commit introduces a prometheus counter metric about the total number of requests per pool.
Add support for LoadBalancing metrics (#60) * git: Add gitignore file * feat: Export LoadBalancer analytics metrics This commit enables support for exporting LoadBalancer analytics metrics. LoadBalancer's pool health is reported: * 1 -> health * 0 -> unhealthy as long as the number of requests each pool receives from each CFL network location[1] 1. https://developers.cloudflare.com/load-balancing/reference/load-balancing-analytics/#graphql-analytics * feat: Export browser map page views count Export browser_map_page_views_count requests metric
PreviousNext