<p>So this might be a crazy idea but I have this problem I am trying to solve for. The company I am working for has literally hundreds of ID's that are used for various tasks, applications and services. The problem is they don't have a clear picture of where all of these ID's are being used. </p>
<p>So I had the idea of creating a routine that would connect to each resource and do a full parse of specific file locations looking for these ID's within files that can be parsed and then producing a report.</p>
<p>I am just not sure if something like that is feasible, or advisable.</p>
<hr/>**评论：**<br/><br/>brogrammingsins: <pre><p>Yes</p></pre>fern4lvarez: <pre><p>I'd first use bash. If it gets too complicated, then switch to Go.</p></pre>hansdr: <pre><p>Something like what you want could be written in Go, or one of the many other languages. Which language is the right choice often depends on which language you're most familiar with (assuming that you're the one who will do the coding). A Go programmer would definitely be better off using Go, while someone who's more familiar with C/C++ would be more productive sticking to C/C++...</p></pre>trevordixon: <pre><p>Rather than one writing a single program that does it all, I'd recommend, if possible, first gathering all the relevant files into one place. That might easily be done using a shell script and SSH?</p>
<p>If you can get it all into one place, you'll be able to run the parsing step more quickly and start over more easily.</p></pre>nathj07: <pre><p>It is feasible. To keep it reasonable you will need to monitor resource use as you hit a lot of network traffic and file io</p></pre>
