Finally add the following to the appsettings.json file\n\r\n\/\/ Eureka info\r\n "eureka": {\r\n "client": {\r\n "serviceUrl": "http:\/\/localhost:8761\/eureka\/",\r\n "shouldFetchRegistry": "false",\r\n "shouldRegisterWithEureka": true,\r\n "validateCertificates": false\r\n },\r\n "instance": {\r\n "appName": "weatherapi",\r\n "port": "8080",\r\n "ipAddress": "localhost",\r\n "preferIpAddress": true\r\n }\r\n }\r\n<\/pre>\n<\/li>\n<\/ul>\nWe’re going to leave the API with the default weatherapi, hence the appName in the appsettings.<\/em><\/p>\nNotice we set the value for “shouldFetchRegistry” to false as this service will not be acting as a client to any other services. Obviously change this is you also need to discovery other services. “shouldRegisterWithEureka” is set to true as we want this service to automatically register itself with Eureka.<\/p>\n
Now navigate to the URL of your Eureka server again (or refresh) and you should see a new Application. In my case I have an application with the name weatherapi<\/em>. This name comes from our appsettings.json configuration application\/name.<\/p>\nInfo and Health<\/strong><\/p>\nIf you click on the instance link within the Eureka server dashboard, you will navigate to<\/p>\n
\r\nhttps:\/\/localhost:5001\/info\r\n<\/pre>\n(or whatever ip\/hostname and port your service is running on) you get a 404, so let’s fix that in our project.<\/p>\n
Info, by default will display some basic information about the application, product version etc. However you can also add further custom information if you want, but example the git build SHA1 hash or just some general info. <\/p>\n
\n- Add NuGet package Steeltoe.Management.EndpointCore<\/li>\n
- In Startup.cs ConfigureServices, add the following\n
\r\nservices.AddSingleton<IInfoContributor, MyInfoContributor>();\r\nservices.AddInfoActuator(Configuration);\r\nservices.AddHealthActuator(Configuration);\r\n<\/pre>\nThe first of these lines will add our implementation of an IInfoContributor to allow for custom info.\n<\/li>\n
- \nStill in Startup.cs, but now the method Configure, add the following to the UseEndpoints endpoint routes<\/p>\n
\r\nendpoints.Map<InfoEndpoint>();\r\nendpoints.Map<HealthEndpoint>();\r\n<\/pre>\n<\/li>\n
- \nNow we’ll create a simple implementation of and IInfoContributor which allows us to add our own info, so add the following class<\/p>\n
\r\npublic class MyInfoContributor : IInfoContributor\r\n{\r\n public void Contribute(IInfoBuilder builder)\r\n {\r\n builder.WithInfo("MyInfo", new { SomeName = "Scooby Doo" });\r\n }\r\n}\r\n<\/pre>\n<\/li>\n<\/ul>\nNow when we run our service we hope to see our info data, however by default Steeltoe seems to set the info and health endpoint to \/actuator\/info and \/actuator\/health respectively. Eureka seems to expect \/info. So go to the appsettings.json and add the following to the Instance section<\/p>\n
\r\n"StatusPageUrlPath": "\/actuator\/info",\r\n"HealthCheckUrlPath": "\/actuator\/health" \r\n<\/pre>\nNote: I’m not sure what I’m missing here and why the defaults don’t match up, but these configuration changes will tell the Eureka server (when we register our service with it) that it should use these paths for info and health.<\/em><\/p>\nNow, if you run the service again for \/actuator\/info you should see something like this<\/p>\n
\r\n{"MyInfo":{"someName":"Scooby Doo"},\r\n"applicationVersionInfo":{"ProductName":"RegisterExample",\r\n"FileVersion":"1.0.0.0","ProductVersion":"1.0.0"},\r\n"steeltoeVersionInfo":"ProductName":"Steeltoe.Management.Endpoint",\r\n"FileVersion":"3.0.2.0","ProductVersion":\r\n"3.0.2\\u002B4089779c66d127f40325a3be9b613149b3b090f2"}}\r\n<\/pre>\nand health something like<\/p>\n
\r\n{"status":"UP","details":{"liveness":{},"diskSpace":{"total":4000769372160,\r\n"free":3889734168576,"threshold":10485760,"status":"UP"},"eurekaServer":\r\n{"remoteInstStatus":"UNKNOWN","fetchStatus":"Not fetching","heartbeat":\r\n"Successful","heartbeatStatus":"UP","heartbeatTime":"2021-01-23T20:40:44",\r\n"status":"UP","applications":"NONE"},"readiness":{}}}\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"The Eureka server is used as a registry for maintaining lists of services and their endpoints. It’s used a lot in the microservice world by way of a microservice registering it’s existence somewhere (in this case in Eureka). When a client (whether it’s another service or anything else for that matter) want to access a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3,102,240],"tags":[],"class_list":["post-8655","post","type-post","status-publish","format-standard","hentry","category-c","category-docker","category-eureka"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/8655","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/comments?post=8655"}],"version-history":[{"count":5,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/8655\/revisions"}],"predecessor-version":[{"id":8672,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/8655\/revisions\/8672"}],"wp:attachment":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/media?parent=8655"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/categories?post=8655"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/tags?post=8655"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}