question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Stackdriver] A maximum of 200 TimeSeries can be written in a single request

See original GitHub issue

Micrometer 1.1.3 Spring Boot 2.1.3.RELEASE

Hi,

We’re encountering this quotas-related error below, should this be handled by Micrometer or by ourselves?

Thanks, Christophe

Error message:

2019-03-28 14:53:01.000  WARN 11949 --- [stackdriver-metrics-publisher] i.m.s.StackdriverMeterRegistry           : failed to send metrics to stackdriver: INVALID_ARGUMENT: Field timeSeries had an invalid value: A maximum of 200 TimeSeries can be written in a single request.

Code sample:

    @KafkaListener(topics = {
        "${kolsquare.ingest.kafka.topic.post.batch.name}",
        "${kolsquare.ingest.kafka.topic.post.stream.name}"
    })
    public void listen(final List<String> payloads) {
        try {
            Metrics.summary("ingest.loader.listener.size.summary").record(payloads.size());

            final List<Post> posts = resolvePosts(payloads);
            postRepository.updatePosts(posts);

            final Set<User> users = resolveUsers(posts);
            userRepository.updateUsers(users);

            Metrics.counter("ingest.loader.listener.success.counter").increment();
        } catch (final Exception e) {
            LOGGER.error(e.getMessage(), e);

            Metrics.counter("ingest.loader.listener.failure.counter").increment();

            throw e;
        } finally {
            Metrics.counter("ingest.loader.listener.total.counter").increment();
        }
    }

References:

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
cbismuthcommented, Apr 3, 2019

Version 1.1.4 solves this issue, thanks @shakuzen for this quick release 👍

0reactions
cbismuthcommented, Mar 29, 2019

I’ve opened a PR #1347.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Quotas and limits - Monitoring - Google Cloud
You can write only one data point for each time series in a request, so this limit also functions as the maximum number...
Read more >
GCP - Logging k8s: Error while sending request to Stackdriver ...
GCP - Logging k8s: Error while sending request to Stackdriver googleapi: Error 400: One or more TimeSeries could not be written · Ask...
Read more >
monitoring.projects.timeSeries.create - Any API
If any time series could not be written, a corresponding failure message is included ... The maximum number of TimeSeries objects per Create...
Read more >
API error: points were written more frequently - Google Groups
One or more TimeSeries could not be written: One or more points were written more frequently than the maximum sampling period configured for...
Read more >
Google Maps Platform Monitoring
In this example, you can see that one API exceeded the limit. When the conditions of an alerting policy are met, Cloud Monitoring...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found