I have some troubles with email sent from Splunk with some Alerts, debugging this takes a lot of time, i have to wait for the alert to trigger and check the log. Then i thought, is there anyway i can send mail immediately when i do a search instead of waiting for the alert triggered. Fortunately, the solution is already there : the sendemail command. * | top 5 host | sendemail to=”[email protected]” sendresults=true inline=true My thought: we just need to thing about a different way to do our daily routine, there will be a better way to do it.Read More →

I build a docker image, everything runs well on my dev machine. But when i deploy the images to my other machine, some services in the container was not able to start. The services starts by using /etc/init.d/script , when i troubleshoot the script i see the script stop at this command Not sure what “test -x ” is , i google and found that : -x is the same as setting xtrace with the -o option to bash. So it gave me some hints to find where the root cause, it looks like we can’t run xtrace , i re-run my container with this option to enable xtraceRead More →

When we configure inputs.exec , your program/bash script must have exit code 0. If it’s not 0 , telegraf will not send the metrics. This is an example , i have a bash file which will run 10 small scripts myscripts.sh /scripts/file1.sh/scripts/file2.sh/scripts/file3.sh/scripts/file9.sh/scripts/file10.sh Telegraf will run my scripts.sh , the last script file10.sh is very important, if this script does not exit 0 , the entire stack will not send any metrics. There is a trick , we can add exit 0 at the end of the myscripts.sh /scripts/file1.sh/scripts/file2.sh/scripts/file3.sh/scripts/file9.sh/scripts/file10.shexit 0Read More →

Cloudflare use several methods to detect if it’s a human or a bot:– SSL order – there is a different in the SSL library between a normal browser like Chrome with other tool like curl – – If the IP source comes from a data center or residential address– The user agentRead More →

1. SQLServer: Buffer Manager: Buffer cache hit ratioThe buffer cache hit ratio counter represents how often SQL Server is able to find data pages in its buffer cache when a query needs a data page. The higher this number the better, because it means SQL Server was able to get data for queries out of memory instead of reading from disk. You want this number to be as close to 100 as possible. Having this counter at 100 means that 100% of the time SQL Server has found the needed data pages in memory. A low buffer cache hit ratio could indicate a memory problem.Read More →