Fork me on GitHub
#xtdb
<
2022-02-03
>
tatut07:02:00

btw, just noticed that on page https://docs.xtdb.com/clients/http/ the link "OpenAPI documentation https://xtdb-api-docs.s3.eu-west-1.amazonaws.com/redoc/1.20.0/xtdb-redoc.html." leads to a NoSuchBucket error

refset10:02:39

ah, it looks like we added new link for it at the top of the page (which is up-to-date @ https://docs.xtdb.com/clients/http/openapi/1.20.0) but forgot to remove/fix that link further down, thanks for mentioning it 🙏

tatut08:02:49

high-resolution? (boolean, default false): increase push rate from 1 minute to 1 second... I haven't set it in cloudwatch reporter but I'm still seeing a PutMetricData call every 5 seconds

tatut08:02:17

{ "context": "default", "level": "DEBUG", "logger": "io.github.azagniotov.metrics.reporter.cloudwatch.CloudWatchReporter", "message": "Sent 70 metric datums to CloudWatch. Namespace: xtdb.metrics.cloudwatch, metric data [MetricDatum(MetricName=jvm.buffers.direct.capacity,...long list of metrics ...

tatut08:02:53

^ every 5s, but that seems to include only jvm metrics

tatut08:02:54

I have set :jvm-metrics? to true

tatut09:02:28

looking at the code, it doesn't look like high resolution changes API call rate but sets the storage resolution in the AWS cloudwatch API

tatut10:02:30

the dry-run-report-frequency option affects how often the cloudwatch put request is made (not just dry run mode)

refset10:02:37

I'm not particularly booted-up in this area, but it does seem like our docs on this are missing some important detail - have you tried setting :dry-run-report-frequency?

tatut10:02:22

yes, and verified that it does in fact set the push rate, it is poorly named imo

refset10:02:58

I'll take a note to improve this before the next release :thumbsup: thanks for your patience and for figuring out a workaround in the meantime(!)

👍 1