- Observability: other versions:
- Get started
- What is Elastic Observability?
- What’s new in 9.0
- Quickstart: Monitor hosts with Elastic Agent
- Quickstart: Monitor your Kubernetes cluster with Elastic Agent
- Quickstart: Monitor hosts with OpenTelemetry
- Quickstart: Unified Kubernetes Observability with Elastic Distributions of OpenTelemetry (EDOT)
- Quickstart: Collect data with AWS Firehose
- Add data from Splunk
- Applications and services
- Application performance monitoring (APM)
- Get started
- Learn about data types
- Collect application data
- View and analyze data
- Act on data
- Use APM securely
- Manage storage
- Configure APM Server
- Monitor APM Server
- APM APIs
- Troubleshooting
- Upgrade
- Release notes
- APM version HEAD
- APM version 8.17
- APM version 8.16
- APM version 8.15
- APM version 8.14
- APM version 8.13
- APM version 8.12
- APM version 8.11
- APM version 8.10
- APM version 8.9
- APM version 8.8
- APM version 8.7
- APM version 8.6
- APM version 8.5
- APM version 8.4
- APM version 8.3
- APM version 8.2
- APM version 8.1
- APM version 8.0
- Known issues
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Multi-factor Authentication
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Scale and architect a deployment
- Synthetics support matrix
- Synthetics Encryption and Security
- Troubleshooting
- Real user monitoring
- Uptime monitoring (deprecated)
- Tutorial: Monitor a Java application
- Application performance monitoring (APM)
- CI/CD
- Cloud
- Infrastructure and hosts
- Logs
- Troubleshooting
- Incident management
- Data set quality
- Observability AI Assistant
- Reference
Configure individual browser monitors
editConfigure individual browser monitors
editThis is only relevant for project monitors. For more information on configuring browser monitors added in the Synthetics app, refer to Use the Synthetics app.
After writing synthetic journeys, you can use monitor.use
to configure the browser monitors that will run your tests.
You’ll need to set a few configuration options:
- Give your monitor a name. Provide a human readable name and a unique ID for the monitor. This will appear in Kibana where you can view and manage monitors after they’re created.
- Set the schedule. Specify the interval at which your tests will run.
- Specify where the monitors should run. You can run monitors on Elastic’s global managed testing infrastructure or create a Private Location to run monitors from your own premises.
- Set other options as needed. There are several other options you can set to customize your implementation including params, tags, screenshot options, throttling options, and more.
Configure each monitor directly in your journey
code using monitor.use
.
The monitor
API allows you to set unique options for each journey’s monitor directly through code.
For example:
import { journey, step, monitor, expect } from '@elastic/synthetics'; journey('Ensure placeholder is correct', ({ page, params }) => { monitor.use({ id: 'example-monitor', schedule: 10, throttling: { download: 10, upload: 5, latency: 100, }, }); step('Load the demo page', async () => { await page.goto('https://elastic.github.io/synthetics-demo/'); }); step('Assert placeholder text', async () => { const placeholderValue = await page.getAttribute( 'input.new-todo', 'placeholder' ); expect(placeholderValue).toBe('What needs to be done?'); }); });
For each journey, you can specify its schedule
and the locations
in which it runs.
When those options are not set, Synthetics will use the default values in the global configuration file.
For more details, refer to Configure projects.