Not really. We do have attribution tags which we ...
# 🧶︱general
a
Not really. We do have [attribution tags](https://docs.pinecone.io/integrations/build-integration/attribute-usage-to-your-integration) which we use to track usage from different integrations, but I'm not sure that will be as applicable here. I see you opened the ticket so will get our support team on that. I also noticed in your screnshot that you're getting a 2s from
/indexes/
which is just the control plane listing out the index...and then it returns in 200ms which isn't too bad (would have to look deeper at the index in question to know whether that's intentional or not). However, from the looks of it, you might be connecting to your index by it's name which involves a control plane call first. If that's correct, I'd suggest taking a look [here](https://docs.pinecone.io/guides/optimize/decrease-latency#target-indexes-by-host) to see if you can cut that out of the critical path of your latency. We've also got this broader "[production checklist](https://docs.pinecone.io/guides/production/production-checklist)" which might be heklpful as well (and links to the specific one about latency)