The log level settings are just activity, headers, payload, so out of the box, no you can't.
However you can use custom code in the API to customise that, of even use custom logstash code to redact out the response bodies if you dont need them.
Bodies are just stored as long strings - they arent parsed, and they considerably increase the overheads in storage and memory on analytics, so unless essential we generally advise against payload storage.
Original Message:
Sent: Mon March 18, 2024 09:55 PM
From: Guo Jun Qiao
Subject: Rate Limiting Setting for Different Consumer Organizations
Hi Chris,
When storing analytic data, is it possible to enable request body and disable response body?
------------------------------
Guo Jun Qiao
------------------------------
Original Message:
Sent: Mon March 18, 2024 08:36 PM
From: Guo Jun Qiao
Subject: Rate Limiting Setting for Different Consumer Organizations
Hi Chris,
Thank you. Let me discuss with team to see if any further questions on this rate limit.
------------------------------
Guo Jun Qiao
Original Message:
Sent: Mon March 18, 2024 04:28 AM
From: Chris Dudley
Subject: Rate Limiting Setting for Different Consumer Organizations
APIC is only going to use its internal list of who is in what consumer org. It is not possible to delegate that to external AD groups. Essentially your external consumer org AD groups are meaningless to APIC and cannot be used for anything directly.
That means you need to make that internal list match your external server - maybe through some kind of cron that runs nightly to make sure that the membership is correct - create new users, remove old ones, etc... That script can use the APIC Provider API/CLI in order to modify the membership of consumer orgs. I'm afraid I don't have any examples, its not something I've ever tried to do.
Remember if you're putting more than 10 users in a consumer org you are probably doing it wrong - consumer orgs only exist to share credentials, so it is a bit of a give away if you have too many users in a single one.
You can always group consumer organizations together into "Groups" which can then be used for setting product visibility.
A reminder - rate limits apply at the application level. A subscription is a link between a given application and a specific product plan.
If you want to raise an RFE for externalising the consumer org membership to AD groups then please do.
------------------------------
Chris Dudley
Original Message:
Sent: Mon March 18, 2024 04:20 AM
From: Guo Jun Qiao
Subject: Rate Limiting Setting for Different Consumer Organizations
Hi Chris,
What do you mean to make the internal membership match what we want? Do you mean match internal membership with Consumer organization AD group?
Is it possible to share some sample scripts to make the internal membership match what we want?
------------------------------
Guo Jun Qiao
Original Message:
Sent: Mon March 18, 2024 02:36 AM
From: Chris Dudley
Subject: Rate Limiting Setting for Different Consumer Organizations
Consumer org membership cannot be externalised to AD groups either.
that must be managed internally inside apic, but you could write scripts to make the internal membership match what you want.
------------------------------
Chris Dudley
Original Message:
Sent: Mon March 18, 2024 02:33 AM
From: Chris Dudley
Subject: Rate Limiting Setting for Different Consumer Organizations
Rate limits are based on application subscriptions. They're not per user or per consumer org.
You could look at creating an application per ad group or something like that, but the apic rate limits would remain per application, you'd need to create the apps per group.
20 consumer orgs is not high, that's tiny, I have more than that on my test system ;-) 20,000 would be a large number of consumer orgs.
Email notifications on rate limits is not currently possible but it's being looked at - I'd suggest raising an rfe.
Id strongly recommend you use apic artifacts such as consumer orgs and apps how they're intended or you'll likely have issues down the line.
eg a consumer org only exists to share application credentials with other people. If you wouldn't tell someone your app keys then you shouldn't be in the same consumer org as that is literally the primary purpose of a consumer org.
------------------------------
Chris Dudley