ceven

Blazemeter

Triggers performance tests, monitors API health schedules, and pipes test validation results into your deployment pipeline to block buggy releases.

Try Blazemeter in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Blazemeter integration

    • Describe the outcome and Ceven picks the right Blazemeter calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Blazemeter data, across all 92 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Blazemeter access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Blazemeter, when, and on whose behalf.
    • The agent pauses and asks when Blazemeter is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Blazemeter.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Blazemeter action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Blazemeter, and when to use it.

Create API Monitoring Schedule
Use this when you need to automate test runs at defined intervals using a cron expression and test ID.
Create Multi Test
Use this to launch a new multi test within a specific project after you have the project ID.
Create Project
Use this to initialize a new project inside a specific workspace using the workspace ID.
Create Test
Use this when registering a new single performance test via the API within a project.
Delete API Monitoring Schedule
Use this to remove a scheduled test by its unique schedule identifier.
Get API Monitoring Schedules
Pull a list of all test schedules in your account to review timing and configuration.
Get Multi Tests
Pull a list of multi tests within a specified project or workspace using the ID.
Get Projects
Pull a list of projects within a specified workspace to enumerate available environments.
Get Tests
Pull a list of single tests within a project or workspace for a specific project ID.
Get Test Validations
Pull validation results for a specific test ID to confirm if uploaded files are valid.
Stop Master
Use this to abort a running test execution immediately by its master ID.
Update API Monitoring Schedule
Use this to enable or disable an existing monitoring schedule after confirming the ID.
Update Test
Use this to modify the name or configuration of an existing test by its ID.
Upload Test Files
Use this to attach scripts or resource files to a specific test ID before execution.
Validate Test
Use this to check if the configuration of a specific test ID is valid and ready to run.
Get Workspaces
Pull a list of workspaces for a specified account to filter by name or status.
Get Accounts
Tool to retrieve a list of accounts associated with the authenticated user. use after confirming valid authentication.
Get API Monitoring Schedule
Tool to retrieve details of a specific api monitoring schedule by its id. use when you need to inspect the configuration or timing of an existing schedule.
Get Multi Test
Tool to retrieve details of a specific multi test. use after creating or listing multi tests when you need full configuration and status. minimal example: "get multi test 12345678 with populated tests."
Get User
Tool to retrieve information about the authenticated user. use when you need the current user's profile and have valid authentication.

20 actions · scroll to see them all

Frequently asked questions

Ceven connects to BlazeMeter using an API key and API secret provided by your account administrator. We store these credentials in an encrypted vault that is isolated from the model context. When an agent needs to trigger a test or pull a report, Ceven retrieves the secret to sign the request and sends it over an encrypted TLS connection. You can rotate these keys at any time within the BlazeMeter account settings, which will require a quick update in the Ceven integration panel to restore connectivity. We never log your API secret in plain text and the agent cannot read the secret itself.
Yes. By using the Get Test Validations action in a loop or watching for specific error thresholds in the results, Ceven can trigger the Stop Master action. This is particularly useful for preventing the waste of BlazeMeter credits when a test fails immediately due to a configuration error or a complete environment outage. You can set a rule that says if the error rate exceeds twenty percent in the first two minutes, the agent should kill the test and alert the team on Slack, ensuring you do not burn through your monthly test capacity on a broken build.
BlazeMeter imposes rate limits on its API to ensure platform stability across all users. If Ceven triggers too many requests in a short window, BlazeMeter will return a 429 Too Many Requests response. To handle this, Ceven implements an exponential backoff strategy, meaning the agent will wait and retry the request automatically. However, if you are running massive parallel workflows that create hundreds of tests per minute, you may hit these limits frequently. We recommend grouping test creations into multi tests or spacing out your API monitoring schedule updates to avoid hitting these platform ceilings.
Yes, Ceven can use the Create Project and Get Workspaces actions to organize your testing environment. For example, you can build a workflow where every new feature branch in GitHub triggers the creation of a dedicated BlazeMeter project. This keeps your performance data isolated by feature, making it easier to compare the baseline of the main branch against the new code. Once the feature is merged and the test is complete, the agent can be configured to delete the project to keep your workspace clean and organized without manual intervention.
Ceven uses the Upload Test Files action to send your JMX or other script files directly to the BlazeMeter servers. Because these files can be large, Ceven handles the upload as a multipart request to ensure data integrity. If a file is too large for a single request, the agent will log a specific error. We recommend hosting very large data sets in a cloud bucket and referencing them in your scripts rather than uploading them through the API every time, as this reduces the risk of timeout errors during the upload phase.
Absolutely. Ceven can interact with the Create API Monitoring Schedule and Update API Monitoring Schedule tools. You can tell the agent to set up a test that runs every Monday at 3 AM or adjust the timing based on your release calendar. Because BlazeMeter uses cron expressions for these schedules, Ceven translates your natural language request into the correct cron format before sending it to the API. This allows you to manage your entire performance monitoring calendar through a chat interface instead of manually editing schedules in the BlazeMeter UI.
Ceven supports both. For simple checks, it uses the Create Test action. For more complex scenarios, such as testing multiple endpoints across different geographic regions simultaneously, it uses the Create Multi Test action. The agent can pull the full configuration of a multi test using Get Multi Test to ensure all child tests are running as expected. This flexibility allows you to scale from a simple smoke test to a full scale stress test of your entire global infrastructure using the same set of automated workflows.
Ceven can pull the high level results and validation status using the Get Test Validations action. While it does not ingest every single raw data point from a load test, it can read the summary metrics and the pass fail status of your assertions. The agent then uses this information to make logic based decisions, such as whether to promote a build to production or to trigger a rollback. For deep dive analysis, the agent can provide you with a direct link to the BlazeMeter report for that specific test ID so you can view the detailed graphs.

Alternatives to Blazemeter

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

k6 logok6LoadRunner logoLoadRunnerJMeter logoJMeterGatling logoGatling

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Blazemeter and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free