Node.js not showing as a service in lab 3.3

Elastic Observability APM
1

In my Obsersability lab 3.3, the Node service is not listed as an APM service.
I have done this lab carefully, and even had the labs restarted to begin afresh.
The services list in the APM app should display petclinic-node, but it only shows the previous two services, petclinic-address-finder and petclinic-java.

  1. All previous labs up to lab 3 of Module 3 are completed successfully with the expected results. This includes Heartbeat, logs, nginx, and java.
  2. The Node.js agent is already installed on the backend server of the petclinic application. This comes pre-installed in the observability course.
  3. I have edited the config.js according to my understanding and according to the examples in the instructions for lab 3.3.
  4. The petclinic-node service is not listed in the APM services.

Here is an image of the configl.js file which I believe is the key to getting node.js to work.

3_3_config_js
3_3_config_js799×302 94.8 KB

My questions and needs:

  1. What is missing or wrong in my config.js file?

  2. Is this config.js file complete? The instructions provide a solution. It specifies that this is the contents of the configuration object. Does that mean this is the contents of the entire config.js file? Or does it mean ONLY that object and that there can be other things in the file? If so, what are those other things needed to make node.js work?

  3. What can I do to troubleshoot this lab? I think there is no need to start labs all over again.

2

@pdorcas I'm not sure GitHub - elastic/spring-petclinic: REST version of the Spring Petclinic sample application is supported anymore. It hasn't been updated in 4 years. I notice that the versions of things for the "petclinic-node" are using unsupported versions. For example:

Can you show me a pointer to the "Observability Lab 3.3"? I am not familiar with it.

3

I am very glad to get a response to my post. As this is a lab environment provided by Elastic, I can't check on all the versions of the various tools. Many of the tools and integrations came prepackaged. Thank you for your quick response!!!

I don't know how to give you a pointer to the lab. I log into the learn.elastic.co site, select the course that I'm currently studying, and have my own lab setup with various tabs. One tab is a Linux terminal where I can do command line and nano editing on text files. I use various linux and docker commands and work in Kibana tab according to the lab instructions.. One tab is Kibana, one is the lab instructions, and one is the browser which is the petclinic user interface.

The Dynamic DNS for the site when the lab is loaded is 6ghtqicvlxrlgbvdc-ihsdbxb2mswxpjpnh.labs.strigo.io.

The Public DNS is ec2-52-53-169-229.us-west-1.compute.amazonaws.com

The Public IP is 52.53.169.229

The Private IP is 172.31.8.143

One approach in the labs would be to just go through them as best as I can with the labs the way they are, learn from the lab videos and instructions, and learn enough in the process to pass the final exam for Elastic Observability Engineer Certification. Thank you again for your reply!

Phil Dorcas
pdorcas@omegaair.com
Senior Engineer, Omega Airline Software
www.omegaair.com

4

Trent, I can email you the lab instructions that I use for lab 3.3 if that would be a help. Thank you again.
Phil D.