We are using Splunk Clockify add-on 2.0.1 in a standalone instance and enabled inputs "user" with an API key. After enabling the inputs we could see only 51 users in the search result. The actual count of the user is 70.
- I verified the ta_clockify_add_on_for_splunk_ClockifyUsers.log file and don't see any ERROR/WARN/FAILED messages.
- Is there any restriction to fetching all the user data from the Clockify add-on?
- Do we need to add/update any settings in the input stanza?
- The log collection interval I have set is 60 sec.
Can someone please help me with this?
@Anurag By default, the clockify add-on fetches the user's information only from the first page. so we updated the page detail formation in the coding. Now it's fetching all the user information.
As far as we know there are no limitation/restriction on how many data/events that can be fetched at a time by using the API. However, one possible question here arises is whether your Clockify workspace is on a subdomain(eg. something.clockify.me) ? If yes, then in that case your API key will work just for that workspace. As mentioned over the Clockify API documentation(https://clockify.me/developers-api
“ Authentication
All your requests should include "X-Api-Key" in request header, containing your API key.
If your workspace is on a subdomain (eg. something.clockify.me), you'll need to generate a new API key in your Profile Settings that will work just for that workspace.”
Hi @Anurag
Sorry for the late response.
"workspace is on a subdomain (eg. something.clockify.me), you'll need to generate a new API key in your Profile Settings that will work just for that workspace.”
No, we don't have any subdomain in our organization. We have only https://app.clockify.me URL. Even though we integrated this setup in multiple instances but we were able to fetch only up to 51 users.
For each setup, we updated the new "X-Api-Key" on the add-on inputs page. Does anything need to check? Pls, let me know.