As you already know, there are two ways to interact with AI Advisor: Co-Pilot Mode where AI Advisor is docked to the current screen you are on (and has page context in memory), and the Full Screen Mode which, well... kind of speaks for itself.

Today we're giving the Full Screen Mode a bit of a facelift, so read on!

The new AI Advisor sidebar

One of the piece of feedback we've gotten is that the AI Settings that host important operational aspects to how AI Advisor operates are burried. Unlike say, collection configurations, AI Advisor settings (notably Runbooks and Custom Network Context) are meant to be living reflections of the operational reality of your network. 

They by definition are better when you create/update them as you go. Forcing users to dig into settings and break the flow from AI Advisor was bad user experience. We're changing that to make AI Advisor settings easier to access, something that compounds with the recently announced RBAC for AI Advisor. 

Here's how in a screenshot since a picture is always better than a thousand words:

The main new change is the sidebar that

• is horizontally resizable
• is collapsible (so you can take the full screen for your chat session)
• that now gives direct access to AI Settings: you don't need to go through Company Settings > Kentik AI to access these settings anymore

Note: The "Recent" section of the sidebar panel is a carryover from the previous version, it lets you navigate existing sessions and load them in one click in the central panel. Pinned Chat sessions will always appear at the top of the "Recent" section of the side panel - this section 

New AI Chat Sessions History screen

When clicking on the history button, a full screen history will load into the main panel. If you do this in the middle of a AI Chat Session, you can always go back by selecting the session from the "Recent" section.

This AI Chat History screen presents a few benefits

• presents itself in a full screen experience instead of being locked in a side bar
• allows users to easily filter between their own AI Chat Sessions, that of their company, or those automatically-generated by other parts of Kentik Portal  (as with the AI Auto-Investigation feature to come)

What do you think ?

We like to share these minor, quality-of-life improvements with our users, and we'd love to know what your thoughts are on this new version.

- Are you Team Co-Pilot Mode or Team Full-Screen Mode ?
- Do you think this new UI is better based on how you use AI Advisor ?
- What other improvements would you like to see us bring to our AI Advisor User Experience ?

When we originally added Syslog and Traps collection capabilities for Kentik-registered Devices, one thing was cruelly missing: while we offered a tab on the Device Details screen for Syslog from the get-go, the same for SNMP Traps was absent.

With this release we're correcting that mistake to make it easier to see specifically what Traps have been triggered on a given device! 

New Infrastructure > Device filters

First-off, you want to be able to find Devices with SNMP Traps enabled and activity in the Infrastructure > Devices screen.
This new filter is located in the NMS Status > SNMP Traps section of the left-side filtering panel - see screenshot below

Visualizing SNMP Traps

When clicking on a device with SNMP Traps, you'll now see an additional tab showing up. As you can see, it has been built with the exact same familiar UI as the Syslog tab.

You can also select the type of traps you want displayed with the Trap Type filter, or type a search pattern in the upper search bar to filter the records within the time range.

Both the Parsed PDUs and Parsed KVs in each row can be inspected in a more human legible format when clicking on the double arrow icon in the cell

What's next ?

First off, remember that both Syslogs and SNMP Traps are first class citizens in Data Explorer - they are labelled as "Events". This means that you can already slice and dice syslogs as well as SNMP Traps to further troubleshoot event that could span over your entire fleet of devices. They are also a key source of telemetry that AI Advisor can access when doing the same too!

In the near future, we'll be releasing a major overhaul of Data Explorer, Metrics Explorer and Dashboards, merging all three in a single analytics and dashboarding app that will allow the following:

• a single Analytics App that allows you to query Traffic (Flow) data, NMS (Metric, state...) data and Synthetics data in a central place
• a drastically revised dashboarding experience allowing our users to build dashboards that mix and match analytics from the three aforementioned datasets, but also simple yet powerful extensions to the Guided Mode capability currently present in Dashboards

So stay tuned as the convergence between Flow, NMS and Synthetics products gets tighter and more powerful in the year to come! 

In the mean time, do let us know what next evolutions of each of these products you'd like to see!

In previous posts, we've discussed how AI Advisor Runbooks help teams capture the operational expertise, knowledge, and procedures specific to their networks, enabling AI Advisor to more accurately investigate issues and guide teams toward answers.

Until now, Runbook management was tied to Kentik's legacy user levels, meaning only Admins and SuperAdmins could create and maintain Runbooks. This created an unnecessary barrier to adoption for a very useful feature as the people who know your network best or operate it most hands-on aren't necessarily the administrators of the tool. 

That changes today. With role-based access control (RBAC) for AI Runbooks, organizations can give more team members the ability to contribute their expertise without granting them broader administrative privileges.

But expanding access also requires maintaining control over how Runbooks are managed. Because Runbooks influence how AI Advisor investigates issues and responds to questions, changes to their content can affect the answers users receive. It's important that those changes are authorized, transparent, and auditable so users can trust the knowledge guiding AI Advisor's behavior.

This reflects a broader principle behind our approach to AI: trust is essential to adoption. Organizations need the flexibility to put AI capabilities in the hands of more people while maintaining appropriate governance over the knowledge and instructions those capabilities rely on.

RBAC builds on the safeguards and we're rolling it out to AI Runbooks now, and to Custom Network Context in the near future.
In a nutshell, we are conducting Trus/Safety work around the entire AI stack:

• Visibility into changes, even for users without permission to modify these configurations.
• Version history and rollback, allowing teams to track changes and restore previous versions.
• Audit logging for Create, Edit, and Delete actions, providing accountability for changes.

Together, these capabilities make it possible to expand participation in building AI Advisor's operational knowledge while retaining oversight and control.

RBAC for Runbooks

If you go to Company Settings > RBAC Management you will notice that Roles now include a new category of permissions titled Kentik AI

Depending on your Runbook permissions, the Settings > Kentik AI left-side panel may have the Runbooks entry disabled: the screenshot below illustrates what it looks like when a user has all Runbook permissions disabled.  

The Settings > Kentik AI > Runbooks screen will offer different functionality depending on a user's RBAC permissions, as displayed in the screenshots below.

Example of the Runbook screen for a user with CREATE, EDIT and DELETE RBAC permissions

Example of the Runbook screen for a user with VIEW only RBAC permissions

Coming up next ?

As you have noticed, we're continuously adding AI Safeties around AI Advisor. Next on our list we'll be adding the following:

• RBAC permissioning for Custom Network Context
• RBAC permissioning for AI Advisor Chat Sessions: this will eventually regulate what AI Chat sessions users have access to (all users currently have access to all sessions)

Let us know what you think!

Getting network data into Grafana shouldn't stop at the dashboard. We understand how frustrating it can be to build a great Kentik view and then have no way to alert on it, or to watch a panel-heavy dashboard crawl while it waits on API calls. That's why we're thrilled to announce v3.0 of the Kentik plugin for Grafana. We rebuilt it as a backend datasource, so your Kentik data works with Grafana the way the rest of your data does.

Some key features: 

• Alert on your network data: Queries now run on the Grafana server, so Kentik flow and NMS metrics work with Grafana Alerting, recorded queries, and shared dashboards.
• Load heavy dashboards without hammering the API: Duplicate panel queries are coalesced into one call, and rate-limited requests retry automatically.
• Start from seven ready-made dashboards: Traffic, Top Talkers, a global traffic map, geo flow, and NMS device health import in one click.
• Build dashboards that adapt: Template variables can now drive the measurement, metrics, dimensions, and filter values of a query.

What's New?

A backend datasource

Query execution, result parsing, credential handling, and the dictionary cache now run server-side in a Go backend instead of the browser. This is what makes alerting, recorded queries, and shared dashboards possible. Queries now run against Kentik's newer query API, and every request identifies itself as kentik-grafana-plugin/.

Fewer API calls, fewer timeouts

v2.0 batched panel queries in the browser. v3.0 handles this on the server:

• Identical queries issued at the same time, or within 30 seconds of each other, share one upstream call.
• Up to 10 queries in a request run in parallel.
• HTTP 429 and 502 responses retry with exponential backoff and honor Retry-After.

A rebuilt query editor

• Measurement picker: Browse Kentik measurements grouped by family (Traffic, NMS, NMS Interfaces, and more) with search and full keyboard navigation. The dimension picker warns you when a metric and dimension come from different namespaces.
• Familiar controls: Limit (Top N), filters, Merge Series Function, and Alias By / Prefix with autocomplete are all still here.
• Response format: Return time series, a table (one row per series, ideal for Geomap, bar gauge, and table panels), or a node graph (nodes and edges for Grafana's Node Graph panel).
• Clearer errors: If a metric and dimension can't be combined, the error names the conflict and suggests the universal equivalent.

Seven bundled dashboards

Import them from the Dashboards tab on the datasource configuration page.

Smarter dashboard variables

Variables can drive measurement, metrics, dimensions, rollups, and filter values. A new values(, ) function builds live variables, such as a device picker that always reflects what Kentik is receiving.

Open in Kentik, from every series

Each series carries an Open in Kentik link that opens Data Explorer in the right region (US, EU, or custom). It also carries dimension values as field labels, so map lookups and transforms work.

Grafana 13 supported

In the v2.0 post we flagged a credential-save error on Grafana 13. v3.0 is tested against Grafana 11.6, 12.4, and 13.0.

Why It Matters

• One place to watch and act: Alert rules, dashboards, and on-call routing can use the same Kentik data your team already trusts.
• Dashboards that scale: Panel-heavy dashboards and many viewers no longer mean one API call per panel per person.
• Faster time to first dashboard: NMS health, flow, and geography views come ready to import instead of being built from scratch.

What's Changing

• Minimum Grafana version is 11.6.
• Your existing panels keep working. Panels saved with v2.0 queries are translated automatically and show a deprecation notice. Re-save them in the new format, because this compatibility layer will be removed in a future release. A translated panel currently opens with blank editor fields, so plan to reconfigure it when you re-save.
• Open in Kentik opens Data Explorer, not your exact query. In v2.0 the link carried your query, time range, and filters. In v3.0 it lands on the Data Explorer for your region and you re-enter the query. We're working on restoring the full deep link.
• Network Health (OSI) is now Traffic Detail. The bundled dashboards were rebuilt for the new query model.
• Events data isn't available yet. Syslog, SNMP traps, and other /events measurements can't be queried through the new API today.
• Check your outbound access. The Grafana server calls the Kentik API directly. If you restrict egress, allow grpc.api.kentik.com (US) or grpc.api.kentik.eu (EU).

Get Started!

Already on v2.x? Update from the Grafana plugin catalog, or run grafana cli plugins update kentik-connect-datasource. Then open Connections > Data Sources > Kentik, click Save & test, import the new dashboards from the Dashboards tab, and re-save your existing panels in the new format.

New to the plugin? In Grafana, go to Connections > Add new connection, search for "Kentik", and install kentik-connect-datasource. Enter your region, email, and API token, then import the bundled dashboards.

Still on the legacy kentik-connect-app (v1.x)? Follow the migration guide, then update to v3.0.

Ready to alert on your network? Grab v3.0 from the Grafana plugin catalog, and see the Kentik Knowledge Base for setup details.

Up until today, our users could only Authenticate our AI Advisor MCP into their own agentic solutions using an API Key and Token. A large number of users asked if we could add OAuth to the MCP Authentication methods, so today's post is about just that!

There are multiple benefits to using OAuth to Authenticate against AI Advisor's MCP:

• OAuth allows our customers to control access to the MCP directly from their IdP (provided said users have a Kentik Portal account): centralized auth management
• OAuth is useful for integrations: instead of relying on the API Token of a single user to build an integration and therefore making it brittle, OAuth elegantly solves for this use case, allowing more easy management for the business
• OAuth prevents security issues such as a User's Kentik API Token leaking or being intercepted
• More generally, OAuth has become the choice standard for MCP Authentication industry wide

Let's dive in!

Adding AI Advisor MCP to Claude Code

Before lauching Claude Code, punch this command in your project directory: 

claude mcp add ai-advisor --transport http https://api.kentik.com/mcp 
(use api.kentik.eu if you are on an EU account)

Then launch Claude Code and fire an /mcp command, you'll see the ai-advisor MCP configured, but unauthenticated, and follow the steps - a browser tab will be invoked to login to Kentik Portal.
The series of screenshot below illustrates these steps.

When done, the /mcp command should give you a similar output with a green check indicating that AI Advisor MCP is connected!

Adding AI Advisor MCP to Claude Desktop

Use the [+] button in your prompt box in Claude Desktop and select Add Connector > Add custom connector

Use this MCP URL to configure the custom connector: https://api.kentik.com/mcp (or api.kentik.eu if you're on an EU account) and follow the step by step, which will invoke a Kentik Portal login page.

Follow the steps until a browser tab opens prompting you to Authenticate

You're done once the browser tab gets to this state

Adding AI Advisor MCP to Cursor

 While in Cursor, use the [+] button in your prompt box, and select MCP > Manage, and on the next screen select New MCP Server, it will open your ~/.cursor/mcp.json config file, updated it as detailed in the screenshot below using this config block. (user api.kentik.eu if you are an EU customer) and Save the mcp.json file.

{  "mcpServers": {    "Kentik AI Advisor MCP": {
      "url": "https://api.kentik.com/mcp"
    }
  }
}

Then click on the Authenticate option for the MCP server entry you just created

and follow the instructions in the resulting browser page until the MCP server is displayed as below

The AI team over at Kentik is very excited to see what your teams are going to build using our MCP, give us a shout if you want to demo your integrations and we'll hop on a call!

This feature request is a small-ish one, but you'd be surprised how many users have been asking for it in recent times :)
Title says it all, our users love AI Advisor so much that they want to make it their landing page, so here it is !

How can I switch my landing page to AI Advisor ?

First head out to your user profile, on the upper right corner of Kentik Portal

Once there, find the Landing Page setting as shown below

And you're done ! 

Hint: you can always go back to your landing page by clicking the upper left Kentik Logo 

What more can I do ?

Bulk-setting the landing page for multiple users in one go

If you go to the Settings > Users you'll notice you can select multiple users, it will make a bulk edit floater open at the bottom of the screen.
If you are an Admin user, you'll then be able to modify a variety of user attributes in bulk.

Role-Sets & the Landing Page

If you are an avid RBAC (Role Based Access Control) admin user, you may already have assigned users to Role-Sets: these objects are groups of RBAC Roles that can be assigned to users.
One of the things Role-Sets also allow you to do is let you configure a single Landing Page. Every user under this Role-Set will have their landing page follow this configuration.
We have made sure to add AI Advisor to the configuration options of these Role-Sets.

Static IPs Are Here for Global Agents!

We are thrilled to announce that Static IP support is officially live for Kentik Synthetics Global Agents!

Managing network access, firewalls, and allowlists just got a whole lot easier. If your testing relies on fixed source IPs to get past strict firewall rules or internal access control lists (ACLs), this update is designed specifically for you.

What’s New?

• Filter by Static IP: Effortlessly search and filter the Global Agents list to isolate agents configured with static IP addresses.

• Agent Details View: Instantly view assigned static IP addresses directly within the Agent Details panel for fast verification and allowlist configuration.

• Streamlined Test Creation: Select agents with confidence! You can now filter for static IP agents directly within the Test Creation workflow, ensuring your synthetic tests run smoothly through locked-down gateways.

Why You’ll Love It

No more guessing which agent IP to put on your allowlist or dealing with broken test runs due to unexpected IP shifts. With static IPs, you gain predictable source addresses, simplified perimeter security management, and seamless testing against protected endpoints and private services.

In a follow up release, you will be able to retrieve the list of global agent static IPs via the API.

Ready to streamline your agent management? Head over to Synthetics > Agents to check out the new filters today!

A steady portion of our Kentik AI Advisor work happens behind the scenes which main goal is to make it both safer and more transparent for users to feel confident when they use it.
When it comes to AI, we strongly believe that security, safety and transparency are key features, even though they're never listed as such and hardens the trust that our users place in Kentik, as well as provide the sound guardrails required for adoption to keep growing.

Today's release is about another one of these focused runs, it is about our engineering team adding guardrails around AI Advisor's Custom Network Context - read on!

AI is Magic. Sometimes too much.

As detailed in this previous post about Kentik's AI Runbooks, both the Custom Network Context (aka CNC) and Runbooks deeply affect AI Advisor's reasoning.
Imagine Kentik users whose workflow could rely on a very specific prompt, which they'd for example routinely enter every morning with their first coffee - say What's the status of my edge routers this morning ?

In this example, imagine that the list of Edge Routers is documented in their company's Custom Network Context. (which is one of the most common usages of CNC, by the way...)
Also a reasonable hypothesis: users who rely on this mapping ignore that it has been configured via CNC by a benevolent coworker.

What the above implies is the following sum of safety features:

• provide ways to track any AI related configuration change (in this case Custom Network Context)
• allow users to determine who made the change and when
• allow the security team to be able to research modifications on such configuration objects, even if they are not users of AI capabilities
• allow users to rollback such changes if it turns out that their effect on AI Advisor answers negatively impacts its answers

This is what today's feature is all about !

Side note: versioning and audit logging was already available for Runbooks, we extended them and perfected them for CNC.

Updated Custom Network Context Interface

Let's head to Company Settings > Kentik AI > Custom Network Context.
First off, we gave the default empty state a bit of a facelift, you know - while at it...

For those out there with an already populated Custom Network Context, here's what it looks like now: a right-side drawer contains every previous version with:

• Date, Author and Summary metadata attached to it
• The ability to load it in the main center section, from where the user will be able to
  • Inspect the Diff with the previous version
  • Trigger a Roll back to said version

Selecting a previous version, and then switching to Diff display mode:

Custom Network Context & Audit Log

While working on AI Safety measures for Custom Network Context, we also added support for Audit Log: with any modification on the CNC (Create, Edit, Delete), an Audit Log line is now generated, and visible in the usual Company Settings > Audit Log as displayed in the screenshot below.

Every network operations team has a "tribal knowledge" problem. When a critical alert fires at 2am, the outcome can depend too much on who responds — who has seen this problem before, who remembers that one strange configuration issue from six months ago, or who knows that when one signal looks normal, the next thing you should really be checking is somewhere else entirely.

Runbooks have always been the answer in theory, allowing organizations to codify that knowledge and those best practices into a repeatable checklist that can be applied consistently across the team irregardless of how good of network and infrastructure engineers they are - they used to be called NOC procedures. 

If only it were quite that simple.

In practice, runbooks tend to be partially maintained notes scattered across Confluence, Slack threads, old tickets, and sleeping brains. And even when a good runbook does exist, it is usually disconnected from the tools where the investigation is actually taking place — so you're context-switching between your observability platform and a document, manually translating "check the BGP neighbor state" into the right query, on the right device, for the right point in time.

Let's look at how AI Advisor natively includes the concept of Runbooks and how we cranked it up a notch in this release!

AI Advisor Runbooks in a nutshell

Runbooks: TL;DR

If you've been using AI Advisor for a while, you may already know that AI Advisor has a native Runbook capability designed to solve for this.
You can write, in natural (wiki-style markdown) language, specific step-by-step instructions for how you want AI Advisor to investigate a particular situation, including what to look at, what certain results mean, and what it should investigate next. 

You can either manage them in Org Settings > Kentik AI > Runbooks

...or ask AI Advisor directly

Composing with Runbooks

Here are a few cool things you can do with Runbooks - go ahead and try them

• Let AI Advisor select the right Runbook for you. Runbooks can be dynamically invoked by AI Advisor based on the context of a user's prompt, so you don't always need to explicitly call one by name. AI Advisor will also expose if it is selecting and using a rubook for an investigation.
• Run a Runbook with variable arguments. If the first lines of a Runbook define required variables, AI Advisor will ask the user to provide those inputs before execution.
  Example: Run the Peering Vetting Procedure for AS12322, where Peering Vetting Procedure is the runbook andAS12322 is passed in as the argument.
• Run Runbooks on a schedule. A Runbook can be executed at a defined frequency using Org Settings > Report Subscriptions with the AI Advisor report type, with the resulting output attached to an email as a PDF.
• Trigger Runbooks from alerts. In the near future, Runbooks will be able to map directly to Alert Policies and automatically execute as an Auto-Investigation whenever the associated alert fires. This capability is currently in Early Access with select customers and will be available more broadly soon.

Runbooks vs Custom Network Context

Now some of you may wonder what's the difference between Runbooks and the Custom Network Context that is also part of AI Advisor. To understand that, ket's look at the concept of AI Context and how it works in general. 

AI Advisor leverages incremental context within a session: this attached context is a consumable budget - it is handed over to the LLM with each prompt to help it answer the most recent question and each turn/response appends to the context, consuming budget: it is therefore a finite quantity and precious resource 

A fresh AI Advisor session launches with the default System Prompt that's common to every customer, to which we append the Custom Network Context (CNC) on the fly. This is specific information you or your organization has provided to AI Advisor that matters for understanding your network.

This is why CNC is best used for general directives and metadata that apply broadly to the entire infrastructure, because it's your default context spend.

If are familiar with Claude, Custom Network Context is basically your claude.md.

Realistically, you cannot attach every single task-specific procedure your NOC has in the CNC because of the risk of eating your entire context budget the second AI Advisor instantiates. For that, we we created Runbooks.

Runbooks leverage dynamic linking: AI Advisor fires a Runbook tool with every turn, which looks up similarities between the ongoing prompt and all of the Runbook's Title and Description (do make sure these are self-explanatory). When a match is found, the Runbook is appended to the session's AI Context, only consuming from the budget when a match is found.

Again, if you are fluent with Claude, a good way to reason about AI Runbooks in Kentik is the parallel with Claude Skills.
 
As explained, both technically and conceptually behave the same:

• Runbooks are task-specific, describe complex and multi-steps workflows (troubleshooting, analyzing, auditing, planning...)
• Runbooks are discovered via metadata (title, descriptions) and loaded only when Claude recognizes a relevant task.

Runbooks & AI Safety

Modifying Runbooks (also valid for CNC), may make AI Advisor start giving different answers overnight to users that were use to getting consistent answers from the same prompts day after day.

As a first principle, Kentik strives to provide the necessary guardrails for the entire company to use AI Safely and Transparently, which implies the following features that come for free with Runbooks:

• Any change (or creation, deletion...) on a Runbook is logged in our Audit Log facility
• Any time AI Advisor dynamically summons a Runbook, it will
  • explicitly mention it in its reasoning
  • let the user view the runbook as part of the process
• Any change in an AI Runbook populates a history, with a view to track changes across time and the ability to revert them

Building on Runbooks

Cranking it up a notch

Now that you know everything there is to know about Runbooks, a problem still stands: you can't foresee every situation in advance, and not every troubleshooting process is already documented well enough to turn into a runbook.

In fact, something we've heard from customers is that one of the useful parts of working with AI Advisor is the ability to prod and poke at an investigation — telling it to look somewhere else, providing additional context, correcting an assumption, or guiding it toward the signals you know matter in your network. 

Here's the beauty of it all: over the course of a fruitful investigation, you've effectively taught AI Advisor how you would troubleshoot that particular problem.
...and now you're telling me I need to open an extra tab, and tediously copy/past every single prompt I've entered during that session into a newly created Runbook ?  Color me disappointed!

Try a prompt like this and AI Advisor will have your back!
"- Turn this session into a Runbook
 - use this title: 'Peering Request Assessment Procedure'
 - use the following Description: "Standard procedure our Peering Managers use to evaluate peering requests from an ASN"

... and AI Advisor will create said runbook for you to keep hacking on.

You didn't give it a name or a description? AI Advisor will figure it out for you based on the content of your session.

Lastlt -- useful advice for the social Runbook writer

• Your NOC team most likely has existing wiki-based or google docs-based procedures.
  Why don't you just pick a couple of them, copy paste them into Runbooks and try them on for size? You'd be amazed how little tweaking these actually need!
• AI is a muscle: build habit around always turning a fruitful AI Advisor session into a runbook.
  
  

Today we're releasing one of AI Advisor's first Write features: a feature that allows it to create objects in your Kentik Portal configuration.

When AI Advisor launched, its initial scope was to help network operators understand and gain insights on their network data faster, whether during a routine investigation or planning exercise or troubleshooting a critical network outage. It was intentionally limited in scope to reading network data, with no ability to make changes. Today marks the first release of a new family of AI Advisor capabilities to help you configure Kentik itself and accelerate onboarding.

Let's take a look at it!

How does it work ?

Let's just ask AI Advisor, shall we?

So all we have to do is prompt AI Advisor to create a site by submitting its main attributes – to double-check which attributes we can set at creation time, let's just ask it again.

Starting with a simple example, note how it will always ask for permission to create, edit, or delete any object in Kentik Portal via a Human in the Loop (HITL) prompt.

What about batch creating sites?

While creating Sites with AI Advisor  in Kentik Portal is neat, what we really want it to do is speed up onboarding (i.e. to create multiple sites in one go).

Good news: AI Advisor can do that!

All we have to do is submit the content of a CSV file that has a row for each site. Here's an example with three sites and a header row that names the fields:

"site name","address_street","address_zipcode","address_country_2_letter","address_region","site_type","site_market","peeringdb_fac"

"[test] CDG Telehouse 2","137 boulevard Voltaire","75011","FR","Île de France","Connectivity","test_site_market","53"

"[test] CDG Equinix PA3","114 rue Ambroise Croizat","93200","FR","Île de France","Connectivity","test_site_market","717"

"[test] LYS Free Pro Lyon Rock","60 Avenue Rockfeller","69008","FR","Rhone Alpes","Connectivity","test_site_market","6976"

This results in the successful creation of three sites, with a single HITL confirmation prompt to confirm.

Taking site creation to the next level: Combining AI Advisor tools

Let's imagine we have all our sites registered in PeeringDB as Facilities. The good news is that AI Advisor can access a tool (to be announced in a separate article) with access to the entire up-to-date PeeringDB data.

So we can ask questions such as:

...and follow up with a request to create them in Kentik.

And voila!