Developer Diary #2 – Splunk


Click here for Developer Diary #1

I’ve just been playing around with the out-of-the-box features in Splunk, and it’s quite impressive.   Here is a video of what I’ve been able to do with the various Vault logs after only a short time.  And I still haven’t downloaded their API.

Now that I have a feel of the product, I can sink my teeth into the API.  Suggestions welcome.



Comments

6 responses to “Developer Diary #2 – Splunk”

  1. Great work and right direction, Doug!
    But can you clear some things:

    Are you handling SOAP traffic in LOG files (for example, at 4:25)? And how did you do this if ‘yes’ – customizing IIS logs, etc.?
    Or you just handling/parsing URL string?
    Can I see what did not-Vault-Explorer application do on server?

    Regards, Dmitry

  2. Great work and right direction, Doug!
    But can you clear some things:

    1. Are you handling SOAP traffic in LOG files (for example, at 4:25)? And how did you do this if ‘yes’ – customizing IIS logs, etc.?
    2. Or you just handling/parsing URL string?
    3. Can I see what did not-Vault-Explorer application do on server?

    Regards, Dmitry

  3. No. I’m not intercepting SOAP traffic. I’m just reading from the log files.
    I’m just reading from the URL string. Several of the Vault clients add extra data to the query string, and that is what I am reading out in Splunk.
    Query string data is not automatic. The client has to explicitly add that data. Vault Explorer and Inventor definitely add this data. I am not sure about other Autodesk applications.
    Third-party apps are probably not setting the query string. But if it’s a plug-in to Vault Explorer, I think the query string will be set. I need to test.

  4. That’s not good enough.
    This way user can work from third-party app and no operations won’t be recorded.
    As I know, IIS in ‘debug’ mode can show the SOAP traffic. But IIS can’t log it in ‘regular’ mode – only via certain customizations with programming. If you could solve this puzzle – that would be the most appropriate solution for any cases.

  5. That’s not good enough.
    This way user can work from third-party app and no operations won’t be recorded.
    As I know, IIS in ‘debug’ mode can show the SOAP traffic. But IIS can’t log it in ‘regular’ mode – only via certain customizations with programming. If you could solve this puzzle – that would be the most appropriate solution for any cases.

  6. Yes, I understand that this app will not cover all cases. However, I think it will be useful for most of the Vault customers.

Leave a Reply to Doug RedmondCancel reply

Discover more from Autodesk Developer Blog

Subscribe now to keep reading and get access to the full archive.

Continue reading