Welcome!

Blog Feed Post

Customizable naming for auto-detected server-side services

Dynatrace automatically detects and names your applications’ server-side services based on basic properties of your application deployment and configuration. These properties and the resulting service names should be intuitive to you because they reflect your service landscape. In some cases however, the default naming scheme may not be to your liking or may not adequately reflect your service landscape. In other instances, you may want to add certain process or service meta data to a service name to improve usability. Our new service naming rules enable you to customize and enhance the automated naming of your services.

To define a service naming rule

  1. Go to Settings > Server-side service monitoring > Service naming rules.
  2. Click the Add new custom rule button.
  3. Type a Rule name.
  4. Define the Service name format including any static text string to be included that describes the named service. Optional placeholders are available to make it easy to dynamically include specific service and process group properties in the automated service name.
  5. Consider whether or not you want to restrict this naming rule to a specific process group, technology, or service type. While this step is optional, it provides a quick means of reducing the number of services that a rule applies to. To reduce the list of applicable services even further, you can add Conditions to the new rule. For an explanation of applying conditions, see Can I organize services, process groups, & hosts with tags?

    Note: If within the name format you reference a property that doesn’t exist in a service that the rule applies to, the placeholder will be replaced with an empty string. You can ensure that the rule only applies to services where the property exists by adding an exists condition for the desired property.
  6. Click Save.

Customize naming standards for your services

Service name format options enable you to build complex naming standards for the services in your environment. The example below includes a CloudFoundry space name as the prefix for automated service naming ({ProcessGroup:CloudFoundrySpaceName}). This naming pattern will only be applied to process groups that have the specified CloudFoundry space name property. The space name placeholder will be replaced with the specific value of the respective process group when the service is named. Also note that because a CloudFoundry space condition has been created, this rule will only be applied to process groups that have the specified CloudFoundry space name.

Every monitored service that is discovered in this CloudFoundry space will be named using the same rule defined above. You can use any property that is displayed within the Properties & tags section of each service page (see Available placeholders list below). You can also include any property of the underlying process in your automated service naming.

You can even extract portions of process and service names for inclusion in service names. Consider that your processes follow a naming logic that contains a qualifier (for example, dynatrace). You can use regex in the references to meta data in names to extract portions of a detected process or service name.

The example rule below looks for services that run in process groups whose name starts with the string dynatrace. All the process groups that this rule applies to follow the pattern dynatrace-<CODE>-<Name>. This is what the regex dynatrace-[^-]++-.* indicates in the condition example below.

All the process groups in this example include the string dynatrace-<CODE>-<Name>. This rule uses <CODE> as a prefix for service names. To do this, use the placeholder {ProcessGroup:DetectedName}. When you use one of the defined placeholders you can add a regex to extract a portion of the detected value.

To extract something from {ProcessGroup:DetectedName} you could use {ProcessGroup:DetectedName/REGEX}. The regex simply extracts the complete match. It doesn’t allow capture groups, only atomic and lookaround groups.

In the example below, the regex looks like (?<=dynatrace-)[^-]++. While this all may look rather complicated, all it does is capture the portion of the string between dynatrace- and the next instance of -. This regex uses a lookbehind for dynatrace- and a matches everything until the next -.

The result speaks for itself. The resulting service names are all prefixed with the desired environment code.

This functionality, combined with the tagging rules, enables you to organize and categorize your services in ways that are intuitive to you and your team. You can even use regex to adjust the default naming schemes of built-in rules.

We’ve decided to simply document the default behavior in the same fashion as custom rules. This is what the built-in rules are—they aren’t configurable. They simply describe how and why certain services are named as they are.

The post Customizable naming for auto-detected server-side services appeared first on Dynatrace blog – monitoring redefined.

Read the original blog entry...

More Stories By Dynatrace Blog

Building a revolutionary approach to software performance monitoring takes an extraordinary team. With decades of combined experience and an impressive history of disruptive innovation, that’s exactly what we ruxit has.

Get to know ruxit, and get to know the future of data analytics.

Latest Stories
DX World EXPO, LLC, a Lighthouse Point, Florida-based startup trade show producer and the creator of "DXWorldEXPO® - Digital Transformation Conference & Expo" has announced its executive management team. The team is headed by Levent Selamoglu, who has been named CEO. "Now is the time for a truly global DX event, to bring together the leading minds from the technology world in a conversation about Digital Transformation," he said in making the announcement.
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, and Brandon Crowfeather, Product Manager, at Vivint Smart Home, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
SYS-CON Events announced today that Conference Guru has been named “Media Sponsor” of the 22nd International Cloud Expo, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. A valuable conference experience generates new contacts, sales leads, potential strategic partners and potential investors; helps gather competitive intelligence and even provides inspiration for new products and services. Conference Guru works with conference organizers to pass great deals to gre...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
The Internet of Things will challenge the status quo of how IT and development organizations operate. Or will it? Certainly the fog layer of IoT requires special insights about data ontology, security and transactional integrity. But the developmental challenges are the same: People, Process and Platform. In his session at @ThingsExpo, Craig Sproule, CEO of Metavine, demonstrated how to move beyond today's coding paradigm and shared the must-have mindsets for removing complexity from the develop...
In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, led attendees through the exciting evolution of the cloud. He looked at this major disruption from the perspective of technology, business models, and what this means for enterprises of all sizes. John Considine is General Manager of Cloud Infrastructure Services at IBM. In that role he is responsible for leading IBM’s public cloud infrastructure including strategy, development, and offering m...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
Companies are harnessing data in ways we once associated with science fiction. Analysts have access to a plethora of visualization and reporting tools, but considering the vast amount of data businesses collect and limitations of CPUs, end users are forced to design their structures and systems with limitations. Until now. As the cloud toolkit to analyze data has evolved, GPUs have stepped in to massively parallel SQL, visualization and machine learning.
"Evatronix provides design services to companies that need to integrate the IoT technology in their products but they don't necessarily have the expertise, knowledge and design team to do so," explained Adam Morawiec, VP of Business Development at Evatronix, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
To get the most out of their data, successful companies are not focusing on queries and data lakes, they are actively integrating analytics into their operations with a data-first application development approach. Real-time adjustments to improve revenues, reduce costs, or mitigate risk rely on applications that minimize latency on a variety of data sources. In his session at @BigDataExpo, Jack Norris, Senior Vice President, Data and Applications at MapR Technologies, reviewed best practices to ...
Widespread fragmentation is stalling the growth of the IIoT and making it difficult for partners to work together. The number of software platforms, apps, hardware and connectivity standards is creating paralysis among businesses that are afraid of being locked into a solution. EdgeX Foundry is unifying the community around a common IoT edge framework and an ecosystem of interoperable components.
"ZeroStack is a startup in Silicon Valley. We're solving a very interesting problem around bringing public cloud convenience with private cloud control for enterprises and mid-size companies," explained Kamesh Pemmaraju, VP of Product Management at ZeroStack, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Large industrial manufacturing organizations are adopting the agile principles of cloud software companies. The industrial manufacturing development process has not scaled over time. Now that design CAD teams are geographically distributed, centralizing their work is key. With large multi-gigabyte projects, outdated tools have stifled industrial team agility, time-to-market milestones, and impacted P&L stakeholders.
"Akvelon is a software development company and we also provide consultancy services to folks who are looking to scale or accelerate their engineering roadmaps," explained Jeremiah Mothersell, Marketing Manager at Akvelon, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...