Skip to main content

Rate Limiting

The Central Monitoring API implements rate limiting to ensure fair usage and system stability. All API requests are subject to daily rate limits based on your client ID and the routes you've been granted access to.

Default Rate Limits​

All new client IDs are allocated:

  • 100 requests per day per granted route

Rate limits are tracked separately for each route you have access to. For example, if you have access to both /v2/logs/scroll and /v2/workloads/scroll, you get 100 requests per day for each route.

Checking Your Rate Limit​

Every successful API response includes your remaining quota in the response metadata:

{
  "data": {
    // ... response data
  },
  "meta": {
    "api_version": "v2",
    "rate_limit": {
      "daily_remaining": 47
    },
    "request_id": "3a5f1229-ccef-4fcb-be27-98fd88e950c7"
  }
}

Monitor the daily_remaining field to track your usage throughout the day.

Rate Limit Exceeded​

If you exceed your daily rate limit, you'll receive a 429 Too Many Requests response:

{
  "statusCode": 429,
  "body": {
    "error": "Rate limit exceeded"
  }
}

Rate limits reset daily at midnight UTC.

Requesting a Rate Limit Increase​

If your use case requires more than 100 requests per day, you can request an increase by contacting the Central Monitoring support team.

Email Template​

To: CM-Support@accenture.com
Subject: API Rate Limit Increase Request - [Your Client ID]

Hello Central Monitoring Support,

I am requesting a rate limit increase for my API client.

Client ID: [Your Client ID]

Routes Requiring Increase:
- /v2/logs/scroll
- /v2/workloads/batch
[Add all routes you need increased limits for]

Requested Daily Limit: [e.g., 500 requests per day]

Justification:
Explain your use case and why you need the increased limit. Include details such as:
- What you're building/automating
- Expected query frequency
- Business need

Best regards,
[Your Name]
[Your Team/Organization]

What to Include​

When requesting a rate limit increase, make sure to provide:

  1. Client ID: Your API client identifier
  2. Routes: Specific API routes that need increased limits
  3. Requested Limit: The daily request limit you're requesting
  4. Justification: Clear explanation of your use case and why the increase is needed

The support team will review your request and respond with approval or follow-up questions.

Best Practices​

To make the most of your rate limits:

  • Use batch endpoints (/v2/logs/batch, /v2/workloads/batch) for large data retrievals instead of multiple scroll requests
  • Cache responses when appropriate to avoid redundant queries
  • Monitor your usage by tracking the daily_remaining field in responses
  • Schedule queries during off-peak hours if possible
  • Use filters and fields effectively to retrieve only the data you need

Rate Limit Reset​

Rate limits reset daily at 00:00 UTC. Plan your queries accordingly if you're approaching your daily limit.