New Relic One is an observability platform, offering support from monoliths to serverless. It helps engineers to instrument, analyze, troubleshoot and optimize the entire software stack - all from one place.
To integrate steadybit with New Relic, there are two general possibilities:
- New Relic to steadybit: checking for specific events from New Relic in steadybit during experiment execution
- steadybit to New Relic: pushing steadybit events during experiment execution to New Relic
We are able to react to the different events of New Relic and process them within the execution of an experiment. You can filter the events and determine at which event type the experiment should fail.
Settings/Monitoring Integrations/New Relicyou can enable the State Check by providing the New Relic
Rest API Base URLand the
REST API tokenthat was previously created in New Relic. That's all we need to react on events of New Relic.
By connecting steadybit to New Relic Insights you are able to investigate the effect of an attack within your familiar monitoring setup (e.g. New Relic dashboards). Thus you can see the direct effect of an attack to certain metrics like erroneous calls, CPU usage or whatever metric is important to you.
Within steadybit go into
Settings/Monitoring Integrations/New Relic, where you can enable the sending of events by providing the
Insights Base URL, New Relic
Account Idas well as the
Insights Insert Key. The former one can be looked up in the New Relic documentation, the latter two are created in the New Relic settings upfront.
As soon as the configuration of New Relic Insights is provided, steadybit sends events of every executed experiment automatically to New Relic. These events can be configured for instance as an own widget on your dashboard by using
NRQL(New Relic Query Language). An example is given below as well as a short explanation of the data structure.
Below you see an example widget that can be configured on your New Relic dashboard. This helps you to correlate the execution of an experiment with other dashboard widgets.
New Relic Insights Example
Events of steadybit are published as the custom event
ExperimentExecutionwhich can be queried using
NRQL. Therefore, go within New Relic to the Dashboard, add a new widget of type chart and use for instance the following
cases( WHERE attack IN ('container-cpu-attack', 'host-cpu-attack') AS 'cpu',
WHERE attack IN ('container-memory-attack', 'host-memory-attack') as 'memory',
WHERE attack in('container-io-attack', 'host-io-attack') as 'IO'),
Experiment Events coming from steadybit have generally the structure below. Thereby,
executionTypecovers what was exectued (e.g.
actionfor a load test) and
statuswhether it was
In addition, events covering the execution of an Attack (
attack) have additional attributes: