Measurements per device or per metric

Hello,
Can someone provide some inputs on what should be the schema of my measurements in this case: we will be reading about 100 metrics (in the future we will keep adding more) of thousands of devices, we need to identify every single device. So I was thinking of one of these two approaches (I am using JSON format), which one looks better?

Measurements per Device:

[
    {
        "measurement": "device001",
        "tags": {
            "hostname": "device001",
            "location": "some_location",
        },
        "time": "Mon Apr 20 12:51:43 2020",
        "fields": {
            "metric_1": 1280,
            "metric_2": 16,
            "metric_3": 0,
            "metric_4": 0,
            "metric_5": 16

Measurements per Metric:

[
    {
        "measurement": "metric_1",
        "tags": {
            "hostname": "device001",
            "location": "some_location",
        },
        "time": "Mon Apr 20 12:51:43 2020",
        "fields": {
            "value": 1280
[
    {
        "measurement": "metric_2",
        "tags": {
            "hostname": "device001",
            "location": "some_location",
        },
        "time": "Mon Apr 20 12:51:43 2020",
        "fields": {
            "value": 16
[
    {
        "measurement": "metric_3",
        "tags": {
            "hostname": "device001",
            "location": "some_location",
        },
        "time": "Mon Apr 20 12:51:43 2020",
        "fields": {
            "value": 0

@RubenAgDev Use measurements sparingly. Too many measurements can be bad for your database. I would just using one or a handful of general measurements, using just the hostname or device tag to identify the origin device, and using the metric names as the field keys.

[
    {
        "measurement": "device_metrics",
        "tags": {
            "hostname": "device001",
            "location": "some_location",
        },
        "time": "Mon Apr 20 12:51:43 2020",
        "fields": {
            "metric_1": 1280,
            "metric_2": 16,
            "metric_3": 0,
            "metric_4": 0,
            "metric_5": 16

Depending on what kind of information you’re storing, you could use the measurement as a category. For example:

  • measurement: environment
    • field: temp
    • field: humidity
    • field: co2
  • measurement: diagnostics
    • field: uptime
    • field: ping
    • field: cpu-temp
  • etc.

That makes sense now.
Thanks for your response, I will design my measurements that way!