Add MicrobotsLogAnalyzer custom ADO task#145
Open
MadhurAggarwal wants to merge 12 commits into
Open
Conversation
Member
Author
|
Moved From Forked Repo PR: #141 |
KavyaSree2610
requested changes
May 26, 2026
| ## Prerequisites | ||
|
|
||
| - Azure DevOps organization where you can install custom extensions. | ||
| - Azure Resource Manager Service Connection with permission to request tokens for the Azure OpenAI resource. The pipeline must be authorized to use this service connection. |
Collaborator
There was a problem hiding this comment.
Add the doc link on how to create a service connection here https://microsoft.github.io/microbots/guides/azure-managed-identity-setup/
| tfx extension publish --manifest-globs vss-extension.json --token <AZURE_DEVOPS_PAT> --share-with <AZURE_DEVOPS_ORGANIZATION> | ||
| ``` | ||
|
|
||
| Update the `publisher` value in `vss-extension.json` before running `tfx extension create`. The task folder must contain `node_modules` when the VSIX is created, so run `npm ci --omit=dev` before packaging. |
Collaborator
There was a problem hiding this comment.
Update the publisher value to what?
| | `codebasePath` | Yes | - | Repository or source folder Microbots can inspect while analyzing the log. | | ||
| | `logFilePath` | Yes | - | Log file path. Use an absolute path, or a relative path resolved from `codebasePath`. | | ||
| | `timeoutSeconds` | No | `600` | Maximum time for `LogAnalysisBot.run()`. | | ||
| | `maxIterations` | No | LogAnalysisBot default | Maximum number of Microbots iterations. Leave unset to use the default from `LogAnalysisBot.run()`. | |
Collaborator
There was a problem hiding this comment.
mention the number of iterations that are default for log analysis bot
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #145 +/- ##
==========================================
+ Coverage 64.95% 65.04% +0.08%
==========================================
Files 34 34
Lines 2374 2380 +6
==========================================
+ Hits 1542 1548 +6
Misses 832 832
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
MadhurAggarwal
force-pushed
the
madagg/log-analyzer-ado-task
branch
from
717c78e to
87c8f36
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Adds a custom Azure DevOps task,
MicrobotsLogAnalyzer@0, for running MicrobotsLogAnalysisBotagainst log files using Azure OpenAI models, with authentication through an Azure Resource Manager Service Connection.Overview
MicrobotsLogAnalyzerTaskAzure Pipelines task.Change Details
.gitignore: Ignores generatednode_modulesfolders used while packaging the ADO task.README.md: Added a brief guide for the new MicrobotsLogAnalyzerTask.azure-pipelines/vss-extension.json: Defines the ADO extension that contributes the custom pipeline task. This file is needed for publishing the task.azure-pipelines/MicrobotsLogAnalyzerTask/task.json: Defines theMicrobotsLogAnalyzer@0task metadata, inputs, Node 20 handler, and task restrictions (restrictions ensure that LLM Outputs don't setup unwanted ENVs in ADO Pipeline, for example printing##vso[task.setvariableas part of Log RCA)azure-pipelines/MicrobotsLogAnalyzerTask/index.js: Implements Main Workflow: validates inputs, logs into Azure Service Connection, prepares Python venv, runsLogAnalysisBot, and prints the analysis.azure-pipelines/MicrobotsLogAnalyzerTask/package.json: Declares the Node dependencies required by the task.azure-pipelines/MicrobotsLogAnalyzerTask/package-lock.json: Locks task Node dependency versions for reproducible packaging.docs/azure-pipelines-log-analyzer.md: Documents prerequisites, packaging, publishing, usage, inputs, and task behavior.docs/examples/azure-pipelines/microbots-log-analyzer.yml: Provides a sample ADO YAML for usingMicrobotsLogAnalyzer@0.mkdocs.yml: Adds the new Azure Pipelines Log Analyzer guide to the docs navigation.Added 12 Unit tests:
