We believe that half of the success of the Community is how easy it is to find what you need, so we're constantly working on making it as easy as possible. One of the best tools for finding what you want is using labels. Thanks to them, you can easily filter through hundreds of topics in the Community.
We’ve set up our labels in a way that reflects both the Dynatrace product and how our users are using it on an everyday basis, so we all speak the same language. Now by simply labeling your posts correctly, you'll ensure more people will be able to find them and help you find solutions.
The label structure
Here is the label structure used across all Dynatrace Self-service Support teams. As you can quickly notice, they're all centered around specific Dynatrace solutions.
Account Experience:
- account management
- licensing
- monitoring consumption
- user management
We merged all “licensing” labels (like DEM, DDU, etc.) into one. Besides that, we also created a special label for “monitoring consumption” in Dynatrace.
Security Protection and Security Analytics:
- application security
- appsec attacks
- appsec vulnerabilitiles
As the Security Protection and Security Analytics solution grows, we added two new labels for specific questions about “appsec attacks” and “appsec vulnerabilities.”
Applications and Microservices:
- applications and microservices
- databases
- distributed tracing
- distributed traces classic
- multidimensional analysis
- profiling and optimizations
- request attributes
- service flow
- services
- services classic
As we wanted to be closer to the product with our label naming scheme, we’ve changed the “purepath” label (more precise one) into “distributed traces” (more general). Similarly, all diagnostic topics are now under the “profiling and optimization” label.
A&M Technologies:
- apache
- dotnet
- go
- iib
- iis
- java
- mainframe
- nginx
- nodejs
- oneagent sdk
- opentelemetry
- php
- serverless
No significant changes in technologies’ naming.
Automations:
- integrations
- workflows
- slo
- automations
- problem notifications
- automationengine
- site reliability guardian
“slo” label will gather all content around SLO/SLI/SLA.
Digital Experience:
- digital experience
- android
- real user monitoring
- browser monitors
- http monitor
- ios
- mobile monitoring
- openkit
- private synthetic locations
- session replay
- synthetic monitoring
- user sessions
- usql
Although many of us got used to the “RUM” name, we have changed it to “real user monitoring”. It would make the label clear even for our newcomers.
Dynatrace Hub:
- hub
- extensions
When you want to ask a question about extensions, use the “extension” label. And for all topics around improving Dynatrace Hub itself, use “hub”.
Infrastructure Monitoring:
- infrastructure monitoring
- infrastructure & operations
- clouds
- hosts classic
- logs
- log monitoring classic
- data ingest
- openpipeline
- network monitoring
- oneagent
- process groups
- processes
The biggest change in the infrastructure monitoring labels is a division between "log monitoring classic" and the newest app, simply named "logs".
Besides that, there’s a new “processes” label for all the topics related to the “Technologies and processes” capability.
Technologies (Cloud & Host):
- aix
- aws
- azure
- cloud foundry
- docker
- google cloud platform
- heroku
- kubernetes
- linux
- openshift
- solaris
- vmware
- windows
The only big change here is the deletion of the “system” label. From good news – we finally changed the “amazon web services” label to the “aws,” as this naming is clearly more popular.
Platform:
- tokens
- activegate
- audit logs
- credential vault
- dashboards
- dashboards classic
- data explorer
- data privacy and product security
- davis
- dql
- dynatrace api
- dynatrace mobile app
- tagging
- segments
- management zones
- metrics
- network zones
- platform notifications
- problems
- problems classic
- problem detection
- problem notifications
- reports
- smartscape
We have adjusted the naming of some labels: “tags and metadata” became “tagging”, “security” is now “data privacy and product security”, and “mobileapp” transformed into “dynatrace mobile app.”
We also divided the “notification” label into two separate labels: “problem notifications” and “platform notifications.”
Platform Delivery:
- dynatrace managed
- cluster management console
- mission control
- dynatrace saas
Similarly, as we did with “real user monitoring”, “cmc” is now a “cluster management console.”
Other:
- maintenance window
- installation
- updates
- python
- ruby
The only small change here is renaming “auto-update” to “updates”.
There's also a list of labels associated with the new Dynatrace:
Latest Dynatrace:
- latest dynatrace
- custom app
- coding assistance
- app functions
- strato
- platform services
- dynatrace app toolkit
- ad-hoc functions
- apps
*All the labels can change in the future, as the Dynatrace grows and evolves every day. This article will be updated to reflect those changes.
How to subscribe to content
You can filter Community content based on a specific topic by just clicking on a label. You can also subscribe to labels to be notified about new content that appears in our Community on the topic. Just remember that following the label from a sub-forum will only show you content from that specific sub-forum. So, if you want to follow ideas and questions about “synthetic monitoring” you should follow the label both in Product Ideas and Synthetic Monitoring forums.
2 Comments
