- 
                Notifications
    
You must be signed in to change notification settings  - Fork 25.6k
 
[Profiling] Add k8s namespace to events #117323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
            rockdaboot
  merged 2 commits into
  elastic:main
from
rockdaboot:profiling-add-k8s-namespace
  
      
      
   
  Nov 23, 2024 
      
    
                
     Merged
            
            [Profiling] Add k8s namespace to events #117323
                    rockdaboot
  merged 2 commits into
  elastic:main
from
rockdaboot:profiling-add-k8s-namespace
  
      
      
   
  Nov 23, 2024 
              
            Conversation
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
    | 
           Pinging @elastic/obs-knowledge-team (Team:obs-knowledge)  | 
    
Co-authored-by: Francesco Gualazzi <francesco.gualazzi@elastic.co>
3883711    to
    c5b4d27      
    Compare
  
    
              
                    inge4pres
  
              
              approved these changes
              
                  
                    Nov 22, 2024 
                  
              
              
            
            
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
          💚 All backports created successfully
 Questions ?Please refer to the Backport tool documentation  | 
    
    
  inge4pres 
      added a commit
        to inge4pres/elasticsearch
      that referenced
      this pull request
    
      Nov 25, 2024 
    
    
      
  
    
      
    
  
Co-authored-by: Francesco Gualazzi <francesco.gualazzi@elastic.co> (cherry picked from commit 8fe13f5)
    
  inge4pres 
      added a commit
      that referenced
      this pull request
    
      Nov 25, 2024 
    
    
  
    
  alexey-ivanov-es 
      pushed a commit
        to alexey-ivanov-es/elasticsearch
      that referenced
      this pull request
    
      Nov 28, 2024 
    
    
      
  
    
      
    
  
Co-authored-by: Francesco Gualazzi <francesco.gualazzi@elastic.co>
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      Labels
      
    auto-backport
  Automatically create backport pull requests when merged 
  
    cloud-deploy
  Publish cloud docker image for Cloud-First-Testing 
  
    >enhancement
  
    Team:obs-knowledge
  Meta label for Observability Knowledge team 
  
    :UniversalProfiling/Application
  Elastic Universal Profiling REST APIs and infrastructure 
  
    v8.18.0
  
    v9.0.0
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Here we add the field
k8s.namespace.nameto theprofiling-events-*datastreams.The name and content of the field are conforming with the OTEL semantic conventions.
Filtering profiling data by the k8s namespace has been requested by customers several times.