-
Notifications
You must be signed in to change notification settings - Fork 426
User-Agent should include receiver type #1150
Copy link
Copy link
Open
Labels
enhancementM-T: A feature request for new functionalityM-T: A feature request for new functionalitysemver:patch
Milestone
Description
Description
We should start to include the receiver type (HttpReceiver, SocketModeReceiver, AwsLambdaReceiver, ExpressReceiver) in the user-agent string. This would allow us to understand the adoption of each receiver and prioritize missing features based on usage.
What type of issue is this? (place an x in one of the [ ])
- bug
- enhancement (feature request)
- question
- documentation related
- example code related
- testing related
- discussion
Requirements (place an x in each of the [ ])
- I've read and understood the Contributing guidelines and have done my best effort to follow them.
- I've read and agree to the Code of Conduct.
- I've searched for any related issues and avoided creating a duplicate issue.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementM-T: A feature request for new functionalityM-T: A feature request for new functionalitysemver:patch