{"id":37113123,"url":"https://github.com/kjansson/yac-p","last_synced_at":"2026-02-16T22:09:46.118Z","repository":{"id":283536065,"uuid":"952084382","full_name":"kjansson/yac-p","owner":"kjansson","description":"An implementation of YACE libraries to remote write Cloudwatch metrics to Prometheus in a serverless configuration","archived":false,"fork":false,"pushed_at":"2025-10-01T13:20:24.000Z","size":1820,"stargazers_count":1,"open_issues_count":5,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-10-25T10:50:05.918Z","etag":null,"topics":["aws","aws-lambda","cloudwatch","prometheus","serverless","yace-exporter"],"latest_commit_sha":null,"homepage":"","language":"Go","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/kjansson.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2025-03-20T17:51:38.000Z","updated_at":"2025-06-18T21:28:19.000Z","dependencies_parsed_at":"2025-05-13T09:40:41.805Z","dependency_job_id":null,"html_url":"https://github.com/kjansson/yac-p","commit_stats":null,"previous_names":["kjansson/yac-p"],"tags_count":25,"template":false,"template_full_name":null,"purl":"pkg:github/kjansson/yac-p","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kjansson%2Fyac-p","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kjansson%2Fyac-p/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kjansson%2Fyac-p/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kjansson%2Fyac-p/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/kjansson","download_url":"https://codeload.github.com/kjansson/yac-p/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kjansson%2Fyac-p/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28421078,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-14T10:47:48.104Z","status":"ssl_error","status_checked_at":"2026-01-14T10:46:19.031Z","response_time":107,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["aws","aws-lambda","cloudwatch","prometheus","serverless","yace-exporter"],"created_at":"2026-01-14T13:21:29.418Z","updated_at":"2026-01-14T13:21:30.035Z","avatar_url":"https://github.com/kjansson.png","language":"Go","readme":"# YAC-p\n\nYAC-p utilizes Go libraries from YACE to collect and convert Cloudwatch metrics into Prometheus format remote write format and writes to your endpoint of choice.  \nIt runs as a Lambda function and only requires AWS managed services to run (You don't have to host anything!).   \n\nhttps://github.com/prometheus-community/yet-another-cloudwatch-exporter\n\n## Purpose\n\nYAC-p fits in wherever you don't want to do metrics scraping to get access to your Cloudwatch metrics in Prometheus.   \nThere are multiple scenarios where push-based metrics collection might be more suitable than pull-based;\n\n- \u003cb\u003eDecentralizing\u003c/b\u003e - When in a multi-account cloud environment with centralized metric collection, keeping the configuration and cost of metrics collection in the scope of the client account simplifies scaling and billing.\n\n- \u003cb\u003eNetwork access\u003c/b\u003e - Scraping through Firewalls or other network access control mechanism can be a hassle. Providing endpoints for push-based metrics delivery simplifies things.\n\n## Features\n\n- \u003cb\u003eNothing to host\u003c/b\u003e - Can run on fully managed AWS infrastructure, Eventbridge + Lambda + Amazon managed Prometheus (Works with your self-hosted Prometheus as well)\n- \u003cb\u003eYACE compatible\u003c/b\u003e - Uses YACE native configuration and its amazing discovery and metric enrichment features\n- \u003cb\u003eManage Prometheus the way you want (or not)\u003c/b\u003e - Authentication options for Amazon Managed Prometheus, self-hosted Prometheus, etc\n- \u003cb\u003eFull cross account functionality\u003c/b\u003e - Collect metrics in one account and store in another. Or collect metrics cross account. Whatever floats your boat. \n- \u003cb\u003eCloser to real-time\u003c/b\u003e - Instead of relying on the timing of an exporter and a scraping job, YAC-p delivers as fresh metrics as you want and Cloudwatch can manage to collect.\n\n## Deployment\n\nYAC-p can be deployed using fully managed services. Using Eventbridge to schedule the YAC-p Lambda function it will deliver AWS Cloudwatch metrics to any Prometheus server, but when using Amazon Managed Prometheus it becomes a fully AWS managed collection process.  \nThe included Terraform example code can deploy everything you need including a Amazon Managed Prometheus workspace.\n\n![Deployment](img/deployment.svg)\n\n## Try it out\n- Write a YACE job config file: [configuration](https://github.com/prometheus-community/yet-another-cloudwatch-exporter/blob/master/docs/configuration.md), or try the included example for EC2\n- Deploy with included Terraform code\n\n## Lambda configuration\nThe included Terraform code will configure the Lambda for you, but if you want to deploy it in your own way there are a few environment variables to set;\n\n```\nPROMETHEUS_REMOTE_WRITE_URL - The URL of the Prometheus remote write endpoint\nPROMETHEUS_REGION - If using AMP, the region needs to be configured\nCONFIG_S3_BUCKET - The S3 bucket where the config file is stored\nCONFIG_S3_PATH - The path of the config file\nAUTH_TYPE - Authentication type to use for the remote write endpoint. Valid options are \"AWS\", \"BASIC\", \"TOKEN. Leave empty if no authentication is required.\nAWS_ROLE_ARN - Role to assume for writing metrics. Used only with Amazon Managed Prometheus when doing cross account remote writing.\nDEBUG - Enables/disables debug logging. Accepts any value accepted by strconv.ParseBool (1, t, T, TRUE, true, True, 0, f, F, FALSE, false, False), empty equals to false.\n```\n\n## Advanced configuration\nConcurrency settings normally passed to YACE via command line flags can be managed through environment variables. Settings are documented here: [Flags](https://github.com/prometheus-community/yet-another-cloudwatch-exporter/blob/master/docs/configuration.md#command-line-flags)\n\nEach flag controlling concurrency has a corresponding environment variable, in screaming snake case with the prefix \"YACE\".  \nExample: the flag \"cloudwatch-concurrency\" can be controlled through ```YACE_CLOUDWATCH_CONCURRENCY```.\n\n## Customization\nGo packages are available (https://pkg.go.dev/github.com/kjansson/yac-p/v3) and can be used for custom applications.\nThe code included in ```cmd``` is for the Lambda implementation and config file storage in S3, but can easily be adapted using custom config file loaders.","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkjansson%2Fyac-p","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fkjansson%2Fyac-p","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkjansson%2Fyac-p/lists"}