Application development and testing

Application development and testing

You can use Splunk in your QA or development evironment. Developers can use Splunk to log and track data that is of interest to them, and to discover problems before their application gets out into production. You can also create mulitple Splunk indexes to separate secure or sensitive data from production log data and show developers only the data relevant to them.

Note: This topic currently provides an outline, which will be expanded over time. The outline and contents may change.

• Securely sharing production logs with Dev & QA:
  • Include quick discussion of security in Splunk, users & groups, etc. See About users and roles in the Admin manual.
• Splunk isn't just for production
  • Free Splunk on developer desktops
  • Splunk use by QA: Sometimes alerts start firing immediately after a new code release. QA can react quickly using Splunk to research issues. This allows them to very quickly identify and correct edge cases that are difficult to catch in non-production environments.
• How developers can make application management with Splunk easier
  • Splunk guidance on what to log - see the next topic in this manual, Logging for Splunk
  • correlation of web server session IDs with database user IDs
• What might you log and how do you document value to others?
  • testing/staging environment
  • errors
  • debug messages
  • integrated systems testing over multiple platforms

• Was this topic useful?
• Post a comment