应当把它放在 command 文件夹下面并把 metadata 改为 Xray 的，还有这个文件复制进来没有 license 问题吧

你改好后，这个 PR 我来合并（时机成熟时，现在 main 在搞 MMDF）

Guys please don't copy protobuf code in project.
protocolbuffers/protobuf#5131

@yuhan6665 I did that last time, but my PR was canceled: #4347
Then how to work with ptorobuf in this project, I would appreciate an explanation.

可以换成自定义的结构吗？不引用外部 proto

Yes, i can do it. I'll just say it again, @yuhan6665 told me to use google protobuf, so that's what I did...

Please don't define your own timestamp, use protobuf version, properly.

@yuhan6665 like I did last time, right? #4347

我不太了解 proto 这里是怎么回事

那如果引用外部 proto，执行 go run ./infra/vprotogen 前都要先把那个外部 proto 拉到本地？

@RPRX It turns out that it is...

所以 google standard timestamp 有什么特别的好处吗？我们不是只需要 timestamp 的值而已？

Initially, I just did the display in seconds, but I was told to use google timestamp. I did so, everything was accepted, but there was a rollback due to the lack of file data during execution: go run ./infra/vprotogen

我想了解下 @yuhan6665 的看法，或许这里我们只是需要一个值？

如果需要先拉下来外部 proto 就比较难受了，我经常 go run ./infra/vprotogen

Using google protobuf is not rocket science, I'm sure we (whoever run into issue) can fix it.
I'm just saying this PR copying of timestamp is not proper usage

主要是看到了 then convert the time.Time to standard google.protobuf.Timestamp

既然没有特别的需求，直接拿个 uint64 存 timestamp 吧

So I'm just returning the timestamp in uint64?

timestamp轻松加愉快为什么要搞个这个东西进来

No no, I'll just return the timestamp (uint64), okey?

timestamp轻松加愉快为什么要搞个这个东西进来

没看懂

@mr1cloud just uint64

Okay, I think that's it.

Execute:

.\xray.exe api statsonlineiplist -server="127.0.0.1:8080" -email user1

Result:

{
    "ips": {
        "192.168.1.2": 1738924438
    },
    "name": "user>>>user1>>>online"
}

改成 int64 吧，不用转换类型了

Does anyone know why I can't get user IPs and access times tracking?

root@localhost:/etc/nginx/conf.d# xray api statsquery --server="127.0.0.1:10085"
{
    "stat": [
        {
            "name": "inbound>>>trojan-ws>>>traffic>>>uplink"
        },
        {
            "name": "outbound>>>direct>>>traffic>>>downlink",
            "value": 1301318
        },
        {
            "name": "outbound>>>block>>>traffic>>>downlink"
        },
        {
            "name": "outbound>>>dns-out>>>traffic>>>uplink"
        },
        {
            "name": "user>>>[email protected]>>>traffic>>>uplink",
            "value": 675335
        },
        {
            "name": "inbound>>>trojan-ws>>>traffic>>>downlink"
        },
        {
            "name": "inbound>>>vless-ws>>>traffic>>>uplink"
        },
        {
            "name": "inbound>>>vless-ws>>>traffic>>>downlink"
        },
        {
            "name": "outbound>>>block>>>traffic>>>uplink"
        },
        {
            "name": "outbound>>>dns-out>>>traffic>>>downlink"
        },
        {
            "name": "outbound>>>api>>>traffic>>>uplink"
        },
        {
            "name": "inbound>>>api>>>traffic>>>downlink",
            "value": 1387
        },
        {
            "name": "inbound>>>vless-main>>>traffic>>>uplink",
            "value": 809502
        },
        {
            "name": "inbound>>>vless-main>>>traffic>>>downlink",
            "value": 1412425
        },
        {
            "name": "inbound>>>vmess-ws>>>traffic>>>uplink",
            "value": 762618
        },
        {
            "name": "outbound>>>direct>>>traffic>>>uplink",
            "value": 675335
        },
        {
            "name": "user>>>[email protected]>>>traffic>>>downlink",
            "value": 1301318
        },
        {
            "name": "inbound>>>api>>>traffic>>>uplink",
            "value": 947
        },
        {
            "name": "inbound>>>vmess-ws>>>traffic>>>downlink",
            "value": 1384095
        },
        {
            "name": "outbound>>>api>>>traffic>>>downlink"
        }
    ]
}

root@localhost:/etc/nginx/conf.d# 
root@localhost:/etc/nginx/conf.d# 
root@localhost:/etc/nginx/conf.d# xray api statsonlineiplist -email [email protected] --server="127.0.0.1:10085"
failed to get stats: rpc error: code = Unknown desc = app/stats/command: user>>>[email protected]>>>online not found.

@fluxx365 you need to use statsonlineiplist instead of statsquery

the result is the same, still can't get data from “statsonline” or “statsonlineiplist”

root@localhost:~# xray api statsonlineiplist --server="127.0.0.1:10085"
failed to get stats: rpc error: code = Unknown desc = app/stats/command: user>>>>>>online not found.
root@localhost:~# 

root@localhost:~# xray api statsonline --server="127.0.0.1:10085"
failed to get stats: rpc error: code = Unknown desc = app/stats/command: user>>>>>>online not found.
root@localhost:~# 

@fluxx365 could you attach which version of the core you are using?

xray version

@fluxx365 could you attach which version of the core you are using?

xray version

this one

root@localhost:~# xray version
Xray 25.3.6 (Xray, Penetrates Everything.) 2cba2c4 (go1.24.1 linux/amd64)
A unified platform for anti-censorship.

@fluxx365 look, its working

@fluxx365 If the client has not connected once since the core was launched, then it will be written that it was not found, this is a feature of the statistics service, it does not download the user until he is connected.

And 127.0.0.1 will not count, I must use LAN IP during test(((((

@fluxx365 look, its working

this is strange, I am really connected and also checked the IP has changed with the server IP

@fluxx365 on my own server it's work perfectly

is there something wrong with my config?

@fluxx365 Oh, you need to add "statsUserOnline": true, to you 0 level policy.

example:

"policy": {
        "levels": {
            "0": {
                "statsUserDownlink": true,
                "statsUserOnline": true,
                "statsUserUplink": true
            }
        },
        "system": {
            "statsInboundDownlink": true,
            "statsInboundUplink": true
        }
    }

@fluxx365 Oh, you need to add "statsUserOnline": true, to you 0 level policy.

example:

"policy": {
        "levels": {
            "0": {
                "statsUserDownlink": true,
                "statsUserOnline": true,
                "statsUserUplink": true
            }
        },
        "system": {
            "statsInboundDownlink": true,
            "statsInboundUplink": true
        }
    }

thank you very much, now it appears

@mr1cloud thank you for the nice feature! Had the same issue online not found, fixed with enabling "policy"
Do you think it should be listed somewhere in CLI tools help or in the error message if command failed to help debugging?

@mr1cloud thank you for the nice feature! Had the same issue online not found, fixed with enabling "policy" Do you think it should be listed somewhere in CLI tools help or in the error message if command failed to help debugging?

Hmm, maybe yes, but all the other CLI functions don't provide this information. That is, I just matched the style of the other developers.

Maybe I didn't quite understand what you mean.