We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing observability resources at scale (Self-Service Observability: How To Scale Observability Adoption Through Self-Service, How To Build a Self-Service Observability Practice with Splunk Observability Cloud). We also saw how to build out an OpenTofu/Terraform repository to successfully start the OaC practice (Splunk Observability as Code: From Zero to Dashboard). But what if it could be even easier?
If you haven’t seen our series on Splunk Observability Cloud’s AI Assistant in Action (find the first post here), we’ll give you a bit of background. The AI Assistant is backed by Agentic AI and is built directly into Splunk Observability Cloud. It helps you quickly and easily tap into the health of your applications and infrastructure and can even do cool things like generate Terraform code for your observability resources. Instead of manually writing HCL syntax from scratch, you can describe what you want to build in natural language and get production ready Terraform code in seconds.
Let’s walk through the simple steps of building a dashboard using the Splunk AI Assistant. Let’s say we want a dashboard for monitoring our Kubernetes cluster’s health (side note: Splunk Observability Cloud comes with out-of-the-box Kubernetes navigators so we can monitor Kubernetes environments with no manual configuration, but stick with us here).
Navigate to Splunk Observability Cloud and look for the AI Assistant icon. Select it to open the assistant:
In the AI Assistant, describe what you want in natural language:
The assistant will generate Terraform code, which you can then plug into your Observability as Code repository:
Don’t yet have an OaC repo template that communicates with Splunk Observability Cloud? Here you go: http://cs.co/self-service-observability
We can then populate our Dashboard with charts by generating chart configurations via Terraform using the AI Assistant. In our prompt, we can specify parameters like the dashboard we’d like the chart to live on, the metrics we’d like to monitor, the time range we’d like to focus on, the way we would like our data grouped, etc.:
We can then take that Terraform generated by the Assistant, and once again plug that into our Observability as Code repository.
Once we’ve deployed those new resources, along with any others we wish to create, we can use them to monitor our application from within Splunk Observability Cloud:
When using the AI Assistant for Terraform generation:
Ready to try it for yourself? Head over to Splunk Observability Cloud, open the AI Assistant, and start building. Don’t yet have Splunk Observability Cloud? Try it free for 14 days.
Never miss a new post. Check out this short guide on how to subscribe to the blog and get updates.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.