Package io.micrometer.cloudwatch2

Interface CloudWatchConfig

All Superinterfaces:
io.micrometer.core.instrument.config.MeterRegistryConfig, io.micrometer.core.instrument.push.PushRegistryConfig, io.micrometer.core.instrument.step.StepRegistryConfig
public interface CloudWatchConfig
extends io.micrometer.core.instrument.step.StepRegistryConfig
Configuration for CloudWatch exporting.
Since:
1.2.0

  • Field Summary

    Fields
    Modifier and Type Field Description
    static int MAX_BATCH_SIZE  

  • Method Summary

    Modifier and Type Method Description
    default int batchSize()  
    default boolean highResolution()
    Whether to ship high-resolution metrics to CloudWatch at a higher cost.
    default java.lang.String namespace()  
    default java.lang.String prefix()  
    default io.micrometer.core.instrument.config.validate.Validated<?> validate()  

    Methods inherited from interface io.micrometer.core.instrument.config.MeterRegistryConfig

    get, requireValid

    Methods inherited from interface io.micrometer.core.instrument.push.PushRegistryConfig

    connectTimeout, enabled, numThreads, readTimeout, step

  • Field Details

  • Method Details

    • prefix

      default java.lang.String prefix()
      Specified by:
      prefix in interface io.micrometer.core.instrument.config.MeterRegistryConfig

    • namespace

      default java.lang.String namespace()

    • batchSize

      default int batchSize()
      Specified by:
      batchSize in interface io.micrometer.core.instrument.push.PushRegistryConfig

    • highResolution

      @Incubating(since="1.6.0") default boolean highResolution()
      Whether to ship high-resolution metrics to CloudWatch at a higher cost. By default, if the step interval is less than one minute, we assume that high-resolution metrics are also desired. This is incubating because CloudWatch supports making this decision on a per-metric level. It's believed that deciding on a per-registry level leads to simpler configuration and will be satisfactory in most cases. To only ship a certain subset of metrics at high resolution, two CloudWatchMeterRegistry instances can be configured. One is configured with high-resolution and a MeterFilter.denyUnless(Predicate) filter. The other is configured with low-resolution and a MeterFilter.deny(Predicate) filter. Both use the same predicate.
      Returns:
      The decision about whether to accept higher cost high-resolution metrics.
      Since:
      1.6.0

    • validate

      default io.micrometer.core.instrument.config.validate.Validated<?> validate()
      Specified by:
      validate in interface io.micrometer.core.instrument.config.MeterRegistryConfig
      Specified by:
      validate in interface io.micrometer.core.instrument.push.PushRegistryConfig