Skip to main content

Creating our Route

Since the purpose of this course is to introduce you to GitOps, we're going to stay out of the weeds, and use a pre-created Pipeline, named apache_logs. This Pipeline does the bare minimum to prep our data for delivery to our Elasticsearch Destinations. We just need to create the Route for it.

Creating the Route
  1. You should still be on the Stream Dev top tab, with Manage active in Stream's own top nav.
  2. Open the Routing submenu. (On small viewports, you might need to click the ••• overflow submenu to reveal it.)
  3. From this submenu, select Data Routes.
  4. Click Add Route to create a new Route.
  5. In the Route Name field, enter apache_logs.
  6. In the Pipeline drop-down, select apache_logs.
  7. Toggle the Enable Expression field to Yes.
  8. In the Output Expression field, enter: 
    `${C.logStreamEnv}_logs`
  9. Use this Route's left grab handle (looks like: ) to drag the Route to the top of the Routing table.
  10. Click Save, and look for a green confirmation message.
  11. Click Commit at Stream's upper right corner.
  12. In the resulting Git Changes – Group default dialog, enter a commit message (e.g., Configure Route).
  13. Click Commit and Deploy, and look for green confirmation messages.

All of our components are now in place! Everything will take a couple of minutes to deploy. But after that, if we take a look at the Elasticsearch/Kibana top tab, we'll see our development Stream instance feeding data to the dev index.

Validating Data Flow in Elasticsearch
  1. Click the Elasticsearch/Kibana top tab.
  2. In the Kibana UI's left nav, click the second button, Discover. (See the screenshot below.)
  3. If dev* is not set as the index pattern, click the drop-down selector and set it.
  4. Click Refresh if necessary.

Kibana Discover

Finally, we need to push all of these configuration changes to our remote dev branch.

Pushing Changes to Dev Branch
  1. Click back to the Stream Dev top tab.
  2. In Stream's own top nav, click the Version Control () button, and from the Version Control fly-out, click Commit.
  3. In the resulting Git Changes – Global dialog, leave a nice commit message.
  4. Click Commit and Push, and look for green confirmation messages.

With all our configuration now pushed to our dev remote, our next step is to go to the repo, where we'll merge our refreshed dev branch to prod.