Daniel Jaglowski 40b485f08a Update core for v0.90.0 release (#29539) | 1 year ago | |
---|---|---|
.. | ||
internal | 1 year ago | |
testdata | 1 year ago | |
Makefile | 3 years ago | |
README.md | 1 year ago | |
cardinality.md | 1 year ago | |
config.go | 1 year ago | |
config_test.go | 1 year ago | |
doc.go | 1 year ago | |
factory.go | 1 year ago | |
factory_test.go | 1 year ago | |
go.mod | 1 year ago | |
go.sum | 1 year ago | |
metadata.yaml | 1 year ago | |
receiver.go | 1 year ago | |
receiver_test.go | 1 year ago |
Status | |
---|---|
Stability | beta: metrics |
Distributions | contrib, observiq, sumo |
Issues | |
Code Owners | @architjugran, @varunraiko, @kiranmayib |
Google Cloud Spanner enable you to investigate issues with your database by exposing via Total and Top N built-in tables:
Note: Total and Top N built-in tables are used with 1 minute statistics granularity.
The ultimate goal of Google Cloud Spanner Receiver is to collect and transform those statistics into metrics that would be convenient for further analysis by users.
The following configuration example is:
receivers:
googlecloudspanner:
collection_interval: 60s
initial_delay: 1s
top_metrics_query_max_rows: 100
backfill_enabled: true
cardinality_total_limit: 200000
hide_topn_lockstats_rowrangestartkey: false
truncate_text: false
projects:
- project_id: "spanner project 1"
service_account_key: "path to spanner project 1 service account json key"
instances:
- instance_id: "id1"
databases:
- "db11"
- "db12"
- instance_id: "id2"
databases:
- "db21"
- "db22"
- project_id: "spanner project 2"
service_account_key: "path to spanner project 2 service account json key"
instances:
- instance_id: "id3"
databases:
- "db31"
- "db32"
- instance_id: "id4"
databases:
- "db41"
- "db42"
Brief description of configuration properties: