Mynd for DevOps engineers
DevOps Engineer, as it will appear in the app, in the next version.
A DevOps engineer brings development and operations together: pipelines, environments, deployments and monitoring. What is learned in an incident must be written down.
The ready-made structure
Score 87 out of 100. What the score means.
The structure starts with Infrastructure, the centre of the work, divided into Platforms, Cloud and Resources. Then come Automation, Development, Containers, Operations, Security and AI. Each record keeps its full path, for example Infrastructure, Platforms, Servers, and can be found by any of the three levels.
The full tree is at the end of this page, with the names as they are in the app.
Suggested Context phrases
The structure says what each record is about. The Context phrases, which each person creates, say the rest. For this profession, some that tend to serve:
Incident Pipeline Lesson learned Automate
A report that sends itself
A search gathers lessons learned from incidents. Every month, the development teams receive the list.
What you gain: Incidents stop recurring for the same reason.
The card with the deployment procedure goes to each new developer.
In this version, Start, each person has 14 automatic search sends and 14 card sends; in Run, they will be able to have as many as they need. Each send has its own search, its own recipients and its own frequency: daily, weekly, monthly or on a date. Emails go out from the person's own email account, and each recipient receives their own.
The full tree
Infrastructure3 Types
- Infrastructure/PlatformsServersContainersClusters
- Infrastructure/CloudAWSAzureGoogleCloud
- Infrastructure/ResourcesComputeStorageNetwork
Automation3 Types
- Automation/ProvisioningTerraformAnsiblePacker
- Automation/ScriptingBashPythonPowerShell
- Automation/WorkflowsJobsTriggersSchedules
Development3 Types
- Development/RepositoriesGitBranchesMerges
- Development/CIBuildsTestingArtifacts
- Development/CDDeploymentsReleasesRollbacks
Containers3 Types
- Containers/DockerImagesVolumesNetworks
- Containers/KubernetesPodsServicesIngress
- Containers/OrchestrationScalingBalancingRecovery
Operations3 Types
- Operations/MonitoringMetricsLogsAlerts
- Operations/ReliabilityAvailabilityPerformanceResilience
- Operations/SupportIncidentsProblemsChanges
Security3 Types
- Security/IdentityUsersRolesPolicies
- Security/ProtectionSecretsEncryptionFirewalls
- Security/ComplianceAuditsStandardsReporting
AI3 Types
- AI/PipelinesReviewsTestsFixes
- AI/IncidentsTriageSummariesRootCause
- AI/InfrastructureIaCGenerationDriftCosts
