I want to write in another index with project monitor (synthetic monitor) It's possible?

Elastic Observability Synthetics
1

I want to write in another index with project monitor (synthetic monitor) It's possible?, I can to change the index synthetic-* or write in other datastream?

2

Hi Oscar,

Thank you for your question. It seems like your question is similar to this one.

In there you will find Tiago's comments which outlines that you can indeed configure these indexing conditions depending on the data. For that, you can have a look at the docs here.

Hope that helps! Please let me know if that's not exactly what you needed or whether there's anything else I can do to help :slight_smile:

3

Hi Lucas,
Currently I don't use Heartbeat, I use Project monitor so I send the monitor by push command (Push api-key url-kibana name-project), installed nodeJS and Playwright @elastic/synthetic, so this method send to index synthetic-* by default, this is a DataStream.

4

Hi Oscar, unfortunately there's no way of doing this yet in case you're pushing monitors to the managed infrastructure to run.

I will bring your suggestion to the team for us to discuss and maybe implement, but I can't make any promises about that, although I do think it is an interesting/useful request.

In the mean time, you should be able to edit the data stream, change the backing-indices, and then reindex the documents from the old index that was being used as the current. I know this is suboptimal, but thought I'd bring it up in case you think it could be helpful.

Thanks again for reaching out, Oscar

1 Like
5

Hey Oscar, one question we discussed within the team is whether you'd be able to explain us a bit more about the use case of changing those indices. We thought that maybe there would be a better way of accomplishing what you wanted without changing the backing indices themselves.

Would you be able to provide us with some more details on this?

Thanks in advance!

6

Hi Lucas,
We want to generate synthetic monitors for different clients, so each client should have an index with different ILMs, as the client requires.

Do you need another information? Tell me please!

1 Like
7

Lucas,
In addition to this,

  1. Is it possible to alter the format of the data Stream index? for example .ds-synthetics-browser-default-2022.08.05-000001, I want to remove the date. That is, what things can I work or customize on the data stream synthetics--.
  2. When we use push command to send monitor project to kibana, we have two options in --project => id | name, how do I send a value for the id and another for the name?
1 Like
8

Hi @odelacruzc,

Thanks for providing information on your use case.

It should be possible to have multiple monitors write to different data streams with the use of spaces. You can use the --space option with the push command to achieve this effect, specifying an existing Kibana space. When monitors are pushed with a different space, a new data stream is generated with the format synthetics-<monitor type>.<data type>-<space>.

Once you have separate data streams, you can follow this tutorial to set custom ILM policies for them. You'll need to do so for each of the data streams in which synthetics data gets segmented into. We do recommend against editing existing managed policies for synthetics integrations.

About your other questions:

  1. Backing indices for data streams are generated automatically, there's no actual way of changing how this name is generated.
  2. Cli log is not very clear on this, --project is used to group monitors from a same project and it only takes a single value. There's a more detailed explanation here.

Hope this helps.

1 Like
9

This topic was automatically closed 24 days after the last reply. New replies are no longer allowed.