Splunk Assessment: Index Ap17 Here, Ap17 Is The Instance For Production Org
Splunk Assessment: Index Ap17 Here, Ap17 Is The Instance For Production Org
index=ap17
here, ap17 is the instance for production org.
Sandbox:
`from_index_sandbox(cs101)`
here, cs101 is the instance for sandbox org.
*API:*
a) Using Rest API, insert an account record in your local org. Provide the splunk query
with results to check the same API call.
Answer: Created a new Account using REST API: 0010I00002Tnt6QQAR
b) Using Soap API, insert a contact record in your local org. Provide the splunk query
with results to check the same API call.
Answer: Created a new contact using SOAP API: 0032w00000IjUS6AAN
c) Provide the splunk query to see all API calls for last 24 hours in your local org.
Answer: We can use the below splunk query to see daily API requests:
*Login Rate:*
1. We are hitting "Login Rate Limit" which is 3,600(default) per user per hour. Please
list the steps you will take to debug this issue, kindly include Splunk query used.
Answer:
Identify the user hitting the limit:
index=instanceno* earliest=-4d orgId* logRecordType=sclrt "LOGIN_RATE_EXCEEDED"
| fields userId
| dedup userId
| table userId
dedup will remove duplicate userId as we just to identify which user hit the limit.
Analyse the usage pattern:
index=instanceno* earliest=-15d `logRecordType(L)` orgId* userId="userId*"
| timechart count span=1h
*Asynchronous Apex:*
1. What are the logRecordTypes associated with Batch Apex? Please explain their
usage.
Answer: We use logRecordType *axapx* with different *quiddity*
Process MessageTypeName
*Apex Execution:*
1. Write a splunk query that will provide a table having all the trigger executions
(triggeName, triggerType etc.) executed in last 24 hours for your local org.
Answer:
Index = ap17 00D2x000005NxZ3 earliest=-24h `logRecordType(t)`
2. Provide the steps to debug the error "Apex CPU time limit exceeded". Kindly
include Splunk queries used.
Answer: Best way is to check for this error is to check the debug logs to identify loopholes
specific to particular process.
Step 1: Retrieve the details using "Apex CPU time limit exceeded"
Step 2: Retrieved the RequestId and then use the requestId to get details about transaction.