The Service list dashboard centralizes all of your running services, allowing you to detect if and when issues occur quickly. You can use the dashboard to investigate the different services, operations, and logs inside each one.
Service list overview
The main Service list table view contains the following details:
- Name of each service
- Impact level - Determines the severity of each event, calculated based on the latency and request rate
- The Environment in which this service is located
- Request rate - Number of requests per second, in numeral and graph view
- Latency - The duration it takes data to travel in the environment, presented in milliseconds and graph view
- Error ratio - Both percentage and graph view
You can change your view by comparing the data to a previous time frame, such as the last day or week. You can also choose a different time frame that ranges from 2 hours ago and up to 24 hours ago.
If you’re looking for a specific service, start typing its name in the search box, and your view will change to display all the matching results.
Dive deeper into your services
Clicking on one of the services opens a new page with additional info, including a visual representation of the service’s current error ratio, request rate, latency, and a breakdown of the service’s operations, infrastructure, and logs.
Hovering over the graphs provides additional info for the time point you’ve chosen:
- The Request rate graph shows the number of requests made per minute
- The Latency graph provides a milliseconds count of how long it takes for data to travel in your environment
- The Errors graph analyzes the percentage of errors that occurred
Operations overview
This table includes all of the operations running inside the chosen service, with this additional data:
- Operation name
- Operation’s Impact level, calculated based on the latency and request rate
- Request rate - Number of requests per second, in numeral and graph view
- Latency - The duration it takes data to travel in the environment, presented in milliseconds and graph view
- Error ratio - Both percentage and graph view
Use the search bar to find a specific operation or the arrows at the bottom of the table to navigate the operations.
Click on an operation’s name to view its detailed trace. The trace dashboard helps you pinpoint where failures occur and find the leading contributors to slow transaction performance.
Infrastructure overview
View the CPU and memory consumption inside the service. The graphs represent a breakdown of consumption by the hour.
Hovering over the graphs provides values for the specific time point, allowing you to see how much CPU was used by the deployment at this specific time, or view how much memory this deployment used.
You can toggle your view between pods and nodes inside the service.
Track Deployment Data
You can enrich your Service Overview graphs by adding an indication of recent deployments, helping you determine if a deployment has increased response times for end-users, altered your application’s memory/CPU footprint, or introduced any other performance-related changes.
To enable deployment tracking ability, run the Telemetry Collector on your Kubernetes clusters. You can also activate this process manually by installing Logz.io Kubernetes events Helm chart and sending Kubernetes deploy events logs.
Once enabled, navigate to Services and choose one of your running services. The deployment marker will appear in your graphs, marked by a dotted vertical line.
You can view additional deployment data by clicking on the line. This data includes the deployment time, the associated service and environment, and a quick link to view the commit in your logs.
Click Go to commit to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
To activate the Go to Commit button, go to your app or service and add the following annotation to the metadata of each resource’s versioning you want to track: logzio/commit_url: "", and the URL structure should be: “https://github.com/<account>/<repository>/commit/<commit-hash>”. Learn more.