Like Prometheus, but for logs.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
loki/vendor/cloud.google.com/go/internal
renovate[bot] d43b2de1b4
fix(deps): update module github.com/fsouza/fake-gcs-server to v1.47.7 (#13935)
9 months ago
..
detect fix(deps): update module github.com/fsouza/fake-gcs-server to v1.47.7 (#13935) 9 months ago
optional all: update dependencies (#211) 6 years ago
pubsub chore(deps): Update Prometheus in Loki and Promtail (#12245) 1 year ago
trace feat: upgrade prometheus (#13671) 10 months ago
version update vendored cortex and add new replace overrides (#3256) 4 years ago
.repo-metadata-full.json fix(deps): update module github.com/fsouza/fake-gcs-server to v1.47.7 (#13935) 9 months ago
README.md Upgrade Thanos objstore, dskit and other modules (#10366) 2 years ago
annotate.go Update Prometheus dependency to latest release (v2.39.1) (#7425) 3 years ago
gen_info.sh feat: upgrade prometheus (#13671) 10 months ago
retry.go Upgrade Thanos objstore, dskit and other modules (#10366) 2 years ago

README.md

Internal

This directory contains internal code for cloud.google.com/go packages.

.repo-metadata-full.json

.repo-metadata-full.json contains metadata about the packages in this repo. It is generated by internal/gapicgen/generator. It's processed by external tools to build lists of all of the packages.

Don't make breaking changes to the format without consulting with the external tools.

One day, we may want to create individual .repo-metadata.json files next to each package, which is the pattern followed by some other languages. External tools would then talk to pkg.go.dev or some other service to get the overall list of packages and use the .repo-metadata.json files to get the additional metadata required. For now, .repo-metadata-full.json includes everything.

Updating OwlBot SHA

You may want to manually update the which version of the post-processor will be used -- to do this you need to update the SHA in the OwlBot lock file.

See the postprocessor/README for detailed instructions.

Note: OwlBot will eventually open a pull request to update this value if it discovers a new version of the container.